RE: New form entry is submitted - Call Back Form - North America

[anon8472635233]

Hi

Thanks for the reply. I have tried to explain the issue below:

I have configured a broadcast on “Change of state of trigger” on address 0x220. Then I have configured Kepware Modbus TCP driver to read/write to address 401041.

Here are my questions:

HuberDriver.cfg (16 KB)

[deryck_hms]

Hello Thomas,

Looking at the configuration you do not have any output data configured, only a few randomly placed trigger bytes
0x206 transaction 2 query trigger
0x220 broadcast trigger
0x5FF transaction 1 query trigger (this one is in the general memory section and is not accessible.)

You also have a single variable data object 3 bytes long set for the response of transaction 1.

@system

I have configured a broadcast on “Change of state of trigger” on address 0x220. Then I have configured Kepware Modbus TCP driver to read/write to address 401041.

Here are my questions:

1. I can write 0, 256 and 512 via Kepware to the Modbus tag in the ABC, but none of the value in between, is that a feature or bug?
2. When I write 0, 256 or 512 to that register, then my broadcast command is send via serial 4 times. Can I change that to only send it one time?
3. Protocol send ascii floats. Is there any way to convert that to float?

I tried to change to produce/consume, and then everything is working perfectly, but I need read most of the data via request/response. I’m I doing something wrong?

I think you are running into write issues since you are writing 2 bytes with the modbus write and the second byte is outside the configured memory range on the communicator.

I am unsure why it is sending the broadcast more then once. I tested you configuration on a device here and it only sent it once. Are you witing all three of those numbers? each write would trigger the message.

I am not sure what format an ascii float would be. Is it sending the number in ascii format?. The communicator only copys the data byte for byte and can not do any conversions besides byte swapping. You most likely will need to handle this on the field bus side.

Deryck

[system]

Topic closed due to inactivity.