Importing a configuration file that was created using another BMXNOR0200 could fail if the size of the file too large.
Issue
Importing a configuration file that was created using another BMXNOR0200 could fail if the size of the file too large.
Product Line
BMXNOR0200
Environment
Windows 7, windows 8, Windows 10. All versions of exec firmware for the BMXNOR0200.
Resolution
When a configuration file is imported into the BMXNOR0200, it will consume memory within the module. If the file size exceeds the amount of free
memory available in the BMXNOR0200, the import will fail. This could occur if the file was created by exporting it from another BMXNOR0200 module
that contained a huge amount of variables defined in the DNP3 'Data Mapping' web pages. When the configuration is exported from a BMXNOR0200 in this
situation, it will creates a file that could be larger than the actual memory size within the BMXNOR0200 module. During the creation of the export file on the PC,
the operation extracts the information from the BMXNOR0200 module and writes it to an ASCII text file. The export of the file will not have any problems
exporting because there is sufficient free memory on the PC.
When the file is imported in to the BMXNOR0200 module, the following occurs: (This action also consumes memory.)
It is recommended to check the free memory available within the BMXNOR0200 module and compare it against the file size. this can be performed by:
To resolve the issue, the following workaround is recommended:
Importing a configuration file that was created using another BMXNOR0200 could fail if the size of the file too large.
Product Line
BMXNOR0200
Environment
Windows 7, windows 8, Windows 10. All versions of exec firmware for the BMXNOR0200.
Resolution
When a configuration file is imported into the BMXNOR0200, it will consume memory within the module. If the file size exceeds the amount of free
memory available in the BMXNOR0200, the import will fail. This could occur if the file was created by exporting it from another BMXNOR0200 module
that contained a huge amount of variables defined in the DNP3 'Data Mapping' web pages. When the configuration is exported from a BMXNOR0200 in this
situation, it will creates a file that could be larger than the actual memory size within the BMXNOR0200 module. During the creation of the export file on the PC,
the operation extracts the information from the BMXNOR0200 module and writes it to an ASCII text file. The export of the file will not have any problems
exporting because there is sufficient free memory on the PC.
When the file is imported in to the BMXNOR0200 module, the following occurs: (This action also consumes memory.)
- The file is downloaded to the web server within the BMXNOR0200.
- The module performs a check of the imported information.
- The information is parsed from the file to the respective locations within the module.
It is recommended to check the free memory available within the BMXNOR0200 module and compare it against the file size. this can be performed by:
- Click on 'Memory' in the BMXNOR0200 web page to open the 'Memory Diagnostics' web page.
- Compare the 'Free Memory Size' against the file size.
To resolve the issue, the following workaround is recommended:
- Use an array data type. rather than configure each point one by one. The 'Array' type is more efficient.
- If a variable name is required for each point, an alias can be used on array.