Aktueller Inhalt von regeditor

  1. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Hi, At the beginning of the code fragment, you begin the conditional statement (IF) with reading from the VFD (ETA word) then progress forwardly by writing to the VFD (CMD word). These two aspects reflect two different configurations for the MB_MODE where in the first, it must be set to 103 (to...
  2. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Hello, I have just notice this request. Attached it is the SoMove project including: 1) an ability to write to the VFD (LFR) 2) an ability to read the voltage input on AI2 3) a configuration for AI3 to support PT100, but still, on TIA I cannot see anything related to temperature
  3. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Hi, By taking into consideration this circuitry (PT100 is to be connected on AI3): And MB_MODE = 103, MB_DATA_PTR = 0, MB_DATA_LEN = 1 and having set AI3C on Channel 1 of Inputs: Could you please state what is left to be configured on the side of the VFD, in order to read temperature on...
  4. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Hello again, My VFD is also from 2022 series (brand new). I did exactly the same wiring as within your attached image. As an alternative trial, I have set AI3T to PT100 and placed the physical value AI3C of the sensor on the Inputs list: What else must have been done in order to have...
  5. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Hello, thank you for your time, and good luck with your server maintenance. I would drain less from your time, as I have new outputs and I am able to read voltage from AI2. If you can please confirm the following: unlike Siemens AI modules for example, the PT100 cannot be directly connected...
  6. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Hello and thank you again! According to what has been precedent: 1) it is understandable now that AI1 only reads voltage or current as set in the drive configuration. For both cases, the resultant values (whether in mA or V) can be seen from the VFD webserver. Can we observe voltage/current in...
  7. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    As an update: intended it is to read the Voltage from AI1. On the VFD side, the following parameters were set as Inputs: and AI1 is configured as "Voltage": On TIA side, the "Data_Receive".Voltage is set as INT, and this is the corresponding output: The value "576" is stubborn and...
  8. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Much thanks! Well, before just changing the attributes of the MB_Client FB, shouldn't the VFD be configured to have its AIx assigned for sensor readings? Again, my model is ATV630U30N4. Also, wiring connections must definitely be taken into consideration, for instance, a regular PT100 without...
  9. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Much thanks!!! Here is the update: 1) VFD new configs (as attachments): VFD_Config1 and VFD_Config2 2) PLC new configs (as attachments): MB_Client_Config and Data_Send and MB_Client As for the SoMove connection to the VFD, it is closed under TIA tests. Result: the VFD is now responding and a...
  10. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Hi again! I now have the 1515-2PN loaded with the MB_Client FB (the connection criteria between the PLC and the VFD is well established). Concerning SoMove configurations, attached it is what have been changed. The purpose is to only send the LFR (logical address = 8502) value from the...
  11. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Thank you! I have attempted to physically reset the PLC to factory settings, where still, after seeing it in PRONETA, its name is not changeable (as attached). I do not have any access to the PLC in TIA, since its IP address is showing unreachable, and therefore not a single online connection...
  12. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    I am unable to change the device name in PRONETA! Regardless, I have tried to adjust the CPU name the same as in PRONETA but still the device is NOT reachable (present in the list of target devices but cannot connect)
  13. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    It did. I have seen my PLC but with its IP address marked in RED, and a status that it is inaccessible!
  14. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    As a side note, I have set the IP address for the new CPU via PRONETA and it is now (in addition to the VFD) pingable from the host computer. When I attempt to download the project, it reveals that the destination PLC is not reachable! Any comments please?
  15. R

    Step 7 Modbus TCP: ET 200SP with Altivar VFD

    Thank you for your interest. Not really. I'm still trying. I have made all the Configs needed for the VFD in SoMove as you have told. Still, I need to check it via TIA FB. I have changed the CPU to 1515-2PN. I will acknowledge back all results. Thanks again
Zurück
Oben