4/4/2014 4:14 PM | |
Posts: 23 Rating: (1) |
Thanks in advance, please take note that ID=9 attachment:
AttachmentOB1-OB100-DBs.pdf (482 Downloads) |
4/4/2014 5:02 PM | |
Posts: 23 Rating: (1) |
Hello I have different ID, ID=8 for the first CPU, ID=9 for the second CPU. In the previous post I attached OBx and DBs for the second CPU. Now I am attaching also CONTROL_DAT DB. Modbus TCP is not in the software redundancy. Hence two CPUs, with two modbus, with two different ID, in order to avoid any problem with the redundancy. AttachmentDB100.pdf (435 Downloads) |
4/7/2014 10:54 AM | |
Posts: 23 Rating: (1) |
Hello I'm checking the Modbus example to try to find any errors, and I have found that FB104 is used both sw redundancy and MODBUS TCP, so I decided to use FB104 SWR_AG_COM (for sw redundancy) because my modbus is server (not client). Is it a problem? And if yes, what can I do? AttachmentFB104.pdf (456 Downloads) |
4/7/2014 12:01 PM | |
Posts: 23 Rating: (1) |
Hello Sakura, don't worry, I call the support. How is it possible to rewire the FB104? I'm afraid to rewire, what happen in FB104 SWR_AG_COM? I see a FAQ that explain what I do but I'm not sure how to do, can you help me? Step by step if possible, see attachment Attachmentrewire.pdf (484 Downloads) |
4/7/2014 4:59 PM | |
Posts: 23 Rating: (1) |
Hello, I supposed the same problem and I tried with end address 30 but I have the same error, is it wrong? |
Last edited by: valerio.albo at: 4/7/2014 5:17 PM |
|
Follow us on