Note the following details of the code protection feature on Microchip devices:
•Microchip products meet the specification contained in their particular Microchip Data Sheet.
•Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.
•There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
•Microchip is willing to work with the customer who is concerned about the integrity of their code.
•Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break Microchip’s code protection feature may be a violation of the Digit al Millennium Copyright A ct. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
Information contained in this publication regarding device
applications and t he lik e is provided only for your convenience
and may be su perseded by upda t es . It is y our responsibility to
ensure that your application meets with your specifications.
MICROCHIP MAKES NO REPRESENTATIONS OR
WARRANTIES OF ANY KIND WHETHER EXPRESS OR
IMPLIED, WRITTEN OR ORAL, STATUTORY OR
OTHERWISE, RELATED TO THE INFORMATION,
INCLUDING BUT NOT LIMITED TO ITS CONDITION,
QUALITY, PERFORMANCE, MERCHANTABILITY OR
FITNESS FOR PURPOSE. Microchip disclaims all liability
arising from this information and its use. Use of Microchip
devices in life supp ort and/or safety ap plications is entir ely at
the buyer’s risk, and the buyer agrees to defend, indemnify and
hold harmless M icrochip from any and all dama ges, claims,
suits, or expenses re sulting from such use. No licens es are
conveyed, implicitly or otherwise, under any Microchip
intellectual property rights.
Trademarks
The Microchip name and logo, the Microchip logo, Accuron,
dsPIC, K
EELOQ, KEELOQ logo, microID, MPLAB, PIC,
PICmicro, PICSTART, PRO MATE, rfPIC and SmartShunt are
registered trademarks of Microchip Technology Incorporated
in the U.S.A. and other countries.
AmpLab, FilterLab, Linear Active Thermistor, Migratable
Memory, MXDEV, MXLAB, SEEVAL, SmartSensor and The
Embedded Control Solutions Company are registered
trademarks of Microchip Technology Incorporated in the
U.S.A.
Analog-for-the-Digital Age, Application Maestro, CodeGuard,
dsPICDEM, dsPICDEM.net, dsPICworks, ECAN,
ECONOMONITOR, FanSense, FlexROM, fuzzyLAB,
In-Circuit Serial Programming, ICSP, ICEPIC, Mindi, MiWi,
MPASM, MPLAB Certified logo, MPLIB, MPLINK, PICkit,
PICDEM, PICDEM.net, PICLAB, PICtail, PowerCal,
PowerInfo, PowerMate, PowerTool, REAL ICE, rfLAB, Select
Mode, Smart Serial, SmartTel, Total Endurance, UNI/O,
WiperLock and ZENA are trademarks of Microchip
Technology Incorporated in the U.S.A. and other countries.
SQTP is a service mark of Microchip Technology Incorporated
in the U.S.A.
All other trademarks mentioned herein are property of their
respective companies.
Microchip received ISO/TS-16949:2002 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
are for its PIC
devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’s quality system for the design
and manufacture of development systems is ISO 9001:2000 certified.
All documentation becomes dated, and this manual is no exception. Microchip tools and
documentation are constantly evolving to meet customer needs, so some actual dialogs
and/or tool descriptions may differ from those in this document. Please refer to our web site
(www.microchip.com) to obtain the latest documentation available.
Documents are identified with a “DS” number. This number is located on the bottom of each
page, in front of the page number. The numbering convention for the DS number is
“DSXXXXXA”, where “XXXXX” is the document number and “A” is the revision level of the
document.
For the most up-to-date information on development tools, see the MPLAB
Select the Help menu, and then Topics to open a list of available on-line help files.
INTRODUCTION
®
IDE on-line help.
This chapter contains general information that will be useful to know before using the
LIN Serial Analyser. Items discussed in this chapter include:
• Document Layout
• Conventions Used in this Guide
• Recommended Reading
• The Microchip Web Site
• Customer Support
• Document Revision History
DOCUMENT LAYOUT
This document describes how to use the LIN Serial Analyser. The manual layout is as
follows:
• Chapter 1. “LIN Serial Analyser Overview” – What the LIN Serial Analyser is,
what makes it a desirable development tool and what features are available.
• Chapter 2. “Getting Started – Quick Setup” – Describes the supplies needed to
set up and begin to use the LIN Serial Analyser.
• Chapter 3. “LIN Serial Analyser PC Program” – Describes the primary
elements of the interface.
• Appendix A. “LIN Serial Analyzer Technical Information” – Provides the
detailed schematic of the LIN Serial Analyser.
This user’s guide describes how to use LIN Serial Analyser. Other useful documents
are listed below. The following Microchip documents are available and recommended
as supplemental reference resources.
It is recommended that you become familiar with the documents listed below before
using the LIN Serial Analyser.
PICkit™ Serial Analyzer User’s Guide (DS51647)
LIN Specification Package 2.1
Microchip provides online support via our web site at www.microchip.com. This web
site is used as a means to make files and information easily available to customers.
Accessible by using your favorite Internet browser, the web site contains the following
information:
• Product Support – Data sheets and errata, application notes and sample
programs, design resources, user’s guides and hardware support documents,
latest software releases and archived software
• General Technical Support – Frequently Asked Questions (FAQs), technical
support requests, online discussion groups, Microchip consultant program
member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip
press releases, listing of seminars and events, listings of Microchip sales offices,
distributors and factory representatives
Preface
CUSTOMER SUPPORT
Users of Microchip products can receive assistance through several channels:
• Distributor or Representative
• Local Sales Office
• Field Application Engineer (FAE)
• Technical Support
• Development Systems Information Line
Customers should contact their distributor, representative or field application engineer
(FAE) for support. Local sales offices are also available to help customers. A listing of
sales offices and locations is included in the back of this document.
Technical support is available through the web site at: http://support.microchip.com.
DOCUMENT REVISION HISTORY
Revision A (June 2007)
• Initial release of this document.
Revision B (June 2008)
• Release describes new features of Revision 2.0 software.
The LIN Serial Analyser development system enables a Personal Computer (PC) to
communicate with a LIN (Local Interface Network) bus. The PC program uses a graphical user interface to enter and display message frames occurring on the target bus.
The LIN Serial Analyser connects to the system network using a three-position terminal
block.
Chapter 2. “Getting Started” will guide you through installing the PC program, the
Windows
1.2HIGHLIGHTS
This chapter discusses:
• LIN Serial Analyser Contents
• LIN Serial Analyser Development Tool
• LIN Serial Analyser Hardware
• LIN Serial Analyser Softwar e
LIN SERIAL ANALYZER
USER ’S GUIDE REV2.0
®
operating system drivers and setting up the hardware.
1.3LIN SERIAL ANALYSER CONTENTS
The LIN Serial Analyser kit contains the following items:
• LIN Serial Analyser
• Mini-B USB Cable
• LIN Serial Analyser CD-ROM
1.4LIN SERIAL ANALYSER DEVELOPMENT TOOL
The LIN Serial Analyser consists of several components, that together, make a network
debug and analysis tool. The user interface program runs on Microsoft
operating system compatible computers with a USB port.
The LIN Serial Analyser connects to the PC using a mini-B USB cable. The LIN Serial
Analyser interfaces to the target network using a three-position, screw-type terminal
block. Figure 1-1 illustrates the LIN Serial Analyser tool connected to a network.
The LIN Serial Analyser connects to a Microsoft® Windows® operating system
compatible computer using a USB port. It interfaces to the target network using a
three-position, screw-type terminal block.
FIGURE 1-2:LIN SERIAL ANALYSER
Status LEDs
LIN Tool
PC
USB Port
1.5.1Status LEDs
The Status LEDs indicate the status of the LIN Serial Analyser. An illuminated LED
means:
• USB (green) – Power has been applied to the LIN Serial Analyser by the USB
port.
• Busy (yellow) – The LIN Serial Analyser is communicating with the LIN network.
• LIN (blue) – The LIN Serial Analyser is connected to the target bus.
The USB port connection is a USB mini-B connector. Connect the LIN Serial Analyser
to the PC using the cable supplied with the device.
FIGURE 1-3:LIN SERIAL ANALYSER NETWORK AND POWER
Terminal
Block
Screws
Auxiliary
Power
1.5.3Network Communication Connector
The communication connector connects to the target device using a three-position,
screw clamp terminal block. The pin assignments, labeled on the top of the device, are:
• VBAT – Positive battery connection for voltage supplied by the vehicle
• LIN – Bidirectional data I/O
• GND – Common chassis, power and serial ground
1.5.4Power Jack
The device us es a stan dard, 6.5 x 2.5 DC pow er plug. Th e center pi n is posit ive. Powe r
can be supplied either through the power plug or the network connector as the two are
internally connected.
1.6LIN SERIAL ANALYSER SOFTWARE
1.6.1User Interface Program
The LIN Serial Analyser PC program displays all of the board’s bus activity via the
software’s Transaction window, displayed on the connected PC. This is useful for
“sniffing” the bus and tracking message frames.
Chapter 3. “LIN Serial Analyser PC Program” explains the installation and operation
of the program.
Network
Connection
1.6.2Firmware
The LIN Serial Analyser firmware is explained in Chapter 9. “PICkit™ Serial Analyzer
Firmware” of the “PICkit™ Serial Analyzer User’s Guide” (DS51647).
• Using the LIN Serial Analyzer for the First Time
• Software Installation
• Running LIN Serial Analyser Program
2.2USING THE LIN SERIAL ANALYZER FOR THE FIRST TIME
The LIN Serial Analyser is shipped preprogrammed and ready for use. The user needs
to supply:
• A wiring harness with appropriate connections to its system network
• A power supply (nominal 13.8V)
Before making any connections, the software must be installed on the host system. The
user must have administrator level rights to install some of the required programs. For
more information, see Section 2.3 “Software Installation”.
Power is supplied either through the round, power plug or the terminal block. The
positive and negative terminals and power plug are common. Supplied power must be
in the range of 8.0V to 30.0V with a nominal value of 12.0-14.4V. Less than 5.0 mA of
current is required to power the LIN transceiver section of the unit.
Internal jumper, E1, configures the unit as either a master or slave node. A 1.0 kΩ bus
pull-up resistor is enabled when E1 is connected across A and B. With the jumper
removed, an internal 30 kΩ resistor is retained.
The unit is configured as a master node as shipped.
2.3SOFTWARE INSTALLATION
All necessary files are contained on the Compact Disc (CD) supplied with the device.
2.3.1Installing the LIN Serial Analys er Program
1. Run setup.exe from the CD.
2. Select Install when prompted and follow any instructions.
Note:The LIN Serial Analyser program requires the Microsoft
version 2.0.
The PC host program is uninstalled with the control panel’s add/remove utility.
®
.NET Framework
2.4RUNNING LIN SERIAL ANALYSER PROGRAM
Before starting the LIN Serial Analyser software:
• The analyzer must be connected to the PC by a USB cable
• The analyzer must be powered up
The analyzer’s green USB and blue LIN lights will be on when these conditions are
met.
There is a hard-wired, loopback bus path, so connection to a network is not needed for
testing the installation.
To start the software:
1. On the Windows operating system taskbar, click Start.
2. Click All Programs>Microchip Technology Inc.>
3. Click Setup>COM port
4. From the pull-down menu, select the USB port to be used.
Note:Only available, plugged in USB ports are displayed by the pull-down menu.
If the correct serial port is not displayed, verify that the USB hardware is
correctly installe d.
5. In the menu’s text box, type the appropriate baud rate value.
6. Click OK.
7. Verify operation by selecting one of the preset messages from the Master
Message area.
Bus activity is indicated by the analyzer’s yellow BUSY light flickering.
A message will be displayed in the Bus Transaction window with:
When the LIN Serial Analyser’s software program starts, the window, shown in Figure ,
appears. The commands are accessed through the pull-down menus at the top of the
interface.LIN Serial Analyzer User Interface
This window, shown in Figure 3-1, constantly monitors and display bus traffic when in
the “Display All” mode. Any message frames seen on the bus are shown, regardless of
the source.
The data is displayed as it is seen on the bus without modification.
This section describes the window’s fields.
FIGURE 3-1:MESSAGE FRAMES DISPLAY
3.3.1TimeStamp
This field of the Transaction window displays the time, in seconds, since the last frame
was received. The value is reset to zero when the window is cleared.
The value can also be cleared by clicking on the “TimeStamp” column label.
3.3.2ID (Identifier)
This field displays the ID byte, including the upper two parity bits.
3.3.3Data
From zero to eight data bytes are displayed in this field. The data is in the hexadecimal
format (without the leading characters, ‘0x’), with the bytes separated by spaces.
3.3.4Checksum
The last field of a frame is the checksum. The checksum contains the inverted, eight-bit
sum with carry, over all data bytes or all data bytes and the protected identifier.
3.3.5ChkSumType
This field indicates whether a “classic” or “enhanced” equation was used for the checksum calculation. For messages sent via the Master Message group box, the type of
calculation is configured in the checksum portion of the Master Message group box
(see Section 3.8.3 “Checksum Group”).
• Classic – Checksum calculation over the data bytes only. Used for the master
request frame, slave response frame and communications with LIN 1.x slaves.
An eight-bit sum with carry is equivalent to the sum of all values and subtracts
255 every time the sum is greater than or equal to 256.
• Enhanced – Checksum calculation over the data bytes and the protected identifier
byte. Used for communication with LIN 2.x slaves.
The checksum is calculated both ways when a message frame is received. A match is
displayed either as “Classic” or “Enhanced”. If neither result matches the incoming
data, “ERROR” is displayed.
3.3.6Baud
This field shows the actual, calculated bit rate observed during the Auto-Baud Detect
period of the current frame.
The “Open” dialog box loads configuration and master message frames from a
user-selected file into the “Master Frames” field, so that they can be sent (see
Section 3.8.1 “Master Frames Field”).
By default, the dialog box, shown in Figure 3-2, displays the file that was last used in
the previous session.
T o display the dialog box, go to the pull-down menus at the top of the user interface and
select File>Open
FIGURE 3-2:FILE OPEN WINDOW
.
3.4.2Save
The “Save” dialog box saves configuration and master message frames, displayed
in the “Master Frames” field, to a previously selected *.ini file (see
Section 3.8.1 “Master Frames Field”.) By default, the dialog box populates the
file name that was last used in the previous session.
T o display the dialog box, go to the pull-down menus at the top of the user interface and
select File>Save
The “Save As” dialog box saves or appends configuration and master message
frames, displayed in the “Master Frames” field, to a preselected file (see
Section 3.8.1 “Master Frames Field”). The default file name is the last used file from
the previous session.
To display the dialog box, shown in Figure 3-3, go to the pull-down menus at the top of
the user interface and select File>Save As
FIGURE 3-3:FILE “Save As” WINDOW
.
3.4.4Print, Print Setup, Print Preview
These three functions relate to printing the contents of the Transaction window.
Print Setup
will appear.
The printing function clears the contents of the Transaction window, but does not reset
the time-stamp.
All of these functions are accessible through the File
configures the printing attributes and Print Preview displays how the print
pull-down menu.
3.4.5Exit
Selecting File>Exit terminates the LIN Serial Analyser software program.
The Slave Response setup function specifies message frames that are published to the
bus whenever the correct ID is recognized.
FIGURE 3-6:SLAVE RESPONSE SETUP WINDOW
To display the dialog box, select Setup>Slav e Response
.
3.5.4Slave Response Frames Field
The “Slave Response Frames” field is composed of 0 to n rows of one or more messages that are sent over the bus in response to a valid ID byte. These messages can
be entered manually, loaded from a previously saved session, or both.
When the response is sent, it is displayed in the Transaction window if it is open and
active.
Messages in the “Slave Response Frames” field can also be saved for reuse (see
Section 3.4.2 “Save” and Section 3.4.3 “Save As”).
3.5.4.1RESPONSE SYNTAX
Messages must consist of the ID byte without parity bits and the data bytes, all
separated by spaces. All inputs are in hexadecimal radix.
The checksum is not included; it is calculated at send time unless the “forced” Checksum option is selected.
Comments or notes may be attached to each frame by prefacing it with a
semi-colon (;). Any text after the semi-colon will be disregarded and not transmitted. All
notes will be saved in the selected .ini file and reloaded when reopened.
3.5.4.2DEVELOPING AND STORING RESPONSE CONTENT
To manually add a slave response message content to the “Slave Response Frames”
field:
1. Click the Add button. A second window displays for creation of the new message.
2. Type the message in the text box.
3. Click OK.
To load a pre-existing message to the “Slave Response Frames” field:
WARNING
Importing a file into the “Slave Response Fram es” fi eld ov er writes any content that previously had been in that field.
1. From the pull-down menus, select File>Open
2. In the dialog box’s list box, select the desired *.ini file.
3. Click Open.
To delete some slave message content:
1. In the “Slave Response Frames” field, select the content to be deleted by doing
one of the following:
•To select adjacent rows of cont ent – Click on the first row, scroll down to the
last row and hold down <Shift> while clicking.
•To select non-adjacent rows of content – Hold down <Ctrl> while clicking each
row.
2. Click Delete.
To edit some slave message content:
1. In the “Master Frames” field, select the content line to be edited
1. Click Edit. A second window displays to edit hte message.
2. Make and corrections or additions to the message in the text box.
3. Click OK
To store a slave response message(s) into the buffer:
1. In the “Slave Responser Frames” field, select the content to be stored by doing
one of the following:
•To select adjacent rows of cont ent – Click on the first row, scroll down to the
last row and hold down <Shift> while clicking.
•To select non-adjacent rows of content – Hold down <Ctrl> while clicking each
row.
2. Click Save.
The highlighted message content is stored, working top-to-bottom through the
“Slave Response Frames” field.
The internal buffer status is updated to reflect the amount a bytes used and
remaining. If the amount of buffer space is exceeded, the Save operation is
aborted and a error message displayed. Reduce the number or size of the messages to be written to the buffer and retry the Save.
1. See Section 3.4.2 “Save” and Section 3.4.3 “Save As”.
3.5.4.3SLAVE RESPON S E FR AMES FIELD ELEMENTS
This section describes the “Slave Response Frames ” field’s two elements.
3.5.4.3.1ID
The “ID” element displays the identifier byte that is compared to identifier bytes
received from the bus. The ID is entered without the upper two parity bits. Parity is calculated and appended when the message frame is stored in the inernal buffer memory.
The acceptable range of values is 00 to 3F hex (0 to 63 decimal).
3.5.4.3.2DATA
The “Data” portion of the “Slave Response Frames” field displays zero to eight-byte val-
ues, separated by spaces. This are the actual bytes sent over the bus in response to a
recognized ID.
3.5.5Slave Response Message Controls
3.5.5.1SAVE BUTTON
Clicking this button stores the selected message content highlighted in the “Slave
Response Frames” field (see the “Save” procedure in Section 3.5.4.2 “Developing and Storing Response Content”).
3.5.5.2ADD BUTTON
Click the Add button to add a new message to the “Slave Response” field
3.5.5.3EDIT BUTTON
Allows the selected message in the “Slave Response Frames” field to be edited.
3.5.5.4DELETE BUTTON
Clicking the Delete button deletes the content that is highlighted in the “Master Frames”
field. (see the “Delete” procedure in Section 3.5.4.2 “Developing and Storing Response Content”).
3.5.5.5CLEAR ALL BUTTON
Clicking this button clears the both the contents of the “Slave Response Frames” win-
dow and the internal buffer memory. The buffer status is updated to show no used bytes
and bytes remaining.
3.5.6Checksum Group
The checksum value is computed at send time. Selecting one of the
option buttons in the “Checksum” group, shown at right, determines
the type of checksum that will be calculated for all transmitted
master message frames, highlighted in the “Master Frames” field.
• classic – The checksum includes all data bytes.
• enhanced – The checksum includes identifier byte and all data
bytes.
• forced – (Enabled only in Debug mode.) The last byte in the message string is
sent in place of the calculated checksum. This is useful in checking master error
handling.
This sections lists the commands on the Tools pull-down menu.
3.6.1Debug Mode
Selecting Tools>Debug Mode enables the user to debug bus or slave operational
issues.
One function forces a user-supplied checksum to be appended to a master message
to check a slave for proper error handling. In this mode, the generation of identifier
parity bits is inhibited and the identifier byte is transmitted without modification.
3.6.2Suppress Bus Time-out Error
The current implementation of the master task cannot refer to a LIN descriptor file, so
there is no way to determine the length of any received message. To calculate an
appropriate time-out value, multiply the length of an eight-byte frame times 140% of the
bit rate.
This value can be overridden by entering a fixed time-out value in the COM Setup
window, described in Section 3.5.1 “Setup COM port”.
3.6.3Clear Monitor Window
This function clears the Transaction window and resets the time-stamp.
3.6.4Filters
This opens a window to display all messages received through the Transaction window
but are sorted by ID number. The window is ‘live’ and shows current bus traffic. New
message frames received will overwrite previous data. This is useful in monitoring constanly changes data.
3.6.5Transmit
This option selects the Transmit Only mode. No received messages are displayed in
the Transaction window.
3.6.6Listen (Filter)
This option selects the Listen Only mode. Only non-duplicated messages are displayed
in the Transaction window.
When “snooping” bus message frames, this prevents the Transaction window from
becoming cluttered with repeated frames.
3.6.7Display All (Snoop) Default
This function selects the Display All mode. All messages seen on the bus are
displayed.
This mode is best used with the data logging feature to capture all bus traffic for later
analysis.
This button – located in the top, right corner of the interface – starts, pauses, or stops
the capturing of messages to the log file.
Before starting the logging process, select and open a log file (see Section 3.5.2 “Log File”).
To pause the logging process, click the button a second time.
3.8MASTER MESSAGE GROUP BOX
This functions in the group box to act as a master node on the LIN bus, sending the
previously constructed frames to the slaves on the bus.
This window will cause a bus conflict if another master appears on the network. Any
conflict will be shown in an active Transaction window as a bus error.
The group box, shown in Figure 3-7, consists of the:
• “Master Frames” field
• “Checksum” group
• Message controls
FIGURE 3-7:MASTER MESSAGE GROUP BOX
“Master Fram
Field
“Checksu
Group
Message
Controls
3.8.1Master Frames Field
The “Master Frames” field is composed of 0 to n rows of one or more messages that
can be sent over the bus for test purposes. These messages can be entered manually,
loaded from a previously saved session, or both.
When the message is sent, it and any response is displayed in the Transaction window
if it is open and active.
Messages in the “Master Frames” field can also be saved for reuse (see
Section 3.4.2 “Save” and Section 3.4.3 “Save As”).
3.8.1.1MESSAGE SYNTAX
Messages must consist of the ID byte without parity bits and the data bytes, all
separated by spaces. All inputs are in hexadecimal radix.
The checksum is not included; it is calculated at send time.
Comments or notes may be attached to each frame by prefacing it with a
semi-colon (;). Any text after the semi-colon will be disregarded and not transmitted. All
notes will be saved in the selected .ini file and reloaded when reopened.
1. See Section 3.4.2 “Save” and Section 3.4.3 “Save As”.
3.8.1.3MASTER FRAMES FIELD ELEMENTS
This section describes the “Master Frames” field’s two elements.
3.8.1.3.1ID
The “ID” element displays the identifier byte to be sent without the upper two parity bits.
Parity is calculated and appended at send time unless the application is in the Debug
mode (see Section 3.6.1 “Debug Mode”).
The acceptable range of values is 00 to 3F hex (0 to 63 decimal).
3.8.1.3.2DATA
The “Data” portion of the “Master Frames” field displays zero to eight-byte values,
separated by spaces.
3.8.2Message Controls
3.8.2.1SEND BUTTON
Clicking this button transmits the message content that is highlighted in the “Master
Frames” field (see the “Send” procedure in Section 3.8.1.2 “Developing and Storing Message Content”).
When the Send button is clicked, the message is sent once (see
Section 3.8.3 “Checksum Group”).
If the Transaction window is open and active, the message and any response will be
displayed.
3.8.2.2CONTINUOUS BUTTON
Clicking the Continuous button sends the selected message entry or entries continu-
ously, at an interval defined in the time control text box, described next. A second click
of the button stops the continuous transmissions.
Any number of messages may be selected for continuous broadcast. They will be
transmitted in the order they appear in the “Master Frames” field.
3.8.2.3TIME CONTROL
Used in conj unction with the Continuous button, this text box sets the interval, in
milliseconds, between message frames being sent in the Continuous mode.
Note:Due to service latency time in the Windows operating system environment,
the minimum time interval may be as high as 200 ms, regardless of desired
time set in the control box. Intervals less than 200 ms will be serviced as
fast as possible, but may not be less than the operating system minimum.
3.8.2.4ADD BUTTON
Click the Add button to add a new message to the “Master Frames” field
3.8.2.5EDIT BUTTON
Allows the selected message in the “Master Frames” field to be edited.
Clicking the Delete button deletes the content that is highlighted in the “Master Frames”
field. (see the “Delete” procedure in Section 3.8.1.2 “Developing and Storing Message
Content”).
3.8.3Checksum Group
The checksum value is computed at send time. Selecting one of the
option buttons in the “Checksum” group, shown at right, determines
the type of checksum that will be calculated for all transmitted
master message frames, highlighted in the “Master Frames” field.
• classic – The checksum includes all data bytes.
• enhanced – The checksum includes identifier byte and all data
bytes.
• forced – (Enabled only in Debug mode.) The last byte in the message string is
sent in place of the calculated checksum. This is useful in checking slave error
handling.
If a slave response is requested (a ID value with no data bytes), the checksum is not
computed and the field is left blank.
The checksum returned by the slave will be displayed in the “Checksum” field of the
Transaction window (see Section 3.3.5 “ChkSumType”.)
3.9STATUS BAR
The status bar at the bottom of the Interface window displays: