I am currently investigating this problem as I have tried all the above to no success yet.
I am currently investigating this problem as I have tried all the above to no success yet.
Eschwellinger, what is the work around if "net start CmpDrvSchedulerAMP" returns the details below?: Stop Code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED What failed: CmpDrvSchedulerAMP. This is after the steps 1 and 2 you mentioned above were successful. Thanks.
Hi Androidzz, No luck so far. I am looking into using Mosquitto as a broker and using the Linux VM on the AWS as an alternative. I will let keep you posted should anything change.
Hi Androidzz, No luck so far. I am looking to using Mosquitto as a broker and using the Linux VM on the AWS as an alternative. I will let keep you posted should anything change.
Hi Rdcoulton, Thank you for your prompt response. I have and had the AWS Device certificate in the "Own Certificates" in the Device Security Manager. I however made the rest of changes that you recommended and my "xbusy" communication status has graduated into an "xError." I made changes to the Policy attached to my "thing" in the AWS server for a more open access per your suggestion as well. I am yet to make a valid error free communication yet. I really appreciate you for taking the time in looking...
Hello Androidzz, I am having a similar problem with connecting to the AWS server from Codesys (Codesys V3.5 SP17 Patch). I am using the AWS IoT Core Client Example as a means of connection to the server. I followed the same guide as the one posted by J-Campbell above. I created the certificates per the guide and I cannot seem to establish a connection to the server (I am getting a busy response). I have attached a copy of my certs in CODESYS and my setup in the PLC_PRG for reference. I am really...
Hi Edwin, I am having the same problem as Nosi described in an earlier post. I constantly get zeros in the read buffer when attempting to read from the COM port after making the changes below to the /etc/CODESYSControl_User.cfg file [SysCom] Linux.Devicefile.1=/dev/ttyACM0 - this is communication port for the motorcontroller (Octopus Pro controller). I am able to successfully write from Codesys (V3.5 SP17 Patch 3) to the motor controller, but reading from MC is proving to be a challenge. I can read...