I've done plenty of PI / PID loops with Danfoss controllers but not something with such a long delay in the feedback.  Does the gate just move very, very slowly, or does it actually take 30 seconds before your controller is sent the position of the gate?  Does it get new feedback every 30 seconds only, or is it continuous feedback but 30 seconds delayed?

The PID loop has a sample time input, and the highest value is 32,767 ms.  So, haha, perhaps you just put 30,000 in there?  I wouldn't expect that to work very reliably, but it might be worth a try for fun.

If this truly is a case where the cylinder moves, and your controller won't know it moves for 30 seconds then you'll need to consider other system dynamics.  Fortunately, since it sounds like position control you're probably only dealing with P-gain which is not time based.  If the signal to the valve doesn't change for 30 seconds is that long enough that you could overshoot your setpoint significantly?  Worst case scenario is perhaps you are right outside the tolerance for your setpoint, and your loop thinks the gate is where it was 30 seconds ago.  In that scenario how far will the gate move in 30 seconds?  Can you limit the speed to where in 30 seconds you will not have overshot your setpoint?  If not then perhaps you'll need to oscillate your valve signal on and off with the on duration set to result in a cylinder movement roughly equivalent to your position tolerance.

That's probably how I'd start out.

Hello

Is there an update on this topic or when can we expect the implementation of the EDS files?

Thanks!

After you did the update was the version string updated to the new version? We are seeing the device go through the 5 step FOTA process from the device details page and then show as completed. The device firmware value does not update to the new version though. I have logged into the device using the remote interlink and it also shows the application version has not updated. Almost like it did not update at all.

I was told it can be done using the connect portal, or a remote download using the remote interlink gateway. I was also told there is not a preferred method. With that being said, I have had zero luck using the remote interlink gateway to update the CS500. Remote download fails after about 10-15 seconds every time (download request failed). I attempted this on multiple devices as well to rule out a bad cell connection or something of the sort. I have had some success using the portal. Only a couple devices seem to have hung up on either "Requested" or "Downloading" so far.

I have 56 devices to update and so far have attempted 8. 4 of the 8 show as "completed" the other 4 are showing as "Downloading" or "Requested".

To update using the connect portal, first login then click on the devices tab in the left side bar menu. From there under your list of devices you will see an icon that is 3 vertical dots. Click on it and then click device firmware update. Once you select the firmware version you want to update and click apply you can view the status from the device details page (magnifying glass icon from device list).

Hope that helps.

I have the same issue with Guide 2023.2, the previous version 2023.1 is also ok. Fortunately I had a backup of the project as was able to go back to 2022.4 easily. If you don't have a backup you may be able to export the screen definitions, import them into a new project and copy the code in from the module viewer.

It will sometimes compile all the images and work ok. You can tell by checking the size of the __imageX.c files that are created in the project directory when compiling. If any of them are below 1kb it will most likely be a missing image.