 |
||
 |
 |
|
 |
||||
 |
||||
|
|
|
|
|
|
DataScope Example |
||||
 |
||||
|
To get acquainted with the the capabilities of the ChiliPORTS DataScope, connect the special loopback cable that came with your ChiliPORTS card between COM3 and COM4. Start DataScope, and Connect to COM3. When DataScope first starts up, all of the control signals will be red ("not asserted", because no software is using the port. Now go to Program Manager, double click on the Accessories program group, and double click on the Terminal icon. You will need to do this twice, to start up terminal sessions on both COM3 and COM4. Configure the first terminal session to COM3, and observe in DataScope that DTR &RTS become green ("asserted", telling the other port that COM3 is ready. Configure the second terminal session to COM4, and observe that the remainder of the control lines have also changed to green ("asserted". Select the COM3 terminal and type in its window. The characters you type should appear on the screen of COM4, and will also appear in DataScope's data window as transmitted data (green). Now select the COM4 terminal and type in its window. Data should appear on the COM3 terminal, and in DataScope's data window as received data (red). You have now observed the simplest form of communications between two ports, and have verified that your wiring is correct. To see how DataScope can be used to diagnose a problem, replace the special loopback cable with the longer modem cable that came with your ChiliPORTS card. Perform exactly the same test you just completed successfully, selecting the COM3 terminal and typing in its window. DataScope shows transmitted data going out, but you are not receiving it at the second terminal. This would point to either a wiring problem or software problem on COM4. Disconnect DataScope from COM3 and Connect it to COM4, then type again on the COM3 terminal. DataScope will show no data received at COM4, although you know it is being sent from COM3. This points to a wiring problem. |
||||