Reading Registers on AB7072-B from PLC

[anonuxzisrfy]

Hello,

I had recently set up an AB7072-B so I am able to write weights to the registers from a PC application via RS-232. I am doing a consume and it is set up to receive 6 words, then a comma, then 6 more words.

I am able to see myself writing data to the gateway by using the logging feature.

My customer is trying to read this via PLC and we’re not sure what address to start reading at? He says he’s expecting a 30,000 number or a 40,000 number and I’m not sure where I find that information. On my configuration, it says the data location is 0 for the first weight and 6 for the second weight.

I’ll attach my configuration and the log of my data. I’m supposed to have a call with them this afternoon, so I’m hoping to hear back by then if possible.

Here is my previous post if you want to reference what we did there:

AB7072-B Setup Questions

I’m looking to set up my Anybus Communicator (AB7072-B). I’ve got a pc that I’m connecting via RS-232 and a PLC that I want to connect via Modbus-TCP. Essentially, I want to transmit two values between the computer and the PLC. The RS-232 string can be formatted however we need it to be, but currently it’s setup two transmit two weights seperated by a comma (Weights up to 6 digits each). So, it looks something like this: “100000,145000”. Are there any guides to walk me through this or coul…

Thanks a lot!
Zach

101718.cfg (16.0 KB)
Log - 101818.txt (24.7 KB)

[deryck_hms]

Hello Zack,
I have been working with your end customer a few time to get some modbus issues resolved but he was still not seeing any data. After further trouble shooting with him it appears that the consume transaction is not actually reading in data.

@anonuxzisrfy

I am able to see myself writing data to the gateway by using the logging feature.

This only would be verifying the serial settings are correct. The log shows all data that is being read into the communicator and not just what is consumed based on your transactions. To see what is consumed you can look at the node monitor. This will show you the Bytes in HEX that have been consumed and are in memory. This is the same data that is available on the Ethernet interface.

It looks like your consume transactions are not actually consuming data. This could be an issue with the layout of the data or possibly some issue with timing. A common issue is that message delimiter timing for the subnetwork is to short. Try increasing it from 100 to 300.

Deryck