FORUM | LATEST POST | # TOPICS |
---|---|---|
General Discussion Forum about anything you want to talk about. |
No posts yet | 1 |
Not connected, but found using: Scan for Devices
The problem is looking for a bug somewhere in CoDeSys in that, when the slave returns, the cyclic data exchange resumes, but the diagnostics do not update and the node continues to resulting off-line. it is not a problem with the PB master, but with its 3S/CoDeSys management. CoDeSys 3.5.19.20 runtime. Any ideas on how to fix it? Thank you.
The problem is looking for a bug somewhere in CoDeSys in that, when the slave returns, the cyclic data exchange resumes, but the diagnostics do not update and the node continues to resulting off-line. it is not a problem with the PB master, but with its 3S/CoDeSys management. CoDeSys 3.5.19.20 runtime. Any ideas on how to fix it? Thank you.
Hello @eschwellinger, I have tried version 4.13.0.0 and the same thing happens to me...
seems a bug in 4.14.0.0 version
WHEREAS, I have already searched various posts and forums, where mostly there are few references and mostly geared toward integration in TwinCAT. I am looking for how to properly configure the EL6731 board as a DP master, (where I have its 3S license), with CoDeSys 3.5.19.x. I have three types of slaves, all integrated with their GSD descriptors. In the tab for the various slaves, I don't see options related to node restart on 'station return'. On the card manual, I read that for each slave I should...
Hello, When I add 2 nics in vPLC this happens to me..., why is it? If I just put one of the two NICs, the vPLC runtime instance starts running correctly...
Hello, When I add 2 nics in vPLC this happens to me..., why is it? If I just put one of the two NICs, the vPLC runtime instance starts running correctly...
I guess that the printer expects to receive an array of byte values. So where it is described that it expects to receive: Hercules String : 1B4F513030311B7532626C61636B04 it actually expects to receive an array of bytes with the values 1B,4F,51,30,30, etc. So what you can do is create an array of bytes and assign the byte value to each item in the array: VAR abyToSend : ARRAY[0..99] OF BYTE; END_VAR abyToSend[0] := 16#1B; // ASCII Escape character, hexadecimal representation uses 16# as prefix abyToSend[1]...
Hello, When I add 2 nics in vPLC this happens to me..., why is it?