Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - CPJLS

Pages: [1]
1
Support Questions / Re: Writing floats/reals to Omron PLC
« on: August 23, 2019, 04:15:33 AM »
Great news, I look forward to it!
Thanks Archie.

2
Support Questions / Writing floats/reals to Omron PLC
« on: August 22, 2019, 07:31:33 AM »
Im am struggling with writing REALs to an Omron CJ2 PLC.
I have managed to get around the issue of reading them by using the '@F' suffix on the read addresses.
This doesnt work for writing though.

Anyone have any ideas how this can be done?
It's really casuing a major problem not being able to write any decimal numbers.

Thanks

3
Support Questions / Re: OmronEthernetFINSCom to CJ2M PLC problems
« on: June 10, 2019, 04:41:26 AM »
Works perfectly now! Thanks very much!

4
Support Questions / Re: OmronEthernetFINSCom to CJ2M PLC problems
« on: June 07, 2019, 08:57:59 AM »
I've reset all data areas on the PLC and re-initialised to factory settings.
I set the IP address of the PLC and PC to be the same as in your example.
Attached are the 2 wireshark traces, one with node address set to 0 in the VS control and the other set to 30.
Different error messages being returned for each then with the previous examples.

I'm using 3.99r1 and I created a new copy of the project from the zip and built it from scratch to eliminate any errors from there.

Thanks

5
Support Questions / Re: OmronEthernetFINSCom to CJ2M PLC problems
« on: June 06, 2019, 12:22:04 PM »
Thanks for the quick reply.
Changing to 201 gives the same error and same result in wireshark.

6
Support Questions / OmronEthernetFINSCom to CJ2M PLC problems
« on: June 06, 2019, 10:58:16 AM »
Hi,

I follwed the initial setup instructions but can't seem to get any communication via UDP to a CJ2M plc over ethernet (OmronEthernetFINSCom).
Tried various changes to the node table in CX programmer and setings within VS2019. I think they are correct as any changes away from the current setup result in EIP transport errors.
Wireshark (trace attached) shows a 0x2108 (write not possible) error being returned.

Anyone have any ideas?

Thanks

Pages: [1]