Troubleshooting CompactClick Communication


CompactClick screen segments, or sensor processor boards (SPBs) communicate via RS232 to CompactControl.

Port settings are fixed baudrate, 38400 baud, 8 bits, No parity, 1 stopbit. The setting will be automatically set by CompactControl. It is not necessary to set this manually.

To troubleshoot CompactClick Communication, start with using the Communication status window.
Check that all elements can be seen in this window, and that status updates happen at regular intervals.

1. No screen elements are seen in the Communication status window
This indicates that there is no communication with CompactClick segments/SPBs.

  1. Check physical connection. The RS232 cable should go to the IN port of the first SPB, and connect trough a RJ-12 - DB9 connector to the PC. If the cable goes through a UTM, check that the communication module is running on the UTM, and open the Communication status or Device maintenance window on the UTM.
  2. Check that the CompactClick elements/SPBs have power.
  3. Check that the correct serial port is used. This can be viewed in Object inspector, under System components/CVcommunication/Device communication/SerialCommunication. If necessary, change the serial port in the registry.
  4. In the Object inspector window, check that CompactControl is sending and receiving data. On the System components/CVcommunication/Device communication/SerialCommunication page, there are byte and packet counters for transmit and receive, respectively. If received packets counters are not changing every few seconds, this indicates that the connection is faulty.
  5. Faulty serial port. The serial port on the computer may be defect (this may have been caused by an incorrect cable used between the PC and an SPB).

2. Not all screen elements are seen in the Communication status window
If the count of physically connected screen elements/SPBs differs from the number of reported screen elements in the communication status window, there are a number of possible causes for this:

  1. Broken connection between two screen segments/SPBs.
  2. Faulty SPB (does not communicate).
  3. Insufficient power for all SPBs.
  4. SPBs interconnected using the "Vertical" connection port. This may cause chain addresses to be generated incorrectly, again causing some SPBs to be ignored. See troubleshooting chain addresses below.

Try disconnecting all screen segments, restart CompactControl with only one segment connected (this needs to have its own power source. Verify that this segment is seen in the Communication status window. Then connect segments one by one, and verify that for each segment connected, a new entry in Communication status appears.

3. Chain addresses are wrong
Chain addresses are determined by the use of the 2 output ports from each SPB. Port 1 must be used for connections in the "Horizontal" direction, and port 2 is used in the "Vertical" direction. When this is used in an array of screen segments, the first (lowest) horizontal row will be numbered from 1 upwards, the second row from 33 upwards, the third row from 65 upwards, 4th row from 97 upwards, etc.

  1. Check that the number of entries (Screen segments) in Communication status matches the number of physical screen segments/SPBs.
  2. Check chain addresses in communication status, and verify that SPBs are numbered correctly. For example, for a 150(H) by 45(V) CompactClick screen, there are 10 by 2 elements, this means that the chain addresses should be 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42.
  3. Check that there are no duplicate chain addresses. This is also an indication of incorrect connection between segments.
  4. Check that all LEDs in all segments can be lit up by selecting an LED pattern from the Auto Calibrate window in CompactControl.