Test Direct Communication

When troubleshooting any data logger, confirming successful direct communication is an important early step.

Check LED

If an iSIC is being used, the LED status light can be observed during boot-up. This is not possible with a SDL or CB-iSIC as the LED is hidden internally.

1. Cycle power to the iSIC
   1. See Cycling Power to an iSIC/SDL
2. As soon as power is re-applied, look in the small hole above the analog terminal for the green LED to blink
   1. It will blink slowly a few times, turn off for a little, then blink quickly for a few seconds before turning off

Check Terminal Output

The most basic form of communication is the terminal output during data logger startup.

1. Open iChart
2. Click on Advanced | Terminal
3. Select the correct PC COM Port
   1. To determine the correct COM Port see the following article Verifying iSIC/SDL COM Port
4. Confirm the Detail section shows 9600 baud, N81, None
5. Choose the Connection type as Direct connect
6. Click Connect
7. Wait for a blank white screen to appear
8. Connect the logger to the computer
9. Cycle power to the logger
   1. See Cycling Power to an iSIC/SDL
   2. ***If using a UW-USB cable to connect to an SDL, this will power the logger and the UW plug needs to be removed from the SDL to fully cycle power.***
10. If Connected via RS-232, the logger should output something similar to the following
    1. First line:          !  RunApp
    2. Second line:     #EXR
    3. Third line:        NexSens <Device Type>
       1. Device type will show iSIC, 3100-iSIC, 4100-iSIC, SDL500, SDL500C, SDL500R, … depending on the type of logger connected
    4. Fourth line:      <Permanent Communication Protocol>
       1. Permanent Communication Protocol will show %232, %TTL, %485 depending on the device’s configuration
       2. If %TTL or %485 appear, follow the following instructions to change the temporary protocol to %232
          http://www.nexsens.com/knowledge-base/software/ichart/temporary-direct-connection-with-an-isic-data-logger.htm
    5. Fifth line:         <Temporary Communication Protocol>
       1. Temporary Communication Protocol will show %232, %TTL, %485 depending on a user’s input
       2. This is what determines how the logger will interface with the computer
    6. Sixth line:        <Other mode information>
       1. This line does not show up in most applications
       2. Other mode information includes things like SDI-12, Modbus, Iridium AT commands
11. If Connected via RS-485,  the logger should output something similar to the following
    1. First line:        NexSens <Device Type>
       1. Device type will show iSIC, 3100-iSIC, 4100-iSIC, SDL500, SDL500C, SDL500R, … depending on the type of logger connected
    2. *Second line:      <Permanent Communication Protocol>
       1. Permanent Communication Protocol will show %232, %TTL, %485 depending on the device’s configuration
    3. *Third line:         <Temporary Communication Protocol>
       1. Temporary Communication Protocol will show %232, %TTL, %485 depending on a user’s input
       2. This is what determines how the logger will interface with the computer

*These lines only appear if the user does an escape command

 

Check Advanced | iSIC | iSIC Communication

After confirming terminal output during power cycle, the next step is to confirm two-way communication.

1. In iChart click on View | Diagnostic Window to open the diagnostic window
2. Click on Advanced | iSIC | iSIC
3. For PC COM Port, select the COM port that was used above when successfully seeing the terminal output
4. Confirm the Detail section shows 9600 baud, N81, None
5. For Connection, select iSIC (Direct connect)
6. Leave the iSIC/SDL Address at 0
7. Click Connect
8. After the button changes to Disconnect, click the General tab
9. It should load up quickly if successful and look like the following
   1. Confirm battery voltage and date/time are read correctly
   2. If it does not load quickly, look at the diagnostic window for more information
      1. RETRY! and Fail sending CMD are an indicator that there is no communication between the computer and the logger
         1. Double check all connection settings
         2. Contact NexSens tech support for more assistance: Contact Us
10. If the date/time and battery voltage read correctly, direct communication has been confirmed

 

If communication failed at any point in this process, please confirm the correct COM port is being used, the cable is plugged in fully, the power supply/battery is good and if none of that works try adjusting the direct timing and re-trying the above steps.

Adjust Communication Timings