| ||||||||
| Added: | ||||||||
| > > |
DEPRECIATED! See Darwin PowerComs Board. | |||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 149 to 149 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Using your comms software and the same settings as you previously used (no flow control), type or send some characters. The exact same characters should echo back to you. If you remove the power from the module, the echo should stop. Turn it on again and check that echo returns. Similarly, if you remove the comms cable echo should stop, put it back it and check that echo returns. | ||||||||
| Changed: | ||||||||
| < < |
For Linux you can also use the 'poke' utility form the firmware toolkit to test the interface. I used device /dev/ttyUSB0 - a serial USB adaptor - as my serial port on a Linux box, Windows users probably have COM1 or something similar. Here is the command line; change your device to match: | |||||||
| > > |
For Linux you can also use the 'poke' utility form the firmware toolkit to test the interface. I used device /dev/ttyUSB0 - a serial USB adaptor - as my serial port on a Linux box, Windows users probably have COM1 or something similar. Here is the command line; change your serial device to match and make sure you have access rights to that device (in Ubuntu you must be a member of the system dialout group): | |||||||
echo 0|./poke -d 2 -t /dev/ttyUSB0 -v -w
| ||||||||
| Line: 161 to 161 | ||||||||
|
<54><51><31><02><00><00> | ||||||||
| Added: | ||||||||
| > > |
If this does not happen, type:
stty -F $serialport -echo -cooked
and try again.
| |||||||
For Windows the poke utility is not currently available. You can use the Java stepper exerciser application instead. If you launch it and drag one of the position sliders, you should see the following error: Update exception: java.io.IOException: Received data packet when expecting ACK
Now you are ready to connect your stepper controller.
| ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 172 to 172 | ||||||||
|---|---|---|---|---|---|---|---|---|
| -- SimonMcAuliffe - 02 Feb 2006 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 137 to 137 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Changed: | ||||||||
| < < |
Now get a module connector cable (which is either 3 or 4 wires depending on how you're constructing your modules) and connect J2 to J3. This makes the comms card behave as if it is addressing other controller cards. Doing so shorts your 12V pin directly to ground, a move that is unlikely to do your power supply a lot of good. | |||||||
| > > |
Now get a module connector cable (which is either 3 or 4 wires depending on how you're constructing your modules) and connect J2 to J3. This makes the comms card behave as if it is addressing other controller cards. Be sure that you don't get your cable twisted when you connect J2 to J3. Doing so shorts your 12V pin directly to ground, a move that is unlikely to do your power supply a lot of good. | |||||||
| Alternatively, you can simply attach a jumper wire from pin 1 on the outgoing comms connector (J2) to pin 1 on the incoming communications connector (J3). Take great care not to get your connector cable twisted. | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 137 to 137 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Changed: | ||||||||
| < < |
Now get a module connector cable (which is either 3 or 4 wires depending on how you're constructing your modules). Alternatively jumper pin 1 from one of the communications connectors to pin 1 on the other communications connector. | |||||||
| > > |
Now get a module connector cable (which is either 3 or 4 wires depending on how you're constructing your modules) and connect J2 to J3. This makes the comms card behave as if it is addressing other controller cards. Doing so shorts your 12V pin directly to ground, a move that is unlikely to do your power supply a lot of good. Alternatively, you can simply attach a jumper wire from pin 1 on the outgoing comms connector (J2) to pin 1 on the incoming communications connector (J3). Take great care not to get your connector cable twisted. | |||||||
You should now observe the following:
| ||||||||
| Changed: | ||||||||
| < < |
At this stage you should be able to do an internal echo test. Using your comms software and the same settings as you previously used (no flow control), type or send some characters. The exact same characters should echo back to you. If you remove the power from the module, the echo should stop. Turn it on again and check that echo returns. Similarly, if you remove the comms cable echo should stop, put it back it and check that echo returns. | |||||||
| > > |
At this stage you should be able to do an internal echo test. Using your comms software and the same settings as you previously used (no flow control), type or send some characters. The exact same characters should echo back to you. If you remove the power from the module, the echo should stop. Turn it on again and check that echo returns. Similarly, if you remove the comms cable echo should stop, put it back it and check that echo returns. | |||||||
| For Linux you can also use the 'poke' utility form the firmware toolkit to test the interface. I used device /dev/ttyUSB0 - a serial USB adaptor - as my serial port on a Linux box, Windows users probably have COM1 or something similar. Here is the command line; change your device to match: | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 61 to 61 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Solder the components into the board as pictured below. See the Electronics Fabrication Guide if you're new to soldering or component placement. | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Pay particular attention to: | ||||||||
| Line: 170 to 170 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 71 to 71 | ||||||||
|---|---|---|---|---|---|---|---|---|
Board connections | ||||||||
| Changed: | ||||||||
| < < |
The connector pins are numbered from the top of the board down, so for example the pin in hole E8 is pin number 1 of connect J4. | |||||||
| > > |
The connector pins are numbered from the top of the board down, so for example the pin in hole E8 is pin number 1 of connect J4. It is advised that you do not plug and unplug things with the PSU turned on, else the magic smoke sometimes escapes. | |||||||
| ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 32 to 32 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Schematic | ||||||||
| Line: 86 to 87 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Variations | ||||||||
| Line: 112 to 113 | ||||||||
Debugging your serial connection | ||||||||
| Changed: | ||||||||
| < < |
Experienced hardware folk never trust their hardware. First make sure your serial port operates, which is easily done by shorting the Rx and Tx lines out on the serial lead from your PC. These are pins 2 & 3 and a small screwdriver will do the job. Do not touch the other pins or the casing. With the other arms, type characters at a dumb serial terminal such as Hypercomm (Windows) or minicom (Linux) which has had all flow control turned off. If the port works, your typing should echo back - and stop echoing when you remove the screwdriver. If it doesn't work, you have the wrong port, a dead lead, a dead port, or if really unlucky a combination of the above. | |||||||
| > > |
Before applying power always first check your stripboard wiring as described in the Electronics Fabrication Guide.
Experienced hardware folk never trust their hardware. First make sure your serial port operates, which is easily done by shorting the Rx and Tx lines out on the serial lead from your PC. These are pins 2 & 3 and a small screwdriver will do the job. Do not touch the other pins or the casing. With the other arms, type characters at a dumb serial terminal such as Hyperterminal (Windows), minicom (Linux) or kermit (Linux) which has had all flow control turned off. If the port works, your typing should echo back - and stop echoing when you remove the screwdriver. If it doesn't work, you have the wrong port, a dead lead, a dead port, or if really unlucky a combination of the above.
When testing with comms software ensure flow control is set to "none". If in doubt for the other settings, use the following (though it's not too important at this stage): 19200 baud, 8 bits, no parity, one stop bit (8-N-1). If available, set carrier-detect to off.
Use the same principle to test the connector to the board, shorting it out with a screwdriver while no power is applied is acceptable. The pins to short are pins 2 and 3 of the serial connector on the module board (while the cable is still attached to the PC). If that doesn't work, your cable is suspect.
If all this checks out and you have verified the stripboard soldering, then you can apply power to the board. If you have a multimeter, check the following voltage levels are present. If any of these are wrong it suggests a defect in your wiring. In each case, measure from the first pin with the negative input of your voltmeter to the second pin with the positive input of your voltmeter. For these measurements, plug the power in, but do not plug the device into the PC. Also leave the communications connectors empty.
| |||||||
| Changed: | ||||||||
| < < |
Use the same principle to test the connector to the board, shorting it out with a screwdriver while no power is applied is acceptable. If that doesn;t work, your cable is suspect. Then test out the serial interface chip by jumpering the No. 1 connectors on the two communications jumpers and checking for echo. This tests the actual circuitry. | |||||||
| > > |
| |||||||
| Changed: | ||||||||
| < < |
If that checks out, use the 'poke' utility form the firmware toolkit to test the interface. I used device /dev/ttyUSB0 - a serial USB adaptor - as my serial port on a Linux box, Windows users probably have COM1 or something similar. Here is the command line; change your device to match: | |||||||
| > > |
Now get a module connector cable (which is either 3 or 4 wires depending on how you're constructing your modules). Alternatively jumper pin 1 from one of the communications connectors to pin 1 on the other communications connector.
You should now observe the following:
| |||||||
echo 0|./poke -d 2 -t /dev/ttyUSB0 -v -w
| ||||||||
| Line: 127 to 156 | ||||||||
|
<54><51><31><02><00><00> | ||||||||
| Added: | ||||||||
| > > |
For Windows the poke utility is not currently available. You can use the Java stepper exerciser application instead. If you launch it and drag one of the position sliders, you should see the following error: Update exception: java.io.IOException: Received data packet when expecting ACK
| |||||||
Now you are ready to connect your stepper controller.
See Also | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||||
| Changed: | ||||||||||
| < < |
(note: item pictured is an older version)
| |||||||||
| > > |
| |||||||||
Introduction | ||||||||||
| Line: 141 to 140 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| Added: | ||||||||||
| > > |
| |||||||||
HOWTO: Building A Stripboard Comms Controller
| |||||||||||||
| Added: | |||||||||||||
| > > |
(note: item pictured is an older version) | ||||||||||||
Introduction | |||||||||||||
| Line: 25 to 26 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
| Changed: | |||||||||||||
| < < |
| ||||||||||||
| > > |
| ||||||||||||
| |||||||||||||
| Line: 37 to 38 | |||||||||||||
| This is the schematic diagram of the circuit you will be building. See reading a schematic? to understand the various parts. | |||||||||||||
| Changed: | |||||||||||||
| < < |
| ||||||||||||
| > > |
| ||||||||||||
Preparing the boardThe strips on the back of the board need to be "separated" at certain points. The easiest way to do this is to use a small electric drill with a drill bit around 3-4mm in diameter. Don't drill all the way, just far enough to cut the copper tracks - you may find a 3.5mm drill in a hand-held chuck is easier to control. See the Electronics Fabrication Guide for more details. This image shows the rear of the stripboard so you can see the points that were separated. | |||||||||||||
| Changed: | |||||||||||||
| < < |
| ||||||||||||
| > > |
| ||||||||||||
| The points marked in black are where you should separate the tracks. | |||||||||||||
| Line: 60 to 61 | |||||||||||||
| Solder the components into the board as pictured below. See the Electronics Fabrication Guide if you're new to soldering or component placement. | |||||||||||||
| Changed: | |||||||||||||
| < < |
| ||||||||||||
| > > |
| ||||||||||||
| Pay particular attention to: | |||||||||||||
| Changed: | |||||||||||||
| < < |
| ||||||||||||
| > > |
| ||||||||||||
| |||||||||||||
| Deleted: | |||||||||||||
| < < |
The 12V line must carry quite high current, so you should use fairly heavy duty wire for the link between holes B17 and E17. | ||||||||||||
Board connections | |||||||||||||
| Changed: | |||||||||||||
| < < |
The connector pins are numbered from the top of the board down, so for example the pin in hole D8 is pin number 1 of connect J4. | ||||||||||||
| > > |
The connector pins are numbered from the top of the board down, so for example the pin in hole E8 is pin number 1 of connect J4. | ||||||||||||
| |||||||||||||
| Deleted: | |||||||||||||
| < < |
| ||||||||||||
| |||||||||||||
| Added: | |||||||||||||
| > > |
| ||||||||||||
| |||||||||||||
| Deleted: | |||||||||||||
| < < |
| ||||||||||||
| |||||||||||||
| Added: | |||||||||||||
| > > |
| ||||||||||||
| |||||||||||||
| Deleted: | |||||||||||||
| < < |
| ||||||||||||
| |||||||||||||
| Added: | |||||||||||||
| > > |
| ||||||||||||
| |||||||||||||
| Line: 98 to 97 | |||||||||||||
| |||||||||||||
| Changed: | |||||||||||||
| < < |
| ||||||||||||
| > > |
| ||||||||||||
| |||||||||||||
| Line: 138 to 137 | |||||||||||||
| -- SimonMcAuliffe - 02 Feb 2006 | |||||||||||||
| Changed: | |||||||||||||
| < < |
| ||||||||||||
| > > |
| ||||||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 110 to 110 | ||||||||
|---|---|---|---|---|---|---|---|---|
Troubleshooting | ||||||||
| Changed: | ||||||||
| < < |
Nothing here yet | |||||||
| > > |
If you experience trouble, please share the problems (and resolutions) with us here: | |||||||
| Changed: | ||||||||
| < < |
If you experience trouble, please share the problems (and resolutions) with us. | |||||||
| > > |
Debugging your serial connection | |||||||
| Added: | ||||||||
| > > |
Experienced hardware folk never trust their hardware. First make sure your serial port operates, which is easily done by shorting the Rx and Tx lines out on the serial lead from your PC. These are pins 2 & 3 and a small screwdriver will do the job. Do not touch the other pins or the casing. With the other arms, type characters at a dumb serial terminal such as Hypercomm (Windows) or minicom (Linux) which has had all flow control turned off. If the port works, your typing should echo back - and stop echoing when you remove the screwdriver. If it doesn't work, you have the wrong port, a dead lead, a dead port, or if really unlucky a combination of the above.
Use the same principle to test the connector to the board, shorting it out with a screwdriver while no power is applied is acceptable. If that doesn;t work, your cable is suspect. Then test out the serial interface chip by jumpering the No. 1 connectors on the two communications jumpers and checking for echo. This tests the actual circuitry.
If that checks out, use the 'poke' utility form the firmware toolkit to test the interface. I used device /dev/ttyUSB0 - a serial USB adaptor - as my serial port on a Linux box, Windows users probably have COM1 or something similar. Here is the command line; change your device to match:
echo 0|./poke -d 2 -t /dev/ttyUSB0 -v -w
It should come back with:
<54><51><31><02><00><00><d0>[54][51][31][02][00][00][d0]Read fail 2 <54><51><31><02><00><00><d0>[54][51][31][02][00][00][d0]Read fail 2 <54><51><31><02><00><00><d0>[54][51][31][02][00][00][d0]Read fail 2 <54><51><31><02><00><00><d0>[54][51][31][02][00][00][d0]Read fail 2Now you are ready to connect your stepper controller. | |||||||
See Also | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 94 to 94 | ||||||||
|---|---|---|---|---|---|---|---|---|
Variations | ||||||||
| Changed: | ||||||||
| < < |
If you're planning on using a PC power supply to run your RepRap, then you can use the 5V supply that it provides instead of using a 7805. This is a simple change and is left as an exercise to the reader
| |||||||
| > > |
If you're planning on using a PC power supply to run your RepRap, then you can use the 5V supply that it provides instead of using a 7805. The simple way to do this is to make the following changes:
| |||||||
| Even if you do use a PC power supply, you can just connect the 12V line and use the module as depicted. The MAX202 chip can be used as a drop-in replacement for the MAX232, optionally allowing C2-C5 to be replaced with cheaper 0.1uF ceramic capacitors. See http://www.maxim-ic.com for details on chip and sampling options. | ||||||||
| Added: | ||||||||
| > > |
The board has a lot of spare space on it and you can make a much more compact board if you prefer. However space is really useful for mounting and adding modifications later on, should any be needed (which will probably save you from starting from scratch). There is a possibility that you might want to add a heatsink to the 7805 in the future, and these take up a little space too. If in doubt, be generous with the board size. | |||||||
TroubleshootingNothing here yet | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 66 to 66 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| The 12V line must carry quite high current, so you should use fairly heavy duty wire for the link between holes B17 and E17. | ||||||||
| Line: 98 to 98 | ||||||||
| Even if you do use a PC power supply, you can just connect the 12V line and use the module as depicted. | ||||||||
| Added: | ||||||||
| > > |
The MAX202 chip can be used as a drop-in replacement for the MAX232, optionally allowing C2-C5 to be replaced with cheaper 0.1uF ceramic capacitors. See http://www.maxim-ic.com for details on chip and sampling options. | |||||||
TroubleshootingNothing here yet | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 41 to 41 | ||||||||
|---|---|---|---|---|---|---|---|---|
Preparing the board | ||||||||
| Changed: | ||||||||
| < < |
The strips on the back of the board need to be "separated" at certain points. The easiest way to do this is to use a small electric drill with a drill bit around 3-4mm in diameter. Don't drill all the way, just far enough to cut the copper tracks. See the Electronics Fabrication Guide for more details. | |||||||
| > > |
The strips on the back of the board need to be "separated" at certain points. The easiest way to do this is to use a small electric drill with a drill bit around 3-4mm in diameter. Don't drill all the way, just far enough to cut the copper tracks - you may find a 3.5mm drill in a hand-held chuck is easier to control. See the Electronics Fabrication Guide for more details. | |||||||
This image shows the rear of the stripboard so you can see the points that were separated.
| ||||||||
| Line: 53 to 53 | ||||||||
Important: There are some voltages that can and will damage components if you aren't careful. Double and triple check that:
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Making the board | ||||||||
HOWTO: Building A Stripboard Comms Controller | ||||||||
| Line: 103 to 103 | ||||||||
|---|---|---|---|---|---|---|---|---|
| If you experience trouble, please share the problems (and resolutions) with us. | ||||||||
| Added: | ||||||||
| > > |
See Also | |||||||
-- SimonMcAuliffe - 02 Feb 2006
| ||||||||
| Line: 1 to 1 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||||||||||
| > > |
HOWTO: Building A Stripboard Comms Controller
IntroductionThe Comms controller is the main interface between the host PC and the rest of the RepStrap or RepRap. See RepStrap for an overview of all the components.RequirementsTools and consumables
Components
SchematicThis is the schematic diagram of the circuit you will be building. See reading a schematic? to understand the various parts.
Preparing the boardThe strips on the back of the board need to be "separated" at certain points. The easiest way to do this is to use a small electric drill with a drill bit around 3-4mm in diameter. Don't drill all the way, just far enough to cut the copper tracks. See the Electronics Fabrication Guide for more details. This image shows the rear of the stripboard so you can see the points that were separated.
The points marked in black are where you should separate the tracks.
Note: This is the minimum size. It is recommended that you leave sufficient additional space on all sides to allow for easy mounting. Around 20mm will be ample.
Important: There are some voltages that can and will damage components if you aren't careful. Double and triple check that:
Making the boardSolder the components into the board as pictured below. See the Electronics Fabrication Guide if you're new to soldering or component placement.
Pay particular attention to:
Board connectionsThe connector pins are numbered from the top of the board down, so for example the pin in hole D8 is pin number 1 of connect J4.
VariationsIf you're planning on using a PC power supply to run your RepRap, then you can use the 5V supply that it provides instead of using a 7805. This is a simple change and is left as an exercise to the reader
Even if you do use a PC power supply, you can just connect the 12V line and use the module as depicted.
TroubleshootingNothing here yet If you experience trouble, please share the problems (and resolutions) with us. -- SimonMcAuliffe - 02 Feb 2006
| |||||||||||||||