Editing RS232/USB Probe
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 19: | Line 19: | ||
A complete log of activity is provided both to the screen and to a log file. | A complete log of activity is provided both to the screen and to a log file. | ||
− | Q: ''(Does this require a [[USB Bit Whacker]] between the PC and the device under test (DUT), or does it also work fine with direct RS-232 connection between the PC and the device under test?)'' A: No BitWacker is required for this application, it works with any serial device ( which can be the device under test ), but works best with devices that wait for a command, then they issue a response. If you have a device to test that does | + | Q: ''(Does this require a [[USB Bit Whacker]] between the PC and the device under test (DUT), or does it also work fine with direct RS-232 connection between the PC and the device under test?)'' A: No BitWacker is required for this application, it works with any serial device ( which can be the device under test ), but works best with devices that wait for a command, then they issue a response. If you have a device to test that does have a serial port then using a BitWacker or other microcontroller as an intermediary can be a useful approach. |
=== Early Mock Up of Screen === | === Early Mock Up of Screen === |