IO4-QuadOD

Fork project on GitHub

IO4 Quad Detector for DCCOD and CPod detector cards - hardwired, IO4 or WeMos/WiFi connected

QuadOD-Graphic
QuadOD-Graphic

 

 

IO4-QuadOD Version 2.0

First built: 2018-11

An IO4 peripheral baseboard for Chubb-style current sensing detectors.

Schematic
Schematic
Bot Silk
Bot Silk
Board
Board
Top Silk
Top Silk

Download IO4-QuadOD.gerbers.zip - Gerber Fabrication files
Download IO4-QuadOD.parts - Parts List (spreadsheet data)

 

IO4-QuadOD.bom

Parts Value Package Quantity Library Type/Feeder
X1, X2, X3, X4 0.156 KK-156-5 4x SPCoast PTH
DCCIN, TK1, TK2, TK3, TK4 0.200 MSTBA2 5x SPCoast PTH
CON1 2.1mm DCJ0202 1x SPCoast PTH
CON3, CON10 5MM SCREWTERMINAL-5MM-3 2x SPCoast PTH
BOARD1 BOARD BOARD-SEEED10X10-NOHOLES 1x SPCoast PTH
CON9 I2C I2C-L 1x SPCoast PTH
MCU Mini-R2 WEMOS-D1 1x SPCoast PTH
MT1, MT2, MT3, MT4 MOUNTINGHOLE MOUNTINGHOLE 4x SPCoast PTH
IO4-MASTER, IO4-SLAVE RJ12/6 RJ25-INVERTED 2x SPCoast PTH

Documentation

Description

This project is a simple baseboard for current sensing detectors. It was inspired (in reverse chronological order) by railnerd, MarkS, MRCS, RR-Cirkits and, of course, Dr Bruce Chubb.

The Quad-OD board has 4x connectors that can be populated with either MRCS cpOD or CMRI DCCOD occupancy detector cards. The board can be powered locally (with a +5vDC wall wart) or remotely (by a “IO4 Field Unit” I/O card), and provides 4x open drain “pull to ground when detected” occupancy feedback lines.

The IO4-QuadOD is a multi-purpose board - it supports 3 different use cases:

  1. It can be an IO4 peripheral using the SPCoast 6-pin RJ12 connector scheme,
  2. It can be hardwired using screw terminals and/or a 5VDC wallwart, or
  3. With the addition of a WemosD1Mini 8266 MCU board, it can become a distributed WiFi and/or I2C peripheral. (Software not provided…)

THere were several previous versions:

  • Rev 1.0 was a conceptual effort to build a self contained unit (like the [[IO4-Detector]], but with DCC-OD design instead of a Paisley one) but the complexity and inflexability doomed it…
  • Rev 2.0A simplified things to simply use DCC-OD style cards AS-IS. Unfortunately, the card-to-card spacing was a bit too tight, and 4x cards wouldn’t fit without severely distorting the PCB.
  • Rev 2.0B is the same design as 2.0A, but with fixed spacing.

The 2x IO4 connections are arranged so that two adjacent control points can both monitor a shared set of detected blocks (usually used by approach logic…). One (master) provides a power source, the other (slave) does not; all other signals from the IO4 connector are in common. This implies that both need to be connected to INPUT configured ports.

This technical documentation is licensed under the CERN Open Hardware Licence v1.2