|
Pay attention to the log at the bottom of the screen in the configuration tool. If it says anything about "failed" or "not found", you are not connected. Another important clue: If the data in any given response is a string of all C's, it is not real data. That is the dummy fill value when real data is not available.
Upon successful connect, the log window will look like this if using a U10, PCC-10 or PCLTA-21 network interface:
Upon successful connect using an i.Lon as the network interface, the log window will look like this:
Upon failed attempt using a PCC-10, the log window will look like this (and is similar for other interfaces):
To further trouble shoot this problem, open your PC's control panel and look for the interface icon. Once you have resolved the interface problem, restart BBConfig.exe so that it refreshes its device list.
|
 |
For USB U10 or i.LON 100 users, Locate the LonWorks Interfaces icon in your control panel (classic view). Double click to open.
For PCC-10 and PCLTA users, click the LonWorks Plug 'n Play icon to find your interface.
|
|
|
Click this icon to check your USB LonWorks Interface or your i.LON 100. |
|
 |
For USB U10 users, click on the USB tab at the top. You should see the USB logo and LONx where 'x' is 1 and up depending on how many LonWorks interfaces you have on your system.
For i.LON 100 users, click the RNI tab of this same utility to look for your interface.
If you are using PCC-10 or PCLTA, click the LonWorks Plug 'n Play icon on the control panel, and configure it for the NSI driver. (If the PCC-10 or PCLTA interface appears in the list but won't connect, it probably isn't configured for the NSI driver.) Look for icon below.
|
|
 |
If you do not see your interface in the control panel tools mentioned above, you will need to look at your system's hardware device manager to see if the hardware is recognized.
Assuming you do find your interface, you may test it by clicking the test button, and further by clicking the comm button. Once the comm button is clicked, press the service button on any LonWorks device on the network to observe the service pin message and ping test.
|
|
 |
If your USB interface does not appear as shown above in the USB tab, you need to check the hardware by first clicking the System icon in your control panel. |
|
 |
Clicking the System icon will bring up the System Properties dialog. Now click the Device Manager button. |
|
 |
Scroll down and expand the view of Universal Serial Bus controllers. You should see the Echelon USB Network Interface listed. If not, you need to re-install the USB driver and/or OpenLDV. |
|
 |
Double click on the Echelon USB Network Interface in the Device Manager window above. You should then see this window showing "This device is working properly".
At this point, you are tempted to say, "No, it is not." However, if you now return to the USB tab of the LonWorks Interfaces window above, you are likely to now see the USB interface listed. It is common to need to check to see that the device is working to get it to start working. Now proceed to run the test mentioned above.
|
|
|
If you are using a PCC-10 (PC or PCMCIA card in laptop) or PCLTA-21 (PCI bus card in desktop), you need to look for this icon in your control panel. |
|
 |
Clicking the LonWorks Plug 'n Play icon will bring up this window. If no hardware has been recognized, no devices will be listed in the Device Selected window. You need to verify hardware and/or re-install drivers.
The most common cause of connect problems is the NI Application selection. LonMaker uses PCC10VNI (for PCC-10) and PCLTA21VNI (for PCLTA-21). Other software, including OpenLDV and BBConfig use PCC10L7 (for PCC-10) and PCLTA21L7 (for PCLTA-21).
If you do not have the P...L7 NI Application selected, select it, and click Apply. Now click the Diagnostics button.
|
|
 |
Clicking the diagnostics button will bring up this window. Click Restart, then Test to do a self-test, and/or Comm to test externally. The example at the left shows reset, restart, then Comm followed by pressing the service pin on a Babel Buster. The Comm test continues to ping the node unit you click Quit (button disappears when clicked). |
|
|
|
Still can't connect? Are you running other LonWorks applications on the same PC? The LonWorks network interface does not support simultaneous use by different applications (which explains why we have as many as 3 network interfaces on some computers used for testing here at Control Solutions). Close any other applications that are using your network interface and restart BBConfig.exe.
Reasons you can't connect to the network interface will be one or more of these:
* Network interface hardware not working
* Network interface already in use
* Wrong NI Application selected (applies to PCC-10 and PCLTA-21 only)
* Network interface driver not properly installed or is old version
* OpenLDV 2.1 (or higher) not found on system
|
