Hi there,

I would like to prepare a clean (in terms of stripped of CodeSys license) Raspberry Pi image ready for release.

Whenever a new device is sold I would like to flash the clean image, connect with my IDE to the device and activate a new CodeSys license on the device.

My question: Which files do I need before creating the clean release image?

I know of the following folder: /var/opt/codesys with the following relevant content:

pi@mypi:~ $ tree /var/opt/codesys/
/var/opt/codesys/
├── 3SLicense.wbb
├── backup
│   └── 3SLicenseInfo.tar
├── bacstac.ini
├── cert
│   ├── export
│   └── import
├── cmact_licenses
│   ├── 128-somenumber1.dyn
│   ├── 128-somenumber2.dyn
│   ├── somenumber3.wbb
│   ├── somenumber4.wbb
│   ├── info.lic
│   └── secure.cnt
├── CMLicenseNew.WibuCmRaU
├── _cnc
├── PlcLogic
│   ├── ac_persistence
│   ├── alarms
│   ├── Application
│   │   ├── Application.app
│   │   ├── Application.crc
│   │   └── Application.ret
│   ├── _cnc
│   ├── RETAIN.ret
│   ├── trend
│   └── visu
│       ├── somepic.png
│       ├── application.imagepoolcollection.csv
│       ├── application_visuusermgmtdb.csv
│       
├── restore
├── SysFileMap.cfg
├── visu
└── WibuCtxt.ctx

Thanks!

Best regards,
LeFish

Hey.

We are planning a similar approach to this with our products in the near future. We are looking to streamline setting up our CODESYS devices by having a pre-built image ready to go.

How did you get on with this? Anyone else have any information on this topic?

Hi,
just clean up the content in
cmact_licenses... or delete the whole directory.
On bootup on the new device this will generated with binding the new hardware ( new empty softcotainer). Thats it.
Best Regards
Edwin