Versions Compared

Version Old Version 2 New Version 3
Changes made by

Nina Cardillo

Nina Cardillo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Open the SmartServer Configuration page as described in Accessing the SmartServer Configuration Page. The Network tab appears as the default SmartServer Configuration page. Once the network settings are configured for the SmartServer system, then the System tab will appear as the default.


    Network tab


    System tab

  2. From the Network tab, select the LAN Interface Static IP Address dropdown option and specify the address details. 



  3. Click Update to save your configuration.

  4. Click the /wiki/spaces/TEMP/pages/1475599 tab.



  5. Enable the SmartServer IoT port 1883 for eth0, which is required for the IzoT Net Export Tool and internal applications.



  6. Click Update to save your configuration.

  7. Click the /wiki/spaces/TEMP/pages/1481252 LON tab.



  8. Enable the SmartServer IoT for IP-852  eth0 interface.



  9. Click Update to save your configuration.

  10. Click the /wiki/spaces/TEMP/pages/1476055 tab and /wiki/spaces/TEMP/pages/1476055CMS tab and log into the CMS.

  11. From the Devices widget, switch the LON management mode to LON Independent Management Mode (IMM).

See Configure Your SmartServer for more information about accessing and using the SmartServer configuration UI.  Additional information about defining the Modbus configuration settings is provided in sections (Optional) Remotely Accessing the IAP/MQ Server and /wiki/spaces/TEMP/pages/1481252 (Optional) Add a LON Interface.

Continue setting up Modbus IMM following the steps in the section below: Installing SmartServer IoT Files. 

...

  1. Use the CMS Import / Export button ( ) to import the internal LON application DTP file.

  2. Connect to the SmartServer IoT via FTP.

  3. In the /var/apollo/data/ directory, create a new directory called apps and a subdirectory under apps, where SmartServer IoT internal application files will be copied using the following commands:
    1. package.json
    2. package-lock.json
    3. <internalApp>.js

  4. Copy the <internalApp>.conf file into the /etc/supervisor/conf.d directory.

  5. If your SmartServer IoT has internet access, from the SmartServer console (as described in the section Connecting to Your SmartServer), navigate to the newly created internal app directory and enter the npminstall command to add the node packages required for this application.

    or 

    If your SmartServer IoT does not have internet access, use FTP to copy the entire node_modules folder into the SmartServer IoT internal application directory.

...

  1. Launch the LonWorks Interfaces (32-bit) control panel applet on your Windows PC.



  2. Using the LonWorks Interfaces applet, add a new IP-852 interface. 

  3. Define an IP-852 VNI interface that will be used by IzoT CT in the LonWorks Interfaces applet.

  4. Launch the EnOcean IP-852 Configuration Server. 

  5. Create or open an existing IzoT CT network and attach to the defined IP-852 interface that is on the same IP-852 channel as the SmartServer IoT.

  6. Set the Management Mode to OnNet.

  7. Verify that the Channel Properties of the opened network is set to IP-852.

  8. Create and add new IP-70 channel that represents the internal IP-70 channel.

  9. Add a new router object to the drawing connecting the IP-852 channel to the newly defined IP-70 channel.

  10. Return to the SmartServer IoT /wiki/spaces/TEMP/pages/1481252 LON Configuration page.

  11. Click IP-852 Router Configuration → Service/Connect button to generate service connect messages for commissioning the router.



  12. Drop a device on the IP-70 channel and commission it using the SmartServer IoT XIF and the /wiki/spaces/TEMP/pages/1481252 LON Configuration page Service/Connect button.

  13. Drop a device on the IP-70 channel and commission it using the SmartServer internal application XIF file to expose the datapoints on the LON network. At this point, the outputs for the LON datapoints on the SmartServer IoT internal application device should be active and populating live datapoints.