Hi, I am looking for a workaround to perform offline updates at end-user site, where VPN access is not possible. The procedure via upload of a configuration archive seems not working for me, as I don’t want to share e.g. a Node-Red flow with the end-user. Currently, I am working on a following scenario, but don’t feel so confident and comfortable with it. So, your recommendations will be very appreciated. Scenario via Backup & Restore: 1. In order to have the same setup as at customer site, I restore the image of the machine to be updated on a new CtrlX-CPU An issue occurs, when older app release (from RM21.03) is in use 2. I install core18 manually on the new CPU and restore of the original image can be then done 3. Update PLC and Node-Red projects 4. Create a new image and send to end-user 5. End-user restores the new image on his machine via CtrlX CORE web interface with user rights limited to backup and restore I guess, at end-user site the same issue during restore will occur as at this CPU ‘core18’ shouldn’t be installed as well. In my particular case to clean up the mess, I created with mixing of different app releases, I would update all apps before creating the new image with the updated projects. But, I am still not sure, if the restore will go smoothly on an older CtrlX CPU in general? (Unfortunately, I updated my older one, so I am not able to try that) Is it possible to create an own rescue SD card in order to perform a total update implementing the crypted image file and not losing all the settings for users, connectivity etc.? This could be a comfortable plug&play way for not experienced end-users to perform offline updates. Thanks, Venzi
... View more
