Prosoft MVI56E-MNETC w/ CLX

[Pdell]

Controller: 1756-L84E v.35
Prosoft MVI56E-MNETC for ModbusTCP/IP

I'm having an issue with some of my write commands. The write command that I'm using individual bits within 1 word for an "enable", "start", "stop", etc will not work. If I'm writing lets say a setpoint for example 700DEGF it will write that value to the module

To see if it was a module problem, I used Mdbus to write to the specific control word and I'm able to "start", "stop", etc. so I know its a problem with the configuration in Studio5000 or Prosoft Configuration builder.

I also set the MNETC.CONTROL.CmdControl.WriteCmdBits to 1111_1111_1111_1111 to ensure all of the commands are enabled.

Enable YES
Internal Address 20
Poll Interval 0
Req Count 1
Swap Code No Change
IP Nunya
Serv Port 502
Slave Addr 1
*****Mdbus Func FC3 - Read Holding Registers *****
*****(I question this but it worked using Mdbus for troubleshooting)*****
MB Addres In Device 4311 (device end is 4312)

Diagnostics has NO errors.

I'm confident that what you might call "basic configuration" would be correct.

What could I be missing here?

 

[AREDA]

Given it's been 9 months, I guess you have it sorted?
I might have missed it between the lines, but are you writing from CLX to 3rd party or writing to CLX from 3rd party? As you said FC 3 infers you are reading from Slave, guessing should be FC 6 or FC 16.
If it is indeed the other way around (reading from 3rd party), try setting Device Address to 4310 and read 3 registers (might be an offset thing)

 

[Pdell]

Given it's been 9 months, I guess you have it sorted?
I might have missed it between the lines, but are you writing from CLX to 3rd party or writing to CLX from 3rd party? As you said FC 3 infers you are reading from Slave, guessing should be FC 6 or FC 16.
If it is indeed the other way around (reading from 3rd party), try setting Device Address to 4310 and read 3 registers (might be an offset thing)

Oh my gosh, amazing somebody actually responded to this!

It actually turned out to be a control narrative that the device had which was causing our commands to not work. You couldn't issue the Enable Modbus and Start Commands to the controller at the same time. We had to add logic so that when the Enable Modbus is true, THEN command to start.

This controller we had was an absolute nightmare to work with, we had to reverse engineer just about everything because there was no manual online and the manufacture couldn't find one either.

Thank you so much for taking a stab at it!

 

[AREDA]

Glad you've sorted it out, and thanks for sharing the details.