MicroLYNX Party Mode

Party Mode Communications – Troubleshooting

When a unit has been put into Party Mode, all communications require a Ctrl J (linefeed) to clear the buffer and act as an end of line delineator. Communications then must begin with the desired unit's device name. The device name is the only command in the Lynx software language that IS case sensitive. It can be set either via the Address Switches on the side of the unit, or via the software command DN (for example DN="A" sets the unit to be A, whereas DN="a" sets the unit to be lowercase a).

It should also be noted that if the Address Switches have been set to a specific device name, it will override any software set device name.Once the Ctrl J has been issued, each MicroLynx in the system them waits for its device name. If its device name is not the first character it sees, it will disregard all other characters until the next Ctrl J is issued.It is a common practice in Party Mode systems to turn the echo off for the units not directly connected to the PC. This cleans up confusion for units either accepting their commands or waiting for their device name. However, when the echo has been turned off, it will appear that the unit is not communicating. The ECHO command can be turned on by issuing the ECHO = 0 command. This turns on the echo for both RS-232 and RS-485 lines. It should be noted that if the echo is off, you will not see the typed command to turn it back on.Another common problem is when there is a program residing in the problem unit. It may have commands executing such that one does not appear to be communicating when, in reality, there is just insufficient time to input your entire command. This can occur due to a print command in the program, or a hardware switch that is overriding the system (a "start input" for example).

Finally, the unit connected to the PC may have been set to have a different BAUD rate than the PC setting. In this situation, you must attempt to establish communications at each available BAUD rate (4800, 9600, 19200, and 38400). Unfortunately, if this is the problem, you may have to attempt each fix at each BAUD rate.

The following is a sequence for troubleshooting Party Mode Communications:

Hardware

  1. Connect to only one MicroLynx at a time. Make sure that the UPGRADE DIP switch on the side of the unit is in the OFF position (Toward the Fan). Check that the communications cable is functional by either using it with another unit, or by shorting transmit (TX) to receive (RX) (Shorting allows all typed characters to be directly echoed back to the terminal). This test will verify the functionality of the communications cable.


  2. To simplify things, set the Address DIP switches to Address 0 = ON, Address 1 = OFF, and Address 2 = OFF. This way we know that the unit will be device "A" since the hardware address settings override any software set device name.


Software

  1. Verify that the Terminal Window says "Connected" (if not, double click where it says "Disconnected" to connect, or use the phone icon in the toolbar). Type Ctrl J, then capital A into the Terminal Window. (If A is echoed back to the screen, skip ahead to "Resetting Factory Defaults") If nothing appears, type ECHO=0, then Ctrl J into the Terminal Window and Repeat Step 2. Note: you will not see the letters as you type ECHO=0. (If you have hit any other key, or lowercase "a", you will need to type Ctrl J, then A before ECHO=0) If you still do not see the A after setting the echo back on, try typing Ctrl C while watching the Green LED on the top of the MicroLynx. If the Light blinked once, then you are communicating (you just simulated a cycle power) and the unit must either be running a program or have a hardware switch overriding the system. If the light did not blink, re-check your Hardware wiring, verify that you have the correct input voltage range, and double check the cable again (If still there is no response, contact Applications Support). To try to stop a program from running, you can type Ctrl J, then A, then hit the ESC key. Then repeat step 2. If there is something printing to the screen, you must get the Ctrl J, A, and ESC input between print lines. If a hardware switch could be interrupting communications, it will be necessary to manually change the state of each switch. (This can be done by turning the DIP switches for the I/O lines into the ON position, then connecting a wire from each I/O line to ground (Pin 8) one by one and testing communications). If your unit could have been set to a BAUD rate other than the Factory Default (9600), then you must attempt the above steps at each Baud rate available (Go to Edit>>Preferences>>Comm Settings, then select and apply).


  2. If all attempts fail, contact IMS Applications Support (see above).


Resetting Factory Defaults

  1. If you have typed the Ctrl J, then A, and you saw an A appear in the Terminal Window, next type PARTY=0, then Ctrl J (this will take the unit out of party mode). Turn the Address DIP switches into the OFF position (otherwise, when you power down and back up, it will revert back to party mode with the specified address). Next, type RTFD into the Terminal window (no Ctrl J required) then hit ENTER (this returns the unit to the factory default settings).


  2. Type SAVE into the Terminal window (no Ctrl J required) then hit ENTER (otherwise it will revert back to the previous saved settings when power is cycled).


Your unit is now set back to the factory defaults.