/
LON IzoT Net Export (inex) Is Not Working

LON IzoT Net Export (inex) Is Not Working

inex is used to export a subset or complete IzoT CT drawing or IzoT Net Server database into the SmartServer in order to access device datapoints. If you are experiencing problems with inex, then check the following:

  1. Verify that you are using IzoT CT or IzoT Net Server 4.2. inex only works with IzoT CT or IzoT Net Server 4.2.

  2. Verify that you are using inex 1.50.016+.

  3. Verify that the SmartServer is supported; check the SmartServer release notes. 

  4. Change the SmartServer to IMM prior to running inex. Failure to change to IMM prior to running inex will cause the IP-852 and U60/U70 routing and datapoint access to stop working after a reboot. 

  5. Convert any required Resource File Sets to XML files and import then prior to importing device XIF files or running inex. A SmartServer IoT device needs to be added to CT for each SmartServer IoT device you are going to use. The SmartServer IoT device needs to be added to a IP-70 channel (each SmartServer needs its own IP-70 channel), which may require you to add additional IP-70 or U60 channel.  Only devices in the CT subsystem or child subsystem will be exported to the SmartServer.

Troubleshooting Scenarios

  1. Did you change the SmartServer to IMM before using inex?

    1. If not, then reset the SmartServer database, change to IMM using the SmartServer CMS Devices widget, and go through the inex import process again. 

  2. inex cannot find the SmartServer IoT device in CT or IzoT Net Server.

    1. Did you add a SmartServer IoT device to a SmartServer IP-70 channel in your CT drawing or IzoT Net Server database?

    2. If not, then add the device.

  3. inex cannot reach the SmartServer.

    1. Make sure that the MQTT ports are open; by default these may be closed. Go to the SmartServer Configuration page Firewall tab and open the ports that you are using with the inex tool.

  4. Datapoints in the SmartServer are correctly formatted or are not working properly.

    1. Did you import any required resource file set prior to running inex? Resource XML files need to be imported manually into the SmartServer CMS prior to running inex.

      1. Workaround: remove all devices and device types, then import the Resource file Set XML files, and finally run inex.

    2. If you ran inex using /skipfile and did not import the XIF manually or import the device XIF into the SmartServer CMS  prior to running inex, then this could cause the issue. 

      1. Workaround: remove all devices and device types, import any required Resource file Set XML files, optionally import the XIF files, and run inex with /skipfiles if XIF files were already imported, or without /skipfiles for inex to export the XIF files.

  5. Routing or datapoint access stop working after a SmartServer reboot.

    1. This usually means that you ran inex while the SmartServer is in DMM.

      1. Workaround: reset the SmartServer database, change to IMM, and reimport the Resource File Set XML and XIF files, and then run inex.