Importing Holding Register JSON overwrites points as Binary Input/Coil Status instead of Holding Register

[Mehul097]

Description:
When exporting a Holding Register data point configuration from one SCADA-LTS instance and importing it into another, the imported points are incorrectly changed to Binary Input or Coil Status types. This causes parameter mismatches and loss of original configuration.

Expected Behavior:
Imported data points should retain their original type (Holding Register) and associated parameters exactly as in the exported JSON file.

Actual Behavior:

Holding Register type is replaced with Binary Input or Coil Status type.

Associated parameters (scale, units, etc.) are altered or lost.

Steps to Reproduce:

On SCADA-LTS instance A:

Create a Modbus Holding Register data point with custom parameters (scale, units, etc.).

Export the data source JSON file.

On SCADA-LTS instance B:

Import the JSON file.

Check the data point type and parameters.

Result:
Data point type changes to Binary Input/Coil Status, parameters are replaced.

Environment:

SCADA-LTS version: [Add version here]

OS: [Windows/Linux + version]

Database: [PostgreSQL/MySQL + version]

Browser: [Browser + version]

Protocol: Modbus TCP/RTU

Additional Context:

This issue happens specifically with Holding Registers.

JSON file attached below:

Scadalts_Server.Json

[Limraj]

Hi @Mehul097,
For example "SCADA-LTS version: [Add version here]"
Why didn't you write that down? It's your responsibility to provide us with as much detail as possible about the problem so we can efficiently reproduce it.

Here, we're more interested in the scenario that leads to the failure, rather than a verbal description of how it currently works and how it should work.

We have two Import functions (mark yellow and green):

Providing a detailed description of what you clicked that caused the error will shorten the time it takes to reproduce the error and expedite the fix. We recommend doing this whenever you're discussing errors.

Regards,
Kamil Jarmusik

[Mehul097]

Hi I am using below version on both windows server 2012 and Windows 11

Scada LTS Version- v2.7.8.1 build 14176899126 (GitHub ref: 42291e5)

[Mehul097]

The file I shared is not a complete project — it only contains the datasource and datapoints.

If you check the JSON file, you will see that Holding Registers are correctly mapped. However, when importing the JSON file using the IMPORT tool, these Holding Registers are somehow being converted into Coil Status automatically.

[Limraj]

Hi @Mehul097,
If you had simply presented the script, we could have avoided any misunderstandings. It's not that I'm assuming anything, but that it's clear from the description. It's simply best to send the script next time with all steps numbered from step 1. This will make the task as easy as possible.

@Mehul097 This import is still missing a Data Source. I'll create a suitable Data Source, and if the problem doesn't occur, I'll also request a JSON file from the Data Source.

Regards,
Kamil Jarmusik

[Mehul097]

Hi Sir

I have attached 1.57MB json file if it can help here for troubleshooting

Regards
Mehul

[Limraj]

Okey @Mehul097 I tried to reproduce this on version 2.7.8.1 build 14176899126 and I can't reproduce it with this data. It imports with the correct Holding Register type, but the "Coil Status" type is the default, so perhaps the import is failing for specific data.

I can't import the full file because I don't have the full data source list, if you send it to me I will be able to import the full json, maybe then this error will appear.

1. I need at least the Data Source list exported, not just the points.
2. The problem is definitely reproducible, so it's a matter of providing information about the specific steps you're taking and what data you're importing.
3. You can also send logs from your import, which are generated during this process, including the red text and any errors.

4. You can also send logs from tomcat/logs, after import. First, it is best to archive old logs and delete the contents of tomcat/logs to have fresher logs.

5. I also tried to save from "Coin status" and import what is from Holding register and it overwrites the Holding register type correctly.

6. For information, we currently do not support the "4 byte float swapped inverted" type. I know this doesn't apply to you because you're using the "4 byte float swapped" type.
   Fixed Modbus IP unsupported data type #3147

7. For now, it's an old file. I may have to wait until the file is updated on the server. You need to export from the data source list.

[Limraj]

Hi @Mehul097,
To sum up:

1. In addition to the exported data points, you also need a data sources, the points are related to the data source and cannot be imported without them;
2. If the updated data does not lead to the error, then I will need the import logs and the Tomcat logs;

Regards,
Kamil Jarmusik