Communication Codesys V2.3 and V3 usin CANopen

Cuno61

Member
Join Date
Aug 2010
Location
Netherlands
Posts
5
Hey guys,

I used to have a PLC and a HMI from ifm. I programmed both of them in v2.3 and used network variables over CAN.

We switched to another PLC and HMI from TTControl. The PLC can be programmed in v2.3 and the HMI with v3. I looked up network variables in v3 and it seems to be supported, but only over UDP. When I want to use CAN it gives me a warning stating: Network protocol not defined in device description.

I can't seem to find the settings for adding CAN as a network protocol. Has someone ever used CAN for communication between codesys v2 and v3? I tried adding a canopen slave in v3, then exporting it as an eds file and then importing it in v2.3. It didn't seem to work (everything stayed 0).

Also, after importing the EDS file, i could not communicate with my encoder on the same CAN.
 
Under the Resources tab select: Target Settings there is a Tab called Network Functionality. Mark "Support network variables". Should worb between 2.3 and 3 as long as the hardware supports it.
 
Under the Resources tab select: Target Settings there is a Tab called Network Functionality. Mark "Support network variables". Should worb between 2.3 and 3 as long as the hardware supports it.

MrQ,

I already have this option enabled in v2.3 but I can't seem to find it in v3. How can I enable network variables in V3 using CAN.
 
Does you HW really Support CAN?

Then It should be no problems. The help file even decribes in detail setting upp comm between 2.3 and 3. Just search for "network variables".
 
I think (I hope I'm not wrong), V3 doesn't support CAN network variables, it supports only UDP network variables.

You have to write your own mechanism in order to communicate between v2.3 and v3 via CAN.
 
Djuro Emedji,

You are correct. V3 does not support network variables over CAN yet. I contacted the manufacturer and they told me it is not supported in v3 (yet?). They asked 3S but they couldn't tell when or if it will be supported in the future for v3.

I did however make the communication work between the 2 projects in v2 and v3. To accomplish communication, you have to create a CAN local device in the v3 project. Edit he I/O area and then generate the EDS file. Import that EDS file in v2 and configure the settings. Afterwards, you should be able to communicate over CAN.
 
It's been 8 years, think CoDeSys supports CAN variables yet? If so how do I communicate CAN variables between a V2.3 project and a V3.5 project? If not, how do I setup the local CAN device?
 

Similar Topics

Hi Guys, I am trying to establish communication over profinet between Siemens S7-1200 PLC as IO device and codesys plc as IO controller. But I am...
Replies
39
Views
2,054
Hi there, I have a standard PLC, that seems like uses Codesys to program. The PLC is a HMI/Controller that runs on windows embedded. I could...
Replies
4
Views
2,172
Dear all, I am a newbie to CoDeSys and I need to establish communication between CoDeSys and non-CoDeSys platform. I came to know that to...
Replies
2
Views
2,742
Hi, I would like help if possible with a little problem. I'm using a TM251MESE from schneider electric with Somachine 4.1 sp2. I'm trying to...
Replies
0
Views
2,012
Hi 1-I have a HY-TTC90 ecu.I can connect to it with TTDownloader and peak-usb but when I want to connect to it with codesys ,the following error...
Replies
1
Views
2,635
Back
Top Bottom