Changes between Version 25 and Version 26 of Hardware/jCM/dCM3/dUsage
- Timestamp:
- Jan 11, 2013, 1:46:41 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Hardware/jCM/dCM3/dUsage
v25 v26 1 1 [[TOC(Hardware/cCM/cCM3/*, depth=3)]] 2 2 3 === Installing the CM3===4 ==== Connections to the CM3====3 ==== Installing the CM3 ==== 4 ===== Connections to the CM3 ===== 5 5 The CM3 card has a few external connections. The power connector (on board revision 4) uses a Tyco Electronics 2 pin surface mount header, the mating side to this header is [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=A98602-ND here]. Using vampire clips connect the positive power cable to the standby voltage from the node power supply (PS), which is typically the purple cable, or pin 9 on the 20(+4) pin power power connector. The ground wire can be connected to any of the PS ground cables. 6 6 … … 9 9 The serial header is used to connect to the serial port on the mother board, the J4 header is another way of accessing the serial lines and uses a standard 2x5 100mil pin spacing. In the present configuration the serial cable should be a straight cable, and not a crossover (or null modem). If you wish to use a null model cable the resistors R17 and R18 must be populated, and R15 and R16 removed. The last connection that needs to be made is the power monitoring cable, which is the floppy power cable from the PS. This feeds the voltage that the CM will monitor to determine the state of the node. 10 10 11 ==== Turning the CM3 on====11 ===== Turning the CM3 on ===== 12 12 13 13 The Lantronix Xport AR does not refresh its IP address when an ethernet cable is plugged in to is it important the that MAC address of the device already be in DHCP with the appropriate address, and that the ethernet cable be already plugged in when the device is powered on. If it is not in DHCP and plugged in to the network it will default to some unknown IP address, and will not change until reset or power cycled. … … 15 15 When the CM3 turns on the software will start sending UDP packets to the CMC and waiting for responses as well as monitoring the hardware status of the node. This will only happen after the Xport AR has gone through it's own boot sequence, which includes getting its IP address from the DHCP sever and booting into the custom code loaded with the CM3 image. 16 16 17 === Using the CM3===17 ==== Using the CM3 ==== 18 18 The CM3 board, once properly plugged in and powered up will find an IP address and then load the custom software written automatically. Once the node has and IP and is powered up it should start communicating with the CMC right away. For details on the way the software works please refer to the [http://www.orbit-lab.org/wiki/Hardware/CM/cCM3/02-SoftwareDescription Software Description] or look at the code repository in the SVN. The UDP commands are described in more detail in the software description. 19 19 20 ==== UDP====20 ===== UDP ===== 21 21 UDP commands are no longer being used as over firmware version 4.0 22 22 23 ==== HTTP commands====23 ===== HTTP commands ===== 24 24 25 25 These are the commands that can be accessed through HTTP. They all return XML pages with the success or failure of the command … … 39 39 40 40 Format for the XML return pages is as follows. 41 ===== Success=====41 ====== Success ====== 42 42 <<command>> OK </<command>> 43 43 e.g. … … 46 46 }}} 47 47 48 ===== Failure=====48 ====== Failure ====== 49 49 <error><command></error> 50 50 e.g. … … 53 53 }}} 54 54 55 ===== Status=====55 ====== Status ====== 56 56 <power>on/off</power> 57 ==== Command line interface (CLI) access====57 ===== Command line interface (CLI) access ===== 58 58 59 59 Base on telnet to port 8023 (also used for Lantronix access). You can find more about implemented commands with "?" e.g.: … … 73 73 }}} 74 74 75 ===== Command line commands=====75 ====== Command line commands ====== 76 76 77 77 || '''''Node related commands''''' || … … 110 110 }}} 111 111 112 ==== Serial to Telnet tunnel====112 ===== Serial to Telnet tunnel ===== 113 113 114 114 Telnet to IP address of CM and you will get access to serial console of the node. The default serial settings for the serial-to-telnet tunnel are: … … 119 119 || Flow Control || None || 120 120 121 ==== Custom Phone control firmware====121 ===== Custom Phone control firmware ===== 122 122 123 123 There is a slightly altered version of the standard firmware designed for controlling a phone though the 3 most common buttons: power, up, and down. All the existing commands from the standard firmware still exist, so depending on the physical connections enacting the 'reset node' command may activate the 'down button' command because they access the same control pins. For this reason, for this firmware it is encuraged to only use the button 1/2/3 commands and nothing else. 124 124 125 ===== HTTP commands=====125 ====== HTTP commands ====== 126 126 || Http address || function description || 127 127 || /1l || 5 second 'button press on button 1 || … … 132 132 || /3s || same as above for button 3 || 133 133 134 ===== UDP=====134 ====== UDP ====== 135 135 136 136 no UDP support for this 137 137 138 ===== CLI=====138 ====== CLI ====== 139 139 140 140 {{{ … … 154 154 }}} 155 155 156 ===== Connections=====156 ====== Connections ====== 157 157 Right now the connections are as such 158 158
