This article describes the steps to follow if you get a "Node version incompatible" error when attempting to import an existing node configuration file into your serial ABC Anybus Communicator.
APPLICABLE PRODUCTS
ABC3000-A
ABC3007-A
ABC3013-A
ABC3028-A
ABC3061-A
PRE-REQUISITES
A serial ABC Anybus Communicator
A node configuration file saved from a previous serial ABC Anybus Communicator
PROBLEM DESCRIPTION
You have configured an Anybus Communicator and saved the node configuration file. When attempting to import this node file into another Communicator configuration, you get an error message similar to this one:
SOLUTION
This error occurs because the firmware version in the Communicator into which you are trying to import the node configuration is higher than that of the Communicator from which this node file was originally exported.
To solve this, there are three main steps to follow:
Creating an old configuration file based on the old node file
Converting the old configuration file to a new configuration file
Extracting the new node file from the new configuration file
CREATING AN OLD CONFIGURATION FILE FROM THE OLD NODE FILE
Go to the Anybus Communicator online emulator [https://emulator.online-config.anybus.com/]
Enter the article number (without the suffix letter) of the Communicator used to create the node file. After entering the article number, you will be offered a choice of all the released firmware versions. Select the Firmware version used on the Communicator where the node file was created. Here is an example:
After clicking on 'Go!' you'll be taken to the emulated web interface of the Communicator:
Click on 'Serial RS-232/485' >> 'Communication' and select the same communication protocol that was used in the original configuration. In this example the default settings are kept:
Now go to the 'Nodes & transactions' page
Click on the downward arrow beside the 'Add' button and select 'Import node'
Select your node file and import it.
After successfully importing the node file, you now need to export the whole configuration file. For this, simply go to the 'Files & firmware' page and click on 'Export'.
Note that the file exported here will be a general configuration file (*.conf), not the node configuration file (*.node).
After this you can close that emulated web interface.
CONVERTING THE OLD CONFIGURATION TO A NEW CONFIGURATION FILE
Now that you have created a full configuration file based on the old node file, you need to import that configuration file to update it to the same version of firmware used in your Communicator. You can again do this in the online emulator but this time you should select the firmware version currently on your new Communicator.
NOTE: You can also do this step directly in your Communicator if you are connected to it. If you choose to do this then please save any current configuration you are working on as these steps will overwrite that. You can do this by applying the configuration to the Communicator or by saving a backup file with the Export function.
In our example the new ABC3000 Communicator has the latest firmware version so on the emulator home page we select it like this:
Now, you import the full *.conf configuration file that you have just created. To do this, go to the 'Files & firmware' page and click on 'Import'.
After selecting the *.conf file and importing it, you will have a pop-up with two options:
Select 'Imported settings'.
Now all that is left to do is to export the node file from this configuration. However, before doing that there is one last thing to take care of.
In our example, if you look closely at the emulated versions of firmware 1.03 and 1.07, you will notice that in the screenshots from version 1.07 there is a language icon on the top right which was not present in version 1.03.
This is because the language feature wasn't present in the firmware version 1.03. However, since that feature is present in the firmware version 1.07 that is currently running on our new ABC3000, we need to manually configure a language before exporting the new node file.
To do this, simply click on the language icon and select the language you wish to use in the new Communicator's configuration.
If you do not do this then you will get the error "Something went wrong - Invalid language tag 'temp'" when you change pages.
EXTRACTING THE NEW NODE FILE FROM THE NEW CONFIGURATION FILE
The final step is to extract the new node file from the latest firmware version of the configuration. To do this, you simply go to the 'Nodes & transactions' page and export the new node file as shown on this screenshot.
You should now be able to use this new node file in your current Communicator.
NOTE: If you were doing the second and third steps on your new Communicator directly (rather than in the online emulator) then you can at this point restore the configuration you were working on. Since you (hopefully) did not actually 'Apply' the configuration you can use the option 'Revert' which will revert all settings in the configuration to the values in the Anybus Communicator's current configuration.
Or if you took a backup you can 'Clear' the changes and reapply that with the 'Import' option.
ADDITIONAL INFO
If you are unable to solve this issue despite following the steps in this article, please get in contact with our Technical Support team [here].
© HMS Networks AB 2025