Activity for AlfredoQuintero
-
AlfredoQuintero posted a comment on discussion Engineering 🇬🇧
Well, great.
-
if you post your project I can have a look at it. Can/t tell with the description only. Or at least post a screenshot.
-
No problem. Let/s hope the project goes smooth from here.
-
This is good. If the process tolerates it, if you increase the RPI (requested packet interval) this would also easy CPU use, because the EtherNet/IP scanner stack will be executed with less frequency, which should help with the CPU use. Edit: I see, do you mean by "increasing the time" increasing the RPI? if so, your solution is what I am explaining. Good to know you fixed it.
-
This is good. If the process tolerates it, if you increase the RPI (requested packet interval) this would also easy CPU use, because the EtherNet/IP scanner stack will be executed with less frequency, which should help with the CPU use. EDIt, I see, do you mean by "increasing the time" increasing the RPI? if so, your solution is what I am explaining. Good to know you fixed it.
-
This is good. If the process tolerates it, if you increase the RPI (requested packet interval) this would also easy CPU use, because the EtherNet/IP scanner stack will be executed with less frequency, which should help with the CPU use.
-
Brazadio, por favor revisa la captura gráfica anexa. CODESYS te reporta estaus 0x01 y estatus extendido 0x203. Como te muestor en el extracto de la especificación CIP, este estatus extendido siginifica que el adaptador deja de comunicarse con el scanner CODESYS. Yo no creo que esto sea problema de CODESYS. Puedes estar teniendo problemas con el adaptador o con el switch. Tienes que tomar capturas con Wireshark para ver por qué termina la conexión.
-
Hi: I am using the latest CODESYS SP 19. I added one GSDML Profinet device file without problem. But, when I try to buidl the project, the compilation process ends in error with "The identifier 'min' is not a valid IEC identifier. Please change the device description." I have tested the device description in the Profibus Profinet International's GSDML checker and the check passes without warning. So my conclusion is that the GSDML file is standard. Attached I show the error as well as the GSDML file....
-
Hello Brazadio: Status 0x01 means connection manager error in EtherNet/IP. Extended Status 0x203 for Status 0x01 means connection timeout. For some reason the EtherNet/IP adapter stops communicating with the CODESYS Scanner. I do not think the probelm is in CODESYS, rather, ti seems to be that either there is a problem with the switch or cabling, or the EtherNet/IP adapter has a problem. Please see attachment. I think you need to take Wireshark traces to figure out the problem.
-
OK, here is the screenshot, with comments, of the error...
-
Hi: I am suing the latest CODESYS SP 19. I added one GSDML Profinet device file without problem. But, when I try to buidl the project, the compilation process ends in error with "The identifier 'min' is not a valid IEC identifier. Please change the device description." I have tested the device description in the Profibus Profinet International's GSDML checker and the check passes without warning. So my conclusion is that the GSDML file is standard. Attached I show the error as well as the GSDML file....
-
Hi: I am suing the latest CODESYS SP 19. I added one GSDML Profinet device file without problem. But, when I try to buidl the project, the compilation process ends in error with "The identifier 'min' is not a valid IEC identifier. Please change the device description." I have tested the device description in the Profibus Profinet International's GSDML checker and the check passes without warning. So my conclusion is that the GSDML file is standard. Attached I show the error as well as the GSDML file....
-
Hi Takeshi, not sure what you are trying to do.Can you post the EDS file for the adapter? And also if possible the two projects only with EtherNet/IP IO configuration. I do not need the logic.
-
This is very useful. Thanks for posting the solution.
-
spfollen, the only work around I could find was to install the 0x86 (32-bit) version, even though the PC is a 64-bit system. The 32-bit version solves the problem. I found this happened when I installed a completely unrelated software on the same PC, the engineering tool from a different PLC maker. I hope this is a solution for you too.
-
Also Have this installation problem when attempting to reinstall package
-
Hello. I updated Windows 10 on several PCs where I was using CODESYS with no problem. Now I cannot save projects on this PC. Tried to reinstall the CODESYS package and have compatibility package installation. Will be grateful for comments and advise.
-
Has anybody used Codesys as a Windows Profibus master using Softing's Profi USB master board? I can7t find documentation and I am unable to get the program working. A sample project showing how to initialize the USB board would be helpful. I am familiar with the Softing API, but cannot get the program to work. Although the library for the ProfiUsb is installed, I get "Unresolved reference" error. I am using Control Win V3 as this driver does not support 64 bit.
-
Has anybody used Codesys as a Windows Profibus master using Softing's Profi USB master board? I can7t find documentation and I am unable to get the program working. A sample project showing how to initialize the USB board would be helpful. I am familiar with the Softing API, but cannot get the program to work.
-
Hello i-cambell, thanks very much for this information. I am not fully understanding your explanation. I will be grateful for your patience. What do you mean to export the Device description of an EtherNet/IP adapter. Normally, when you use the Codesys as an EtherNet/IP scanner you have to import the EDS file for the EtherNet/IP adapter you want to communicate with. In the opposite use case, you configure Codesys as an EtherNet/IP adapter and you export the EDS file so the Codesys adapter can be...
-
Hello. I have sued in the past the Codesys as an EtherNet/IP adapter, and it is a very good solution to communicate with other PLCs which have EtherNet/IP scanner function. I have a customer who develops applications on an EtherNet/IP scanner capable PLC which has tenths of robots and the problem when developing his logic is that usually he does not have all the IO as it is a line which costs millions of Euros, so very few chances to test his logic with all the IO. Using Codesys EtherNet/IP adapters...