Activity for snguyen

  • snguyen snguyen modified a comment on discussion Engineering πŸ‡¬πŸ‡§

    Hi, I do not know if there is a specific library for this, but you can run linux command line from CodeSys, meaning you can call your python script too. First, you need to edit a codesys file in the RPI to allow codesys to run command lines : sudo nano /etc/CODESYSControl.cfg in the file "CODESYSControl.cfg", add this : [SysProcess] command=AllowAll Then, in CodeSys, you need the have the SysProcess library in your project. You can then call your python script as follows : commandString:STRING:='python...

  • snguyen snguyen modified a comment on discussion Engineering πŸ‡¬πŸ‡§

    Hi, I do not know if there is a specific library for this, but you can run linux command line from CodeSys, meaning you can call your python script too. First, you need to edit a codesys file in the RPI to allow codesys to run command lines : sudo nano /etc/CODESYSControl.cfg in the file "CODESYSControl.cfg", add this : [SysProcess] command=AllowAll Then, in CodeSys, you need the have the SysProcess library in your project. You can then call your python script as follows : commandString:STRING:='python...

  • snguyen snguyen posted a comment on discussion Engineering πŸ‡¬πŸ‡§

    Hi, I do not know if there is a specific library for this, but you can run linux command line from CodeSys, meaning you can call your python script too. First, you need to edit a codesys file in the RPI to allow codesys to run command lines : sudo mousepad /etc/CODESYSControl.cfg in the file "CODESYSControl.cfg", add this : [SysProcess] command=AllowAll Then, in CodeSys, you need the have the SysProcess library in your project. You can then call your python script as follows : commandString:STRING:='python...

  • snguyen snguyen posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Hi, The new release for RPI 64-bit is pretty nice, but I can't make CodeSys work on it. First thing that is strange is that when I install the runtime, it gives me only the choice for Single core and not Multicore. It is probably due to the fact that CodeSys search for "armv7l", and the 64-bit OS is "armv8". Then, the runtime won't start because of the Bullseye "/opt/codesys/scripts/init-functions", so I fix the function with the help of a previous Thread post about this, but now it just gives me...

  • snguyen snguyen posted a comment on discussion Codesys V2.3 πŸ‡¬πŸ‡§

    Hi, I have a problem that I cannot find the solution to. I have CodeSys 2.3 installed on my computer to program IFM controllers, and I decided to download CodeSys 3.5 patch 4 from IFM's website and when I installed 3.5, the font size and type in CodeSys 2.3 changed in some place. I tried uninstalling CodeSys 2.3 and 3.5, deleted folders in %USER%/appdata and %USER%/documents, clean install codesys 2.3 only and nothing worked. I tried changing screen resolution and dpi settings. I tried resintalling...

  • snguyen snguyen modified a comment on discussion Runtime

    Hi, I have a subsequent question on multicore. In the manual, it is stated : - Bit access (data type BIT) is not processed consistently on marker CPUs in the IEC program. For this we recommend that you use the external library function SysCpuTestAndSetBit() (for more details, see SysCpuHandling.library). - Simple data types up to a width of 32 bits (BIT, BYTE, WORD/INT, DWORD/DINT, etc.) are processed consistently in the IEC program on marker CPUs as well. So I was wondering what that meant. Does...

  • snguyen snguyen posted a comment on discussion Runtime

    Hi, I have au subsequent question on multicore. In the manual, it is stated : - Bit access (data type BIT) is not processed consistently on marker CPUs in the IEC program. For this we recommend that you use the external library function SysCpuTestAndSetBit() (for more details, see SysCpuHandling.library). - Simple data types up to a width of 32 bits (BIT, BYTE, WORD/INT, DWORD/DINT, etc.) are processed consistently in the IEC program on marker CPUs as well. So I was wondering what that meant. Does...

  • snguyen snguyen posted a comment on discussion Runtime

    I've updated to 3.5.16.10 and it works.

  • snguyen snguyen posted a comment on discussion Runtime

    It is 3.5.15.40 MultiCore Info: -- MultiCore support: [activated], all cores are used -- Number of cores: 4

  • snguyen snguyen posted a comment on discussion Runtime

    Hi, I'm trying to use the raspberry pi Multicore, but it does not let me create tasks on different core. It says I don't have the license. What I did : - Task Configuration -> Add group = NewGroup on Core 1 - Task Configuration -> add task to NewGroup I need the functionnality because I need to send email with a python script but the script takes 650ms and I don't want to block the rest of the program. Also, I'm not using the Mail functionnality of the IIoT library because it does not let me choose...

  • snguyen snguyen posted a comment on discussion Runtime

    Hi, do you have any news :) ?

  • snguyen snguyen posted a comment on discussion Runtime

    Thank you

  • snguyen snguyen posted a comment on discussion Codesys V2.3

    Hi, can't write the code for you, but here's how to do it. Create a bool that is going to be turned on by the first sensor and off by the second. Create a timer (TON) and tie the input to the bool variable. When the timer stops, the variable "ET" (elapsed time) will give you the time between the on and off of the timer. You can then correlate the distance and time together.

  • snguyen snguyen posted a comment on discussion Runtime

    Hi, I currently need to send mail through the IIoT library and it works well with GMail, but I can't get it to work with our mail server. Monitoring Wireshark, I've successfully sent mails with our server using python smtplib. It uses TLSv1.2. When I send email with the codesys library using our server, it uses TLSv1 and fails. However, when I send mail with the codesys library using gmail, it uses TLSv1.2 and works. Does anyone have a clue why the library automatically chooses TLSv1? Maybe I can...

1