Simplex 4007ES Troubleshooting Guide

Overview

Simplex 4007ES integrations fail in predictable ways. The most common root causes — tracked across Chipkin support projects — are:

Data vectoring not enabled on the panel (most common)
Hardware incompatibility between newer QuickServer hardware and the 4007ES RS-232 output
Driver mismatch — CAS Simplex 4100 driver used instead of the CAS Simplex 4007ES driver
Wrong port (Port A instead of Port B)
Dipswitch misconfiguration

[!WARNING] The Simplex 4007ES uses a different serial protocol than the Simplex 4100 and 4100ES and requires its own driver. Using the CAS Simplex 4100 driver on a 4007ES will produce no data or corrupted data.

This guide is organized by symptom. For initial configuration steps, open a Chipkin Support ticket. For the 4100 or 4100ES, see the Simplex 4100 Troubleshooting Guide.

Model Identification

Before troubleshooting, confirm the panel model. The 4007ES and 4100/4100ES look similar in the field and use incompatible drivers.

Panel	Driver Required	Notes
Simplex 4100	CAS Simplex 4100
Simplex 4100ES	CAS Simplex 4100
Simplex 4100U	CAS Simplex 4100
Simplex 4007ES	CAS Simplex 4007ES ⚠️	Different protocol — separate driver

[!TIP] The model number is on a label inside the panel door and on the main board. Photograph the label before any troubleshooting session — driver mismatch is the most common source of no-data errors on the 4007ES.

No Data (RX Counter = 0)

Symptom: The gateway RX counter is not incrementing. No data from the panel.

Work through these checks in order:

1. Confirm Data Vectoring Is Enabled

The 4007ES RS-232 port is not active by default. Data vectoring must be explicitly enabled by a qualified JCI/Simplex technician in the panel programming.

Do not proceed with any other troubleshooting until this is confirmed. A Chipkin engineer cannot enable data vectoring remotely.

Ask the technician to confirm in writing:

“Port B is configured for ASCII output with data vectoring enabled.”

2. Confirm Cable Is on Port B

Port A is the programming/display port and does not output user data. The RS-232 cable must be on Port B (secondary port).

3. Check TX/RX Pin Orientation

RS-232 requires a crossover — panel TX → gateway RX, panel RX → gateway TX:

Simplex Port B Pin	FieldServer / QuickServer Pin
TX (Transmit)	RX (Receive)
RX (Receive)	TX (Transmit)
GND	GND

If RX is zero but wiring looks correct, swap the TX and RX wires.

4. Verify Baud Rate Match

Baud rate must match on both panel and gateway. Default is 9600. Confirm the gateway serial port matches whatever the panel is programmed to.

5. Verify DIP Switch Settings

The main board dipswitches control the serial interface. The Simplex technician should photograph and confirm the dipswitch state matches the integration settings.

Port B Reported as “Abnormal”

Symptom: Simplex panel software reports Port B status as “Abnormal”. No TX/RX LED activity on the gateway. Factory reset does not resolve.

This is a documented hardware compatibility issue between the Simplex 4007ES RS-232 output and some QuickServer hardware generations. If an older SMC-generation gateway communicates successfully with the same panel while the newer QuickServer fails, that is a strong indicator of this issue.

Steps:

Check gateway firmware — Contact Chipkin Support with the QuickServer model and firmware version. A firmware update may be required for 4007ES compatibility.
Test with an alternate gateway — If available, test with an older gateway to isolate whether the issue is panel-side or gateway-side.
Do not repeat site visits — If data vectoring is confirmed correct, cable is on Port B, and the gateway still shows “Abnormal”, this is not a panel configuration problem.

[!CAUTION] If an older gateway works with the same panel but the new QuickServer does not, do not assume panel misconfiguration. Escalate to Chipkin for RMA evaluation instead of cycling through repeated site visits.

Driver Mismatch

Symptom: RX counter is incrementing but point data is wrong, corrupt, or points are missing.

The CAS Simplex 4100 driver is not compatible with the 4007ES. Using the wrong driver produces partial or corrupt data.

Panel Model	Correct Driver
Simplex 4007ES	CAS Simplex 4007ES
Simplex 4100 / 4100ES / 4100U	CAS Simplex 4100

Verify the driver in the FieldServer Toolbox / QuickServer configuration. If the wrong driver was used, request a corrected configuration file from Chipkin.

Points Missing or Wrong

Symptom: RX counter is incrementing and driver is correct, but not all expected points appear or point labels don’t match the panel.

Root Cause	Fix
Incomplete points list at intake	Request the full zone/point database printout from the Simplex technician
Labels differ from as-built	Compare delivered config against current panel database — request updated printout
Zone count changed since config was built	Submit updated points list to Chipkin for a config revision

Gateway Not Visible to BMS / SCADA / NMS

Symptom: Panel data is being received by the gateway, but the target system cannot see the gateway.

Target	What to Check
BACnet/IP	Confirm gateway IP is reachable (ping). Verify BACnet UDP port 47808 is not blocked. Check Device Instance is unique on the network.
Modbus TCP	Confirm TCP port 502 is not blocked. Verify gateway IP in SCADA config.
SNMP	Confirm MIB file is loaded in the NMS. Verify community string matches.

Gateway Configuration Reference

Quick reference for verifying gateway settings. For full initial configuration, open a Chipkin Support ticket.

Serial Port

Parameter	Value
Driver	CAS Simplex 4007ES
Port	COM1 (or port label on gateway)
Baud Rate	Match panel (typically 9600)
Data Bits	8
Parity	None
Stop Bits	1

Network

Parameter	Example Value
IP Address	10.60.82.199
Subnet Mask	255.255.255.0
Default Gateway	10.60.82.1

Quick Diagnostic Decision Tree

Start by checking whether the FieldServer or QuickServer RX counter is incrementing.
- If no: confirm whether JCI has enabled data vectoring.
  - If data vectoring is not confirmed: stop and contact the JCI technician before going further.
  - If data vectoring is confirmed but there is still no data: continue with panel-side wiring checks.
    - Check whether the cable is on Port B instead of Port A.
      - If not: move the cable to Port B.
    - Check whether TX and RX are crossed correctly.
      - If not: swap TX and RX.
    - Check whether baud rate matches on both ends.
      - If not: align the baud rate.
    - Check whether the panel reports Port B as “Abnormal.”
      - If yes: treat it as a hardware compatibility issue and escalate to Chipkin.
- If yes: check whether the correct driver is loaded, specifically CAS Simplex 4007ES.
  - If not: request a corrected config from Chipkin.
  - If yes: check whether all expected points are present.
    - If no: submit the updated points list to Chipkin.
    - If yes: check whether the BMS, NMS, or SCADA platform is receiving data.
      - If no: check IP settings, port values, and Device Instance or MIB configuration.
      - If yes: communication is confirmed.

Summary: Common Failures at a Glance

Symptom	Most Likely Cause	Fix
RX counter = 0	Data vectoring not enabled	JCI technician enables Port B output
RX counter = 0	Wrong port (Port A)	Move cable to Port B
RX counter = 0	TX/RX swapped	Swap the two signal wires
RX counter = 0, Port B “Abnormal”	Hardware compatibility issue	Check firmware; escalate to Chipkin
Garbled or corrupt data	Wrong driver (4100 vs 4007ES)	Request corrected config from Chipkin
Points missing	Incomplete points list	Request updated zone database from JCI
BMS/NMS cannot see gateway	Network/protocol misconfiguration	Check IP, port, BACnet instance, MIB

Simplex 4100 Troubleshooting Guide — configuration, wiring, and diagnostics for the 4100 family
BACnet Discovery and Network Architecture Reference
Modbus Commissioning Site Toolkit Checklist

Chipkin Tools

FieldServer — Protocol conversion gateway
QuickServer — Compact protocol conversion gateway
Chipkin Support — Include panel model, firmware version, and RX counter status in your ticket