can-gca1e-en
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
can-gca1e-en [2020/06/30 21:22] – [Firmware Copyright] rjversluis | can-gca1e-en [2022/01/29 16:53] (current) – [CAN-GC1e V2 CANBUS-Ethernet Interface] phg | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== CAN-GC1e CANBUS-Ethernet Interface with 3 Amp Power supply====== | + | ====== CAN-GC1e CANBUS-Ethernet Interface with 3Amp power supply====== |
[[english|{{ | [[english|{{ | ||
[[: | [[: | ||
* [[: | * [[: | ||
- | * [[:cbus-en|CBUS Rocrail Setup]] | + | * [[:cbus-en|CANBUS |
* [[: | * [[: | ||
* [[: | * [[: | ||
Line 12: | Line 12: | ||
\\ | \\ | ||
- | =====Firmware Copyright===== | ||
- | Copyright(c) Mike Bolton & Gil Fuchs.\\ | ||
- | |||
- | \\ | ||
===== The CANBUS Ethernet interface ===== | ===== The CANBUS Ethernet interface ===== | ||
Line 22: | Line 18: | ||
* The circuit is mounted on a professional, | * The circuit is mounted on a professional, | ||
* DB9 connectors are used because of their toughness. | * DB9 connectors are used because of their toughness. | ||
- | * The DB9 connectors are supplying 12V power for the CBUS network. | + | * The DB9 connectors are supplying 12V power for the CANBUS |
* This computer interface has, like all other CAN-GCA modules, | * This computer interface has, like all other CAN-GCA modules, | ||
* The board features an ICSP connector for (re-)programming the CPU. | * The board features an ICSP connector for (re-)programming the CPU. | ||
Line 37: | Line 33: | ||
* Connection timeout after 100 seconds idle. | * Connection timeout after 100 seconds idle. | ||
* **[[# | * **[[# | ||
- | * Compatible 12VDC mergCBUS | + | * Compatible 12VDC connector. (J5) |
* PC **[[: | * PC **[[: | ||
- | * Ethernet galvanic isolated from MergCBUS | + | * Ethernet galvanic isolated from CAN |
\\ | \\ | ||
Line 53: | Line 49: | ||
| 4 | Running | continuous | | | | 4 | Running | continuous | | | ||
| 4 | Learning mode | 500ms blinking | Activated by push button or Rocrail setup. | | | 4 | Learning mode | 500ms blinking | Activated by push button or Rocrail setup. | | ||
- | | 4 | Error | One shot long DIM | Ethernet or CBUS Queue full. Socket not ready. | | + | | 4 | Error | One shot long DIM | Ethernet or CAN Queue full. Socket not ready. | |
| 4 | Disconnect | One shot DIM | A client, e.g. Rocrail server, has disconnected. | | 4 | Disconnect | One shot DIM | A client, e.g. Rocrail server, has disconnected. | ||
| 4 | Read/Write variable | One shot short DIM | During setup with FLiM. | | | 4 | Read/Write variable | One shot short DIM | During setup with FLiM. | | ||
- | | 5 | CBUS activity | random flashing | | | + | | 5 | CAN activity | random flashing | | |
\\ | \\ | ||
Line 67: | Line 63: | ||
| J2, J3 | CAN-GC connector | | J2, J3 | CAN-GC connector | ||
| J4 | Ethernet connection. | | J4 | Ethernet connection. | ||
- | | J5 | | + | | J5 | |
| JP1 | CAN termination. | | JP1 | CAN termination. | ||
\\ | \\ | ||
Line 82: | Line 78: | ||
\\ | \\ | ||
- | ===== Adjusting supply for CBUS ===== | + | ===== Adjusting supply for CAN ===== |
Supply for all CAN-GCx units should be standard 12V.\\ | Supply for all CAN-GCx units should be standard 12V.\\ | ||
This can be adjusted with POT1, to be measured on J5 pt 1 & 4.\\ | This can be adjusted with POT1, to be measured on J5 pt 1 & 4.\\ | ||
Line 98: | Line 94: | ||
| **The CAN-GC1e can only be configured over Ethernet.** |\\ | | **The CAN-GC1e can only be configured over Ethernet.** |\\ | ||
The usual way is to connect CAN-GC1e to your home network.\\ | The usual way is to connect CAN-GC1e to your home network.\\ | ||
- | A direct link will mostly work too but in some occasions a router or Ethernet hub seems to be needed.\\ | + | A direct link will mostly work too but computer network TCP/IP address should |
+ | REMARK: Best is to set it to 192.168.0.101, | ||
{{: | {{: | ||
- | The default IP address of the CAN-GC1e is 192.168.0.200. Make sure the PC is also in the same network range of 192.168.0.x before trying to connect.\\ | + | The default IP address of the CAN-GC1e is 192.168.0.200. Make sure the PC is also in the same network range of 192.168.0.x before trying to connect.( See above )\\ |
- | Your PC gets usually its IP4 address autmatically from your home router.\\ | + | Your PC usually |
- | This might be different | + | This might be different |
In that case, write down the IP4 number where your PC is running on.\\ | In that case, write down the IP4 number where your PC is running on.\\ | ||
- | Change the automatic IP4 address in the PC network settings to manual and set IP4 address to 192.168.0.1 and subaddress to 255.255.255.0\\ | + | If it is not listed, see in Help menu of Rocrail, there it will show.\\ |
- | Now Rocrail should have connection with CAN-GC1e.\\ | + | Change the automatic IP4 address in the PC network settings to manual and set IP4 address to 192.168.0.101 and subaddress to 255.255.255.0\\ |
+ | Now Rocrail should have connection with CAN-GC1e. Please note that sometimes it helps here to restart Rocrail and CAN-GC1e.\\ | ||
To change the IPadress in the CAN-GC1e, follow this procedure : \\ | To change the IPadress in the CAN-GC1e, follow this procedure : \\ | ||
After connection is established, | After connection is established, | ||
Line 122: | Line 120: | ||
If for any reason you like to go back to standard IP-Number 192.168.0.200, | If for any reason you like to go back to standard IP-Number 192.168.0.200, | ||
+ | \\ | ||
+ | For those who like to set this IP number directly into memory of the chip, you will need programmer which can handle PIC18F2585.\\ | ||
+ | The IP numbers are stored hexadecimal in &H305 to & | ||
+ | |||
+ | |||
Line 147: | Line 150: | ||
This is to avoid zombie connections which will unnecessary occupy a TCP/IP resource.\\ | This is to avoid zombie connections which will unnecessary occupy a TCP/IP resource.\\ | ||
Disable this option if sniffer software is connected.\\ | Disable this option if sniffer software is connected.\\ | ||
- | | Rocrail sends every 2 seconds, in case no other command has been send, a keep alive message to the CAN-GC1e. \\ This message is not broadcasted to the CBUS and serves only for resetting the idle timer in the CAN-GC1e for this connection. |\\ | + | | Rocrail sends every 2 seconds, in case no other command has been send, a keep alive message to the CAN-GC1e. \\ This message is not broadcasted to CAN and serves only for resetting the idle timer in the CAN-GC1e for this connection. |\\ |
Line 160: | Line 163: | ||
\\ | \\ | ||
- | ====CBUS==== | + | ====CANBUS==== |
===CANID=== | ===CANID=== | ||
- | Unique ID in the CBUS network.\\ | + | Unique ID in the CANBUS |
The CANID is not used from the ASCII Frames because more then one PCs can connect using different IDs.\\ | The CANID is not used from the ASCII Frames because more then one PCs can connect using different IDs.\\ | ||
Line 169: | Line 172: | ||
=====Multiple Connections===== | =====Multiple Connections===== | ||
The CAN-GC1e Firmware supports up to 4 concurrently connections.\\ | The CAN-GC1e Firmware supports up to 4 concurrently connections.\\ | ||
- | Keep in mind that commands send from one connection to CBUS are not broadcasted to the other connections.\\ | + | Keep in mind that commands send from one connection to CANBUS |
- | This is the normal behaviour because all commands send by a CBUS node are not seen by this node itself. \\ | + | This is the normal behaviour because all commands send by a CANBUS |
Only packets coming from other nodes in the network are broadcasted to all connections.\\ | Only packets coming from other nodes in the network are broadcasted to all connections.\\ | ||
Line 185: | Line 188: | ||
=====Hardware Files===== | =====Hardware Files===== | ||
- | * http://bazaar.launchpad.net/~rocrail-project/rocrail/hardware/files/head:/ | + | * https://gitlab.com/rocrail/GCA/-/tree/master/ |
====Harware info==== | ====Harware info==== | ||
| {{: | | {{: | ||
Line 197: | Line 200: | ||
===== Power for CAN-GC3 programming track===== | ===== Power for CAN-GC3 programming track===== | ||
The standard 12V, coming from CAN-GC1e , is used for programming track as well.\\ | The standard 12V, coming from CAN-GC1e , is used for programming track as well.\\ | ||
- | Allthough | + | It should be adjusted before |
+ | Though many programmers often also work with no more that 12V, \\ | ||
it seems that some decoders have a bit of a problem with that.\\ | it seems that some decoders have a bit of a problem with that.\\ | ||
To solve that, a higher Voltage will be the solution.\\ | To solve that, a higher Voltage will be the solution.\\ | ||
- | For this reason, the VR1 regulator on CAN-GC1e can be swapped with a LM2576T-adj type.\\ | + | The Pot1 regulator on CAN-GC1e can be set to max 18V, but I advise not to that if not need.e.\\ |
- | Pot1 on CAN-GC1e is already there and in that case can be used for adjusting | + | With 18V all connected |
- | CAN-GC1e | + | Without these programming needs, the voltage |
+ | Voltage can be measured at the pins +12V and GND on J5.\\ | ||
+ | |||
+ | \\ | ||
+ | =====Trouble Shooting===== | ||
+ | ====Not all CAN messages are processed==== | ||
+ | Replace C18, and if needed also C3, if not all CAN messages are processed.\\ | ||
+ | The CPU will stop responding if C18 is very bad.\\ | ||
can-gca1e-en.1593544943.txt.gz · Last modified: 2020/06/30 21:22 by rjversluis