11/22/2023 10:13 PM | |
Joined: 8/29/2023 Last visit: 11/23/2023 Posts: 6 Rating:
|
Dear experts, I'm trying to establish a modbus tcp pn redundant communication between 2 H-systems.(CPU's are 410-5H) I'm having issues with the connections, which are currently not established indicated by A0FF status code. I think this would be due to the local_tsap_id & rem-tsap_id. I used default values from an example project but I'm afraid I'll have to change them according my configuration? According the manual, I'm supposed to use the high byte of port no. in hex display, for local_tsap_id[1], and low byte of the port no. in hex display for local_tsap[2]. Am I supposed to find this information in the hardware configuration? How does this low and high byte separation work? Also, local_device_id is supposed to be B#16#5 for 400 H CPU, and B#16#15 for the CPU in rack 1, but when I used the modbus TCP PN RED wizard, it filled in 8 & 18. Am I missing something here. As for the id_0_a / id_1_a / id_0_b / id_1_b, am I supposed to just choose any ID's here, or is this linked to anything in the hardware configuration as well? Currently I used 1,2,3,4 accordingly in both MB_PNHCL (see 1st page of attached pdf) and MB_PNHSV. In the attached pdf, you can find find some of the client parameters on page 3, and server parameters on page 4. Feel free to comment if you find any issue that is not related to what I explained above. Hoping for some help! Attachmentparameters.pdf (333 Downloads) |
Follow us on