[BUG] IO Modules export/import

[Hommit]

Describe the bug
IO modules correctly identified by project discover, but do not get exported (and obv imported)

|-- A14 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A13 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A12 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A15 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A16 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A17 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A18 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A19 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A21 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A22 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A23 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A24 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A25 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A26 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A27 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A28 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A29 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)
|-- A30 (device | 225bfe47-7336-4dbc-9419-4105a7c831fa | ScriptObject)

To Reproduce
Steps to reproduce the behavior:

1. Run export script
2. No files with module names anywhere

Expected behavior
Export/import works

Environment (please complete the following information):

• CODESYS Version: 3.5 SP17, 17 fork, 16 fork
• Script Version: 1.7.4
• OS: Windows 11 latest

Additional context
NOTE: when collecting device mapping, use only filled rows and ignore everything else, as ithe amount of info in full defice mapping can be overwhelming.

Also, you don't need to concern yourself with signal hardware addressing (if module order changes, for example), as codesys automatically asssigns them on mapping import:

Application.astDI_Input[1].xInput;DI[1];;Шкаф CАУ открыт (инверсный);%IX0.0;A12
Application.astDI_Input[2].xInput;DI[2];;Шкаф CАУ ТС Тест прошел;%IX0.0;A12
...
Application.astDI_Input[31].xInput;DI[31];;Кран 1-2 свечной по входу ГРС КЦ - соленоид открытия;%IX0.0;A12
Application.astDI_Input[32].xInput;DI[32];;Кран 1-2 свечной по входу ГРС КЦ - соленоид закрытия;%IX0.0;A12
Application.astModDI_Input[1].xInput;Online;;Online status;%IX0.0;A12

This is fragment from my mapping generator csv output. As you can see, all lines generated with IX0.0 addressing (QX0.0 for DO, IW0/QW0 for AI/AO), no errors thrown on import

[Hommit]

Same goes for PersistentVars declaration:

Do you need separate bug for it?

[ArthurkaX]

Thanks for the report. Hardware round-trip is not in scope for now, only export and Git compare. The current direction is to keep these objects as export-only, and their
handling can be adjusted through the profile JSON if needed.

[ArthurkaX]

Thanks for the additional note about PersistentVars. I did not manage to include that in v1.7.5