1. Technical Communication
Kevin Kwan

2. LonScanner Protocol Analyzer

3. Confirm the utilization of LonScanner tools
Can it measure TP1250 or Ethernet media LON Communication?
The answer is Yes
How?
TP/XF-1250 Channel
Chose a right network interface card
PCC-10 with TP1250-POD
LonWorks’ Plug’n Play in Control Panel
Ethernet media – LonWorks/IP Channel and IP-852 Channel
LonScanner with LNS Turbo Edition
Will not receive packets that are sent on an IP-852 channel from one device or router to another if the source or destination device is not the computer running the protocol analyzer.

4. Confirm the utilization of LonScanner tools
Only receive packets sent on the network paths displayed in green.
Not receive packets sent on the network path displayed in red.

5. Procedure to transfer LNS Database to LonScanner
Names are not included in the packets sent over the network, nor are they saved in log files. However, you can still use names to identify the devices, the network variables, or the domains and groups on your network.
You can import the names stored an LNS database for your network.
The network database must be stored on the same computer you are running the protocol analyzer on, and you must have an LNS Turbo Edition Server or an LNS3 Server installed on the computer.

6. Procedure to transfer LNS Database to LonScanner
Names are not included in the packets sent over the network, nor are they saved in log files. However, you can still use names to identify the devices, the network variables, or the domains and groups on your network.
You can import the names stored an LNS database for your network.
The network database must be stored on the same computer you are running the protocol analyzer on, and you must have an LNS Turbo Edition Server or an LNS3 Server installed on the computer.
Demo to import a LNS Database to LonScanner

7. How to use LonScanner connecting with Ethernet to measure FT-10 channel devices performance
Yes or No?
Yes, if you use iLon100 / FT-10
No, if you use VNI plus iLon600
You need a separate NIC to directly connect to FT-10 Channel
Indirectly with LNS application, but not LonScanner
VNI + iLon600 + MPR-50
Install the Monitor Node of MPR-50
Get the related Network variable

8. How to use LonScanner connecting with Ethernet to measure FT-10 channel devices performance

9. Lon connectivity

10. Fiber optics LON converter
Let’s discuss later

11. Echelon devices throughput specification in terms of package / second and kbps
How Much to Put on the Backbone (1 iLon MPR-50)
IP-852
Supervisory Software
FT-10
TP-1250
10/100

12. Echelon devices throughput specification in terms of package / second and kbps
How Much to Put on the Backbone (1 iLon MPR-50)
100 Packets/s per channel
or 452 Packets/s Total
Design targets:
FT-10 channel bandwidth not to exceed 50% or ~100 Packets per second. For each FT-10 channel or inter FT-10 channel traffic
TP-1250 channel bandwidth not to exceed 70% or ~600 Packets per second
FT-10
TP-1250
10/100

13. (50% traffic bandwidth on FT channel)
Echelon devices thoughput specification in terms of package / second and kbps
Recommended System Design
Number of MPR-50 per TP-1250 channel
Recommended Total Traffic From FT-10 to TP-1250 per MPR-50
(50% traffic bandwidth on FT channel) 1
452 Packets/second 2
300 Packets/second 3
200 Packets/second

14. Echelon devices thoughput specification in terms of package / second and kbps
FT-10 Bandwidth to Packets Curve

15. Echelon devices thoughput specification in terms of package / second and kbps
TP-1250 Bandwidth to Packets Curve

16. Echelon devices thoughput specification in terms of package / second and kbps
Throughput rate
Channel type
Utility of bandwidth for best performance
iLon600
800 packets / sec.
200 packets / sec.
TP/XF-1250
FT-10
Not exceed 70% or 600 packets / sec
Not exceed 50% or 100 packets / sec
MPR-50
200 packets / sec
PCLTA-21

17. Demonstrate how to make use of i
Demonstrate how to make use of i.LON 600 as NIC commission FT-10 channel devices
Demo
Create a VNI with LonWorks Interface in Control Panel
Create devices in LonWorks-IP Configuration Server
Launch the management tool
Add channels firstly
Then add routers
Thirdly, add devices on right channel
Finally, commission routers prior to the devices

18. How to use ethereal study Lonworks packets over IP in UDP protocol
Demo
Not focus on the utility of bandwidth
Use filter to isolate the un-necessary information

19. Frequency Converter

20. Procedure to classify the frequency converter influencing LON Chips
Tools
Multimeter
Make sure the wiring is alright
LonScanner
Focus on the error log of devices
Short packet errors (<8bytes) are called out separately from CRC errors because noise can appear as a valid preamble followed by a few bytes of data on some transceivers. The distinct counters may help one distinguish channel noise from packet collisions or transmission errors.
CRC errors can occur due to collisions or noise on the network. If they occur frequently, they may indicate a hardware transceiver malfunction or an improperly designed channel (e.g. improper loading, termination, etc).
Long packet error (>249bytes) could occur if transmissions from separate devices were concatenated. This could happen in far/near scenarios where the two devices cannot hear each other, but the protocol analyzer can hear both of them.
Oscillograph
Visually to see the noise on a certain channel

21. Reference document point out FTT10 Chips can sustain how large harmonic frequency
FTT-10 / FT31x0
Speed rate: 78kbps
Peak to peak voltage: round 1.4V
Environmental parameter
Refer to LONWORKS® Control Products Environmental Specifications and MTBF Guide
Devices based on FTT-10 / FT31x0
Which is totally different from transceiver
Depend on devices itself (manufacturers should provide specification)

22. LonWorks Configuration Server

23. The communication status when disable any device at LonWorks Configuration Server. 
We need enable there have completely no signal across LON Channel while disable specific devices
Demo