[Signature Log Checksum]

Hello everyone.
I'm looking for a way to certify that a program running on a PLC is the same as some project file (.vlp).

Some type of signature CRC.

The tool "VisiDiff" doesn't support V130 nor V350. (the two versions that I use)

I've found an SDW value tagged as "Signature Log Checksum", that I think is the key that I need, but this value is always 0, and the help doesn't say anything about it.

Can anyone help?

 

Regards, Javier.

[Reuse Socket]

Yes Flex, The solution is as simple as this:

[Reuse Socket]

SOOLVED!!!

Looking to the problem, I've tried to set the protocol type manually, and YES! It works!

After initializing the socket, I set the socket protocol manually in 0.

Starts the synchronization, and it works.

There is no need to close the socket. I think that closing the socket only got effect on TCP MASTER connections.

If you are interested, you can find the details attached.
Thanks everyone!

Solved.pdf

[Reuse Socket]

Aus: Thanks for your answer!
You are right on this. I normally play with instruction orders, or I use a label to go to end of ladder when launching or modifying a connection. The PLC executes the communications at the end of ladder scan. So, I force it to do this before evaluating any connection condition.
In this case, I am in test stage, so I´m using manual flags to run any single rung. This assures to avoid any timing trouble.

[Reuse Socket]

Flex: Thanks for your answer!

Going a little deeper, the application normaly uses this socket for modbus comm as slave. In some conditions, I need to use this socket for a time synchronization. For this second use, I need the connection as UDP, and don´t have any modbus config to define.

All I can do is stop the modbus listener rung...

...close the socket...

...and initialize as UDP.

 

[Reuse Socket]

Hi everyone!

I´m using the four sockets in a Vision 130, and I need more!

So, I tried to redifine a socket in run time according to some conditions, but I find out that once the socket was defined,  I can´t redefine it.

The socket is first initialized as TCP / Port 502 / Server. A Modbus IP configuration is attached to this socket, and running as Modbus IP Slave.

 

Then, I close the socket...

...and redefine it as UDP

The result is that the socket never loose the Modbus definition, and can´t connect via UDP.

When the second socket definition is executed, the socket state goes from 20 to 34.

 

If I insert a reset of the PLC before the second definition, all runs correctly.

So, I think that the only way to "release" the socket definition is restarting the PLC. Is this right? Or (more likely) I am doing something wrong?

 

Thank you very much!!

[Modbus Configuration - Indirect Slave ID Declaration]

Yes, I did that manually, using a pulse in parallel with power-up bit that I set in run time.

I realized another thing during this: The IP and port setings in Modbus configuration have no effect! The communication uses the socket settings, regardless of Modbus configuration. The only one parameter that uses from configuration is the ID.

[Modbus Configuration - Indirect Slave ID Declaration]

Yes. Just using direct assignment in SLAVE ID and all other parameters as they are, and communication is fine.

The issue is clearly related with indirect assignment in SLAVE ID. Not in IP adressing.

[Modbus Configuration - Indirect Slave ID Declaration]

Hi everyone.

I tried to use a MODBUS configuration using an indirect declaration of SLAVE ID, but didn't work. (see example in index 2 and 3 below)

If I declare the SLAVE ID in a direct way, all OK.

My problem is that I have to read several slaves from the PLC, and is realy hard to do with a fixed Modbus configuration.

I am using a V130 in revision 9.6.0.

 

Thanks in advance.
Regards, Javier.

P.D.: Sorry if I posted this twice. I couldn't find the first post.

[Modbus Configuration - Indirect Slave ID Declaration]

Hi everyone.

 

I tried to use a MODBUS configuration using an indirect declaration of SLAVE ID, but didn't work.

(You can see an example in index 2 and 3 of the attached image)

If I declare the SLAVE ID in a direct way, all OK.

My problem is that I have to read several slaves from the PLC, and is realy hard to do with a fixed Modbus confifuration.

I'm using a V130 in version 9.6.0.

 

Thanks in advance.

Regards, Javier.