I am trying to utilize the PBCL_SysLinuxShell command to execute „curl -s ifconfig.co“ from a PLCnext ladder program.
It runs fine on my demo controller. It fails with Diag Code 8300 (Function Block is Busy) on my production controller. Both are running the same 2024.x firmware. I know my demo controller does not utilize authentication, but my production controller is (not sure if that matters).
Ideas?
SFW
Hi! I suspect there is some issuers with networking at your prod controller. Curl can`t reach the site or there is some other blocking issues. Can you reach other addresses with curl. Also, does your project enables PLCnext_Base service property . The code sample will be helpful here.
BR
Also, try to use curl via console of the plc
Thank you for the response.
I can run the curl command from the PLC shell; it seems to work fine.
Here is my code. I’m not sure what you mean by „does your project enables PLCnext_Base service property.“ I added the library to the project and then added the commands to the program.
image.png
PS: I did change the site to „google.com“ and I get the same 8300 error.
Depends on version of library you use, it can be separate system task or function block to enable use of PLCNext_Base library in proper and comprehensive manner.
Please, verify this chapter of help dock, and implement initiation example if require.
BR
I am using v 1.6.4 of the PLCnextBase Library and 2024.0.3 of the PLCNE software.
Despite not having to use the PBCL_Setup block in my test machine, I attempted to add the Setup block to the prod machine.
The PBCL_SysLinuxShell block still failed with an 8300.
I think that in the past there were some issues with the PLCnext Base library not updating correctly on the controller if a PLCnext Engineer project that used an older version of the library had previously been running on the same device. In those cases the ultimate solution was to perform a Type 1 reset on the device and reconfigure the device again. That might be a drastic step (depending on how complex the application is), but if not then it might be worth a try.
Thanks Martin.
I might give that a try…however, this Production Machine is a new, out-of-box controller that has never had a different Base Library on it.
Does redirecting the curl output to a file, using the --output <file> option, maybe to a file in the /opt/plcnext directory, make any difference?
Also, just to be clear, did you use the PBCL_Setup FB in the required way, as described in the documentation?
Thank you, Martin. I rechecked my Setup logic, made a correction, and it resolved the 8300 error.
Thank you, Oleksandr.