Beijer terminal

General Discussion
1

I'm looking for some help. Has anyone ever used a Beijer HMI as a modbus device in order to get data into ignition?

For better detail i have an older Beijer E600 terminal. There is no ethernet option on this specific terminal. I have a 422 and 232 port. The 422 port is configured to talk with the PLC. I am attempting to setup my 232 port as a modbus device to then go to a DVS-232-2 serial to ethernet converter. I can add the device to ignition using the IP of the DVS-232-2. But i am having no luck transmitting any data, it all comes back bad.

I was wondering if anyone had experience with Beijer Terminals or a similar setup like this, and if so maybe someone can help me find out what im doing wrong.

2

When serial is involved, you need Modbus RTU (true serial port on the gateway) or Modbus RTU over TCP (when using a simple converter). Not Modbus TCP. You may need to configure the ethernet converter to not mangle the RTU packets. See the appendix to my alternate driver for Moxa recommendations (applicable to IA's driver, too) and interpret for DVS.

https://www.automation-pros.com/modbus/UserManual.pdf

3

You will have to excuse me as i am still new with modbus.

But with this specific converter i am able to enable "Modbus RTU to Modbus TCP" i am going to assume this is what your referring to and i do have it enabled.

My fear is something i may not have correct on the side of the Beijer Terminal. I setup the second controller to be a modbus RTU slave, and setup a simple address to try to bring into ignition. But on the serial side of the converter i am receiving no TX or RX activity. But from what i have been able to find on this older terminal i should have everything correct.

But obviously i am doing something wrong.

4

You may need to specify a unit ID on your addresses instead of allowing the default of 0 to be used.

e.g. an OPC Item Path that looks like [MyDevice]1.HR1

5

I came across that before and like you said yes i needed to specify a different unit ID, in that case it was 1. I tried 0,1,2 and so forth with zero luck.

6

Sorry, no experience with this hardware, not sure what else to suggest.

If you can get any other Modbus client software (modscan, modpoll, etc...) to communicate then it should be pretty easy to figure out what's different between the settings.

1 Like
7

Yeah i've brought other modbus devices into my system before. These are all Modbus TCP devices, i think where my downfall is now is this is Modbus RTU. I have no experience with this platform, specifically these Beijer Terminals and the DVS-232-2 device.