[PDXATS]

I have been working on doing some energy dashboard integrations on an LVIS ME215 but the Loytec only responds to requests every once in a while. I am using the Loytec as a Slave with a Field server as master and neither RTU or TCP seem to be functional. Using Modscan for verification and sniffing packets with no success

Anyone has success or experience with the LVIS and modbus?

 

[381engineer]

What is your Loytec support case #?

 

[PDXATS]

2016031717000241

 

[381engineer]

I've never had issues with Loytec support. Did they reply to the initial request? What did they suggest?
I have used the Lvis modbus interface with the lvis as the master with no issues. Modbus can certainly be hit and miss setting up, sometimes it goes easy sometimes not. Have you tried the internal Loytec modbus scanner, if you can't read data with it the problem is most likely not in the lvis.

I'd suggest resending a back up of the project to see if they can duplicate the issue.

 

[PDXATS]

They did respons to the orginal request but nothing since.

The RTU sniffer only works if its a master and we are using slave. It appears the device on TCP will not stay in slave mode either. Thank you

 

[381engineer]

I'm assuming as a slave you can read and write to the registers you create on the lvis but not read and write to other devices. I'll read up when I get to my pc.

 

[381engineer]

I'm assuming as a slave you can read and write to the registers you create on the lvis but not read and write to other devices. I'll read up when I get to my pc.

I kind of got that mixed up.
A modbus slave only responds to requests from a master. If you are trying to visualize data from other devices on the LVIS then it will need to be the master.

 

[amigo]

I think he is trying to write data to the LVIS so it can be displayed and interacted with. He probably has some other PLC that is getting metering data from somewhere and is the master on the network, so he wants LVIS to be the slave.