EN2MB-R on power cycle resets Ramsey Checkweiger batch


#1

@anondgehybjs
Hi Dave,

As we spoke about, we are going to need some more information about what causes the reset (error or something in software) before we can determine if anything can be done one this end to help correct this issue, so when you find out more please respond directly to this email or give us a call back and we can go over it with you.

Thank you,

Kyle


#3

Kyle,

When we put the device into the run state, is it possible that the Modbus side could be writing zeroes to the Modbus server before the EIP side has updated the data from the PLC?

Also, are there any firmware upgrades planned for the EN2MB soon that might give us floating point support in the ControlLogix? Also, the RSLogix software crashes on editing when we’ve had the Modbus configurator open. Is that issue being addressed?

Thanks,

Dave


#4

Hey Kyle,

Would it help to change the parameter download data to acyclical as opposed to I/O mapped? If so, do you have any examples of explicit messaging to write that data? There are no examples in the user guide.

Thanks,

Dave


#6

Hi Dave,

To recap our phone call. You said the Ramsey device will only trigger if a new value is written to the registers. With the device started in idle, the transaction startup-mode set to “wait for data” and you writing the current value on the Ramsey device we should not be triggering a new batch.

I would like to see a wireshark capture of the traffic to and from the Linking device Client and the Ramsey Server. This should give us a clear understand of what modbus messages are being sent and if we are sending a incorrect message.

Deryck


#7

Do you guys have any examples of writing data to a non-IO mapped transaction using a ControlLogix MSG instruction? You mention that it can be done in the manual, but I can find no examples anywhere.


#8

Hi,

We have this document covering using message instructions to our standard X-gateway. https://www.anybus.com/docs/librariesprovider7/default-document-library/application-notes/hms-sci-1204-095.pdf?sfvrsn=a3f6aad6_15

Since we still do not know exactly what is triggering the new batch I am not sure that message instructions are going to help you here. All we know is the I recommend first identifying what message on the modbus side is triggering the new batch then working back from there.

Deryck