Differences

This shows you the differences between two versions of the page.

--- can-gca2-en [2019/01/18 23:51] – Link normalized rainerk
+++ can-gca2-en [2021/07/24 10:35] (current) – [SoD] rjversluis
@@ Line 10: / Line 10: @@
 ^Copyright Peter Giling^
-=====Firmware Copyright=====
-Copyright(c) MERG and Rocrail.\\
-Commercial use is prohibited.\\
- \\
+The CAN-GC2 is an alternative to the MGV50 with the same capabilities running on the CANBUS open source CAN standard. \\
-The CAN-GC2 is an alternative to the MGV50 with the same capabilities running on the mergCBUS open source CAN standard. \\
 the CAN-GC2 can be mixed with MGV50 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-GC1 connects the computer with the CAN bus. All the well known MGV*/GCA* satellite boards are compatible with the CAN-GC2.  \\
-MergCBUS  runs on 125 KBd.
+CANBUS  runs on 125 KBd.
@@ Line 31: / Line 26: @@
-A jumper makes it possible to set terminator on the last board in the mergCBUS chain.\\
+A jumper makes it possible to set terminator on the last board in the CANBUS chain.\\
-This jumper connects a 120 Ohm resistor to the mergCBUS.\\
+This jumper connects a 120 Ohm resistor to the CANBUS.\\
 White connectors at the back are compatible with all [[:mgv-overview-en|GCA(MGV)xx interfaces]].\\
-These interfaces are all electrical isolated from mergCBUS by optocouplers.\\
+These interfaces are all electrical isolated from CANBUS by optocouplers.\\
-Power, as available in mergCBUS-cable, is only used for supply of mergCBUS board itself.\\
+Power, as available in CANBUS-cable, is only used for supply of CANBUS board itself.\\
 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.\\
@@ Line 54: / Line 49: @@
 |{{:cbus:can-gc2-pcb.pdf|The pcboard and parts positions}}  |
 |{{:cbus:can-gc2-bomfile.pdf|The partslist}}  |
-|{{:cbus:can-gc2_gerber.zip|Gerber files}}  |
 \\
@@ Line 154: / Line 149: @@
 ====Save output state====
-Write the output state in EEPROM after detecting a **power off command** on the mergCBUS.\\
+Write the output state in EEPROM after detecting a **power off command** on the CANBUS.\\
 The outputs will be restored after the [[:can-gca2-en|CAN-GC2]] is powered on.\\
@@ Line 169: / Line 164: @@
 The [[:can-gca2-en|CAN-GC2]] will report the status of every input after receiving an accessory command with this address. (Short event)\\
 The SoD address should be the same as set for the __**[[:cbus-en#sod|Controller]]**__ and can be tested with the **SoD** button.\\
+===All===
+If 'All' is not set, only high inputs will be reported at SoD.\\
 ====Node Nr.====
@@ Line 179: / Line 176: @@
 | **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 [[:switch-int-en#switch_time|software timed off]] is not possible with mergCBUS; It is realized in the hardware. | \\
+| **PU** | Pulse | Output with x ms activation time. (±50ms) | Note: A [[:switch-int-en#switch_time|software timed off]] is not possible with CANBUS; It is realized in the hardware. | \\
 ====Pulse time====