| Q: |
Is a physical LON adapter (FTT-10, etc.) required by the JACE to use the LonIp driver?
|
| A: |
No LON adapter is required. The LonIp driver uses the JACE’s Ethernet port—unlike the standard Lonworks driver, which binds
any LonNetwork to a specific LON adapter by device name (LON1 or LON2 for example). In the LonIp driver, this device name is fixed, read-only as “LonIp”.
See this in property sheet of a LonIpNetwork, by expanding its Lon Comm Config container.
|
| Q: |
Why can’t I add the LonIpNetwork from the Driver Manager, as with most other drivers?
|
| A: |
Because there is no separate “LonIpNetwork” class. The LonIpNetwork palette entry is just “BLonNetwork” with the comm stack
and the local device changed to support communications using IP.
|
| Q: |
What is the purpose of the Config Server?
|
| A: |
The Config Server collects address information from each of the members of the LonIp channel, and then updates all the other
members with the collected information. It is necessary to have one central device responsible to collect and disseminate
this member information, since the protocol does not provide a mechanism for members to discover each other..
|
| Q: |
Why during a device discover do I get a lot of warning messages, similar to below?
WARNING [12:58:48 31-Jul-09 EDT][lonip] Received
response message with no matching transaction.16 00 01 19 0f 00 04 01 00
00 00 00 00 00 00 00 21 03 00 00 08 26 81 80 00 01 01 01 01 9a 21
|
| A: |
This is normal behavior for the LonIp driver (LonIpNetwork), as the driver receives and processes all messages on the wire
addressed to our device. The discover process involves broadcasting a request/response message, and then processing the first
response which closes out the transact. Other responses may be received after matching transact has completed.
When using the standard Lonworks driver (LonNetwork), these warning messages do not appear because the Neuron processes the
messages off the wire, and it filters out all except the first response.
|