About CodeShepherd

CodeShepherd · ‎03-08-2021

I will send you a private message please contact me directly.

CodeShepherd · ‎03-08-2021

Please stay tuned to this thread.

CodeShepherd · ‎03-05-2021

Your engineering PC as well as the ctrlX CORE (in standard XF10) have to be connected to the internet. The IP can be static but mus fit to your local subnet of your router or like descriped above a gateway could be used.

CodeShepherd · ‎03-05-2021

So where is your ctrlX CORE coming from? Did you order it from Germany with the 1.6 Version installed? Did you do any updates via image on your own (then certificates are deleted)? It seems that your certificates are missing that are needed to claim this device. You can check this here: Each Device from our production line has this files and is able to be claimed. So there are quite no more information.

CodeShepherd · ‎03-04-2021

After checking your last information it seems, that you opened the WebInterface of the ctrlX CORE via the IPv6. At the moment this ip is directly copied to the target setting in the engineering and these tools cannot use it. So actually you have to insert the IPv4 by hand in this constellation. If the error will stay, please open your WebInterface of the ctrlX CORE via the IPv4 and open the engineering from there. Could you check this two possibilities please and tell if it working at your side? There will be some improvements in the next release RM21.03 (version 1.8.x).

About CodeShepherd

Re: Device Portal connection instructions needed for Remote Agent - 1.6.1

Re: OPC UA - Which variants are available?

Re: Sample Node Red Dashboards

Re: Device Portal connection instructions needed for Remote Agent - 1.6.1

Re: ctrlX I O : exception when saving