can-gca2-en
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | can-gca2-en [2025/06/09 19:11] (current) – [The hardware] phg | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== CAN-GC2 Universal 16 port I/O node for CANBUS ====== | ||
+ | [[english|{{ | ||
+ | [[: | ||
+ | * [[: | ||
+ | * [[: | ||
+ | * [[: | ||
+ | * [[: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ^Copyright Peter Giling^ | ||
+ | |||
+ | The CAN-GC2 is a sister of the GCA50 with the same capabilities, | ||
+ | the CAN-GC2 can be mixed with GCA50 units on the same cable, but of course need different computer interfaces.\\ | ||
+ | The also available CAN-GC3 will bring a complete solution for DCC Model Railroading in DIY. \\ | ||
+ | The CAN-GC1e connects the computer with the CAN bus. All the well known MGV*/GCA* satellite boards are useable with the CAN-GC2. | ||
+ | |||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | ===== The pcboard ===== | ||
+ | |||
+ | | | ||
+ | |||
+ | |||
+ | A jumper makes it possible to set terminator on the last board in the RCAN chain.\\ | ||
+ | This jumper connects a 120 Ohm resistor to the RCAN system.\\ | ||
+ | White connectors at the back are compatible with all [[: | ||
+ | These interfaces are all electrical isolated from CANBUS by optocouplers.\\ | ||
+ | Power, as available in RCAN-cable, is -where ever important- generally only used for supply of RCAN board itself, \\ | ||
+ | with a few minor exceptions.\\ | ||
+ | As a standard recommandation for all CAN systems, connection and disconnection of cables is not possible while system is running.\\ | ||
+ | Using this cheap and rigid d-type connector with locking screws will avoid that connectors drop off accidently.\\ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== The hardware ===== | ||
+ | === Actual version (green pc-board) === | ||
+ | | {{: | ||
+ | | {{: | ||
+ | | {{: | ||
+ | | {{ : | ||
+ | ^ N.B. Only complete ordered kits will be supported! | ||
+ | \\ | ||
+ | ^ Housing is only for DIY 3D printing. | ||
+ | | {{ : | ||
+ | \\ | ||
+ | === Previous version (blue pc-board) === | ||
+ | |{{: | ||
+ | |{{: | ||
+ | |{{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ====Connections==== | ||
+ | * [[: | ||
+ | * For connection with interfaces, see instructions in propriate interface. | ||
+ | |||
+ | * **Attention: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Led functions ===== | ||
+ | ^ L1* ^ | ||
+ | | Can bus activity | ||
+ | |||
+ | * leds are blinking | ||
+ | |||
+ | |||
+ | ===== PB1 functions ===== | ||
+ | ^ PB1 ^ Function ^ | ||
+ | | After power on | Switch to learn mode for setting a node number. A second push will leave this mode. | | ||
+ | \\ | ||
+ | |||
+ | =====Port connectors===== | ||
+ | {{: | ||
+ | \\ | ||
+ | |||
+ | |||
+ | |||
+ | refer to: | ||
+ | [[PSK-Interface connections-en|**Connection interfaces**]] | ||
+ | |||
+ | ===== Connector J4 10pin header ===== | ||
+ | |||
+ | ^ LocoIO port ^ Pin # ^ | ||
+ | | +5V | 1 | | ||
+ | | GND | 2 | | ||
+ | | 1 | 3 | | ||
+ | | 2 | 4 | | ||
+ | | 3 | 5 | | ||
+ | | 4 | 6 | | ||
+ | | 5 | 7 | | ||
+ | | 6 | 8 | | ||
+ | | 7 | 9 | | ||
+ | | 8 | 10 | | ||
+ | \\ | ||
+ | ===== Connector J3 10pin header ===== | ||
+ | |||
+ | ^ LocoIO port ^ Pin # ^ | ||
+ | | +5V | 1 | | ||
+ | | GND | 2 | | ||
+ | | 9 | 3 | | ||
+ | | 10 | 4 | | ||
+ | | 11 | 5 | | ||
+ | | 12 | 6 | | ||
+ | | 13 | 7 | | ||
+ | | 14 | 8 | | ||
+ | | 15 | 9 | | ||
+ | | 16 | 10 | | ||
+ | ===== Direct connection of leds to outputs===== | ||
+ | [[http:// | ||
+ | \\ | ||
+ | ===== Reed switches and hall sensors ===== | ||
+ | Read switches and hall sensors can be used as feed-back sensors.\\ | ||
+ | However, since the contact information inside the CAN-GC2 is arranged so that the unit is\\ | ||
+ | low sensitive for distorsions, | ||
+ | In addition to that, reed-contacts usually give more than 1 pulse when activated, known as ' | ||
+ | For this way of sensoring, a special pulse-extender is available. See __**[[gca173-en|Hall sensor and reed switch unit]]**__\\ | ||
+ | |||
+ | |||
+ | ===== Hardware for CAN-GC2 ===== | ||
+ | |||
+ | Boards, programmed processors and complete kits are available from www.phgiling.net.\\ | ||
+ | With a proper tool, it is possible to do the programming of the chip yourself.\\ | ||
+ | The programmer , used for these chips is called PICKIT3 from Microchip.\\ | ||
+ | The on-board ICSP connector is useable for this programmer.\\ | ||
+ | |||
+ | \\ | ||
+ | < | ||
+ | |||
+ | ===== Setup ===== | ||
+ | {{: | ||
+ | |||
+ | ====Reset EEPROM==== | ||
+ | Hold down the button at power on to reset/ | ||
+ | * port 1-8 switch with address 1-8 | ||
+ | * port 9-16 block with address 9-16 | ||
+ | The same can be achieved by sending a **[[: | ||
+ | |||
+ | ====Set==== | ||
+ | Set the first found change. This button must be pushed multiple if more then one port or setting is changed.\\ | ||
+ | The sequence of change check is: | ||
+ | - Ports | ||
+ | - Node configuration | ||
+ | - SoD | ||
+ | |||
+ | ====Set all==== | ||
+ | Set all ports and options.\\ | ||
+ | |||
+ | ====Save output state==== | ||
+ | Write the output state in EEPROM after detecting a **power off command** on the CANBUS.\\ | ||
+ | The outputs will be restored after the [[: | ||
+ | |||
+ | ====Short events==== | ||
+ | Ignore the event node number and compare the event number only.\\ | ||
+ | |||
+ | ====Long events==== | ||
+ | For long events the BUS variable on the interface tab of sensors, switches and other objects is used to address the module its node number.\\ | ||
+ | The address variable is equal to the one used with short events.\\ | ||
+ | |||
+ | |||
+ | ====SoD==== | ||
+ | **" | ||
+ | The [[: | ||
+ | The SoD address should be the same as set for the __**[[: | ||
+ | ===All=== | ||
+ | If ' | ||
+ | |||
+ | ====Node Nr.==== | ||
+ | For outputs with long events only.\\ | ||
+ | Inputs will use the **[[: | ||
+ | |||
+ | ====Port types==== | ||
+ | ^ Type ^^ Description ^ Recommendation ^ | ||
+ | | **IN** | Input | Normal input port. | Push buttons, feedback of servos/ | ||
+ | | **BK** | Block | Input with a 2 seconds delayed off. (±50ms) | Occupancy detectors. | | ||
+ | | **SW** | Switch | Continuous output. | Single coil switch drivers like servos. | | ||
+ | | **PU** | Pulse | Output with x ms activation time. (±50ms) | Note: A [[: | ||
+ | |||
+ | ====Pulse time==== | ||
+ | Activation time for pulse type outputs.\\ | ||
+ | |||
+ | ====Inv==== | ||
+ | Inverts the port.\\ | ||
+ | \\ | ||
+ | |||
+ | ====Test==== | ||
+ | Every port has a test button in which also the current state is displayed as a " | ||
+ | The state is only updated after pushing a test button.\\ | ||
+ | |||
+ | \\ | ||
+ | ====Usage==== | ||
+ | Shows the Rocrail object ID which is linked to this port.\\ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ====LEDs==== | ||
+ | The information of the LEDs is explained on the firmware page: **[[: | ||
+ | |||
+ | |||
+ | \\ | ||
+ | =====Node Variables===== | ||
+ | ^ NV# ^ Purpose ^ | ||
+ | | 1 | General configuration | | ||
+ | | 2...17 | ||
+ | | 18 | CAN ID | | ||