Can you give a bit more details on your setup and how you have implemented the connections?

I am using RPI 3B. May i ask which runtime you installed on your RPI. Is its Codesys Control Runtime for Linux ARM or for raspberry?

@@brightersidehacks Codesys Control Runtime for Raspberry PI. Version 4.14.0.0

You should use the GPIOs_A_B device module. All pins are reserved for the different interface so you cant use them for anything else. The GPIOs_A_B reserves 12 pins are Digital IOs and i am certain it should work for RPI 4

It should actually connect. Sometimes you may use a Modbus TCP Master to Troubleshoot but it is not necessary. I wonder why its not working for you. Can you provide more details about your setup and code as well?

Sure, i will soon make a Video with the ESP32 as well.

ok, let me know if you have any questions

Printers have special templates that you use to send commands. If you are using the correct template, then it should work.

Hello, i will do a demonstration on this soon. Regards

You can try to change the PLC name. Use a name with no special characters

Hi, you can find the numbers from the Raspberry Pi pinout diagram

You can watch the video here: kzbin.info/www/bejne/j6eooJh8qtyDitk

@@brightersidehacks thank you, though i might be a little confused. Do i need an actual modbus license for this to work?

In production, you need a license, but you can use a trial license to test it out. By default, all fieldbuses can be tested in Codesys without need for license. Trial License lasts 2 hours. You need to restart the runtime for another 2 hours trial period

Here is the link: us.store.codesys.com/codesys-iiot-libraries-sl.html

You can get the sample project from here : github.com/brightersidetech/rest-client-codesys

Two questions 1. Does your controller have a device user management account? 2. Do you have access to your Codesys Runtime config file? Also could you mention which controller you are working with?

Thank you

Glad you liked it

Hello can you give more details about your setup, which PLC you are using, MQTT client parameters, broker address, topics and things of the kind so that we know how to help you

​@@brightersidehacksFYI, I'm using Advantech AMAX-5580. As for the codesys setup, I follow exactly your video.

Is your PLC connected to the Internet? As you can see in the video, we are using a remote broker only accessible if you have internet

@@brightersidehacks Yes, currently my PLC connected directly to the router switch with internet connection. I already logged into the PLC to check the network and everything is fine. I can even play KZbin videos using Chrome inside the PLC. I also already try to use it in wireless mode but the results are still the same. Weird😕

To me this sound like you are trying to reach a broker but either the host name is not correct or you cant reach that broker. Can you try using the ip address instead of the broker host name?

Yes, it is possible since both are ethernet based but independent protocols, they can co-exist over the same infrastructure

Its the IP address of your computer

Thanks, more to come

You can find it here: forge.codesys.com/prj/codesys-example/http-client-exa/home/Home/

Hello, for Mobile apps connection to industrial controllers, i think the best protocols i would would recommend are REST, Socket or MQTT, if you are working with wireless communication, and also since they are easy to setup . For wired communication, i would add serial but this is already a secondary option. But also, it may depend on which programming language you are using for your mobile app implementation and also how easy it in for you to interface with these protocols I hope this helps. Good luck

I think this was covered in the video

Yes, it will work

If your node is of type float, then it will treat the data received as a float, and same thing with a double. You should not have any issues.

Yes you can, same steps

The VFD simulator is free for download from the Yaskawa website

@brightersidehacks thanks so much gor your prompt response

Hello, In this tutorial, the server is the PLC running Codesys and the client is a UaExpert.. You don't need any xml files for this

What error are you getting?

@@brightersidehacks I too have the same issue. Using a Raspberry Pi 5. Getting Error 39. I'm guessing access to the Linux root folders has been locked and needs to be enabled in the CODESYSControl.cfg or CODESYSControl_User.cfg files? I'm not an expert and don't know what needs to be done though.

Nice, glad you like it

You need to get device description files for your PLC . heck out this link, it might help: extranet.epec.fi/Public/Manuals/EPEC_Programming_And_Libraries/index.htm#t=projecttopics%2FTopic314.htm

Glad it helped. About the difference, yes, Codesys Runtime for Linux ARM can be installed on any Hardware running Linux with an ARM Arch, but Codesys Runtime for raspberry pi is dedicated to only raspberry Pis. Another difference id that Codesys for Raspberry pi comes with device descriptions for raspberry specific devices and interfaces such as I2C, SPI and others, but these may not be available for the one for Linux ARM. But since Codesys for ARM is a generic runtime, you can develop your own device descriptions to interact with any interfaces that your hardware might have, making it more flexible. The last and maybe most notable difference is that there is no trail license for Codesys For Raspberry pi, so you cannot try it out before buying, which is not the case with Codesys Runtime for Linux ARM

Hello, is your custom made server based on Flask? What library are you using?

​​​@@brightersidehacks Hello, yes i am using Flask Library and also HTML for frontend. Also thank you so much for the reply. ❤

@@JudishXavier-t2n I really can do much here in the comments, send me an email, we can setup a session and go over the details together, regards

@@brightersidehacks Hello, I have sent you a email. Thank you

I will do that soon