Zebra FS40 Fixed Scanner¶
What It Is¶
The Zebra FS40 is a fixed industrial barcode scanner that reads 2D barcodes (DataMatrix, QR codes) on labels as they pass on the conveyor. It uses Zebra's Aurora software platform for configuration and communicates with GateKeeper via TCP/IP using a dual-port architecture.
Which Sites Use It¶
- Zebra Futures Lab
Connection Details¶
| Detail | Value |
|---|---|
| Protocol | TCP/IP |
| Control port | 2001 (for trigger commands) |
| Results port | 2002 (for barcode data in Push mode) |
| Connection string format | SCANNER_IP:2001 (e.g., 192.168.100.210:2001) |
| GateKeeper role | Client -- GateKeeper connects TO the scanner |
How to Tell If It Is Working¶
- Diagnostics panel: Camera shows "Connected" with a green indicator.
- Log message on startup:
[FS40] Connected successfully. TriggerMode=Software, TriggerString='T', Timeout=5000ms - LED indicators: The FS40 has status LEDs on the unit.
- Manual trigger: In diagnostics, trigger the scanner and check for barcode data.
How Triggering Works¶
| Mode | How It Works |
|---|---|
| Hardware | Photo-eye wired to FS40 external trigger input (production use) |
| Software | GateKeeper sends trigger command (T) to Control Port 2001 |
| Manual | Trigger via Aurora software interface |
At Zebra Futures Lab, the photo-eye is wired directly to the FS40 trigger input (Hardware mode).
Dual-Port Architecture¶
The FS40 uses two TCP ports: - Control Port (2001): Receives trigger commands from GateKeeper - Results Port (2002): Sends barcode data back to GateKeeper (in Push mode)
Both ports must be accessible from the GateKeeper PC.
Common Problems and Solutions¶
| Problem | Symptoms | Solution |
|---|---|---|
| Scanner not connecting | Log shows [FS40] Connection FAILED to {IP}:{Port} |
Check network cable, ping scanner IP, verify Aurora port settings |
| NOREAD | Log shows [FS40] NOREAD: No response after {X}ms |
Check barcode alignment, focus, lighting |
| Wrong port | Connected but no data | Verify Control Port and Results Port match Aurora settings |
| Trigger not working | No response to trigger command | Verify TriggerString matches Aurora configuration (default: T) |
Error Messages¶
| Error Message | What It Means |
|---|---|
[FS40] Connection FAILED to {IP}:{Port} |
Cannot connect to scanner -- network or power issue |
[FS40] NOREAD: No response after {X}ms |
Scanner triggered but no barcode read |
Aurora Software¶
The FS40 is configured using Zebra's Aurora software, which runs on the scanner itself. Aurora settings must be configured before deployment:
- Control Port number (default 2001)
- Results Port number (default 2002)
- Trigger string (default T)
- Output format and terminators
Aurora settings are not managed by GateKeeper -- they are configured separately on the scanner hardware.
When to Escalate¶
- Scanner LED shows no power
- Scanner is pingable but GateKeeper cannot connect to either port
- Aurora software shows errors
- Scanner reads barcodes in Aurora but not via GateKeeper (protocol mismatch)