/
LON Devices Are Not Communicating Using U60s or U70 (RED CMS Device State)

LON Devices Are Not Communicating Using U60s or U70 (RED CMS Device State)

U70 is not supported for SmartConnect. SmartConnect is available with SmartServer 4.2 and higher. LON is supported for SmartConnect 4.3 and higher, with the exception of LON PL. 

If the SmartServer LON Configuration page displays the message "The lon1 device has failed a CENELEC protocol query. Device likely needs to be reset to restore communication", then you need to use SmartServer 3.65 or 4.1 (Beta) and higher, and update the U70 software. For power-line repeating networks, update the SmartServer and U70 software even if do not see the CENELEC error. 

If you experience problems with the U60 or U70, then add a USB 2.0 ferrite clamp onto the USB cable to reduce LON channel noise. See https://www.usbfirewire.com/parts/rr-fh0-500b.html

Follow the steps below for more information and diagnostics. 

  1. Verify that the U60 or U70 is up using one of the following methods:

    1. Use the SmartServer Configuration page LON tab to see if the U60/U70 appears under LON interfaces.

      1. Use the console/SSH command ifconfig and check the lon#. There should be one lon# per U60/U70. When using the ifconfig command from the console, either log in as root or  enter sudo ifconfig.

    2. If the U60 or U70 do not appear, then perform the following:

      1. Verify whether these devices are plugged in.

      2. Check for USB noise by looking for EMI? in the SmartServers.

        1. For SmartServer release 4.0 and higher (most of the important logs are now in the /var/log/syslog): 

          1. Go to the System Configuration Web page and click on the Logs button which will download the file to your PC (usually downloads folder).

          2. Extract the *.tgz - on windows you can use 7-zip to extract the files.

            1. During the extraction process you may see a Confirm File Replace dialog pop up. If you see this dialog click the Auto Rename button.

          3. Extract the *.tar file.

            1. During the extraction process you may see a Confirm File Replace dialog pop up. If you see this dialog click the Auto Rename button.

            2. As some of the files in the *.tgz are symbolic links which may not be supported by Windows, wait until the progress bar is completely green and the click the Close button.

            3. Look for EMI? in  /var/log/syslog, using console/SSH. 

              sudo grep "EMI?" /var/log/syslog

               

        2.  For Smartserver 3.6 and prior releases:

          1.  Look at /var/log sys.log, kern.log, and error files using the commands below. If you see EMI? in the log files, then you need to add a filter, like a USB 2.0 ferrite bead clamp onto the U60/U70 USB cable.

            Console/ssh commands to look for looking for EMI?

            sudo grep "EMI?" /var/log/kern.log sudo grep "EMI?" /var/log/error sudo grep "EMI?" /var/log/syslog

      3. Reboot the SmartServer.

        If the U60/U70 continuously stops working after power cycles, then perform the following:

        1. For SmartServer 3.6 only, enter the following SSH command (this command may allow the U60/U70 to come up, but it is not a fix):

           sudo /sbin/apollo-usbreset start

        2. For all SmartServer versions, add a USB 2.0 ferrite bead clamp onto the U60/U70 USB cable.

    3. Verify that the LTE and LTX services are running.

      1. For SmartServer release 4.0 and higher:

        1. Check if LTE and LTX services are running. The LTE and LTX may get restarted if you import or make changes to an XIF file or re-import Resource File Set XML file.

        2. Check the current status of these services using the following ssh commands. The example below shows the U60 working.

          $ sudo smartserverctl status alarm ACTIVE 1h 4min bacnet ACTIVE 1h 4min core ACTIVE 1h 4min datapoint-connection-manager ACTIVE 1h 4min datapoint-controller ACTIVE 1h 4min datapoint-get ACTIVE 1h 4min enocean-driver ACTIVE 1h 4min formatter ACTIVE 1h 4min housekeeper ACTIVE 1h 4min iap-controller ACTIVE 1h 4min init ACTIVE 1h 4min lim ACTIVE 1h 4min loader ACTIVE 1h 4min logger ACTIVE 1h 4min lon ACTIVE 1h 4min lte ACTIVE 1h 4min ltx ACTIVE 1h 4min lwd ACTIVE 1h 4min modbus ACTIVE 1h 4min monitoring ACTIVE 1h 4min mosquitto ACTIVE 1h 4min node-red ACTIVE 1h 4min pyro4-ns ACTIVE 1h 4min query ACTIVE 1h 4min reboot-manager ACTIVE 1h 4min resource-publisher ACTIVE 1h 4min scheduler ACTIVE 1h 4min secmount ACTIVE 1h 4min services ACTIVE 1h 4min smartserver ACTIVE 1h 4min storage-manager ACTIVE 1h 4min apollo@smartserver-17qam88:~$

        3. You can also restart these services as they may get out of sync (for example, you may have deleted a device in the CMS, but it did not get cleared from MQTT) using the following command: 

          sudo smartserverctl restart lon

      2. For SmartServer 3.6 and prior releases:

        1. Check if lon:echlte and lon:echltx services are running. The LTE and LTX may get restarted if you import or make changes to an XIF file or re-import Resource File Set XML file.

        2. Check the current status of these services using the following ssh commands. The example below shows the U60 working.

          sudo supervisorctl status ~$ sudo supervisorctl status apollo-init EXITED Dec 19 06:29 AM core:echhousekeeper RUNNING pid 1159, uptime 4:21:35 core:echlim RUNNING pid 1163, uptime 4:21:35 echbacnet RUNNING pid 1155, uptime 4:21:35 echmodbus RUNNING pid 1240, uptime 4:21:34 echopcua-server STOPPED Not started lon:echlte RUNNING pid 3627, uptime 4:19:57 lon:echltx RUNNING pid 3626, uptime 4:19:57 ready EXITED Dec 19 06:29 AM services:echalarm RUNNING pid 1208, uptime 4:21:35 services:echapollo-rp-launch RUNNING pid 1236, uptime 4:21:34 services:echconnection RUNNING pid 1214, uptime 4:21:35 services:echdatapointcontrol RUNNING pid 1216, uptime 4:21:35 services:echdatapointget RUNNING pid 1227, uptime 4:21:35 services:echformatter RUNNING pid 1229, uptime 4:21:35 services:echiap-controller RUNNING pid 1239, uptime 4:21:34 services:echloader RUNNING pid 1185, uptime 4:21:35 services:echlogger RUNNING pid 1170, uptime 4:21:35 services:echmonitoring RUNNING pid 1174, uptime 4:21:35 services:echquery RUNNING pid 1180, uptime 4:21:35 services:echscheduler RUNNING pid 1237, uptime 4:21:34

        3. You can also restart these services as they may get out of sync (for example, you may have deleted a device in the CMS, but it did not get cleared from MQTT) using the following command (include the : at the end of the command):

          sudo supervisorctl restart lon:

           

  2.  Use NodeUtil to see if device status "s" works.

    1. Using NodeUtil: Make sure that an RNI is set up for the U60 or U70. Next make sure you set up a RNI in the PC Windows Control panel > LonWorks Interfaces applet. 

      1. Start NodeUtil (e.g., nodeutil -dx.default.215) using a DOS command prompt.

      2. Add the device neuron Id (from the CMS Devices Widget) to NodeUtil using the "a" add command. Next click "g" followed by return and then "s".

    2. If NodeUtil device status works, then:

      1. Make sure the device is configured for the correct domain Id.

        1. Press "d" for domain in nodeUtil which will show you the device's domain ids. You can look at the SmartServer Configuration Page LON tab for the current domain id.

      2. If the domain ids are correct, then restart the LON drivers as shown above.