Converting a v2 config to a v3 config

Note: It is best practice to have separate v2 and v3 configurations, rather than using the same configuration files for both products. This is due to the devices running different firmware and thus requiring different commands to enable certain features. If you only want to copy the orientation, antenna and advanced slip settings then you can instead copy over the following files:

• mobile.ata
• mobile.att
• mobile.gap
• mobile.gpa
• mobile.nsa
• mobile.nsp
• mobile.nvsa
• mobile.nvsp
• mobile.vaa
• mobile.vat 

Keep separate v2 and v3 mobile.cfg files and only transfer the files listed above. 

Method

As v3 units have additional hardware features the configurations files are different. To convert a v2 configuration these steps should be followed.

Step 1

• Select modify config in NAVconfig
• Read settings from folder
• Select V2 version for the product type

Step 2

• Check the settings and values
• Commit to the v3 unit
•  The configuration will fail verification as the v3 unit will automatically have some default wifi settings.

Step 3

• Read the configuration back from the v3 unit 
• Configure new hardware settings as necessary:
  • WiFi
  • Enable NTRIP if using (this setting won't carry over from the v2 config as different commands are used)
  • Internal NTRIP client
  • CAN FD

The output Ethernet packet based on trigger 1 is on by default this can be switched off if not needed. If needed then the trigger 1 should be selected as an input.

Step 4

• Commit the new configuration to the v3 unit