Download Measurement Set-Up.
Transcript
this particular problem only occurs for USB to serial converters based on the “Prolific” chipset, and only under Windows Vista or Windows 7. If you consider building your own uTracer I strongly recommend that you download the GUI and test it first. It is very easy to test the GUI and its communication without having the actual uTracer hardware by using an emulated COM port. Although it is possible to test the GUI with the COM port just open, a more thorough check is possible if the COM port is fooled by connecting the transmit pin to the receive pin. The small dummy uTracer circuit on the right shows how such a circuit can be wired on a 9-pin female RS232 (DB9) connector. Pins 2 and 3 are the data pins, and the other wiring makes sure that the handshake signals are properly bypassed. After installing the GUI as described above, two configurations should be tried in order to have a 100% failsafe test of the GUI communication: With the COM port open, start the uTracer and click the “Debug” command button. Select the proper COM port number and press the “Ping” command button. Pressing the Ping button will cause the GUI to send two command strings to the uTracer. The first string is a “start measurement sequence” command, and the second string is a “read out all analog channels” command. The GUI will transmit the first character (the first “0” in “00”) and then wait for uTracer to echo it. When the COM port is open nothing is echoed, so after 2 seconds the GUI will detect a timeout and give a timeout error. Connect the “dummy uTracer” circuit to the COM port, and press the “ping” command on the Debug form. In this case the GUI will successfully transmit the two command sequences, and then after 10 seconds give a timeout error because it expects a result string to be sent back by the uTracer. If the GUI responds as above in both cases, the GUI and its communication with the COM port are functioning properly. 7.4 – Stacking of COM ports It sometimes happens that some devices claim a COM port and then not “release” it when the device is removed. Especially (cheap) Bluetooth serial communications modules have this nasty habit. The result is that the lower COM ports numbers become occupied by devices which are not there. Since the COM port number selected on the GUI has to be in the range of 1-10, it can happen that you run out of COM ports. Here is a way to release unused COM port numbers: 1. First thing is to see if hidden devices are taking up the COM ports: Click Start > All Programs > Accessories and then click Command Prompt. 2. Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and then press Enter. (you might have to restart your computer after this) 3. Type “cd \Windows\system32” in the Command Prompt and then press Enter 4. Type “start devmgmt.msc” in the Command Prompt and then press Enter 5. Click View > Show hidden devices. This will display devices that are not connected to your computer 6. Now if you expand the section on COM ports, all the COM ports that have ever been created will be displayed, the non present ones being in grey. You can uninstall away anything that you don’t want (right click, select uninstall).