Logicport Overview

As promised earlier, the Near Future Laboratory has published an overview of the Logicport Logic Analyzer. They’re using the Playstation 2 analysis as an example. The Logicport uses “interpreters” to define protocols. It has I2C/TWI, SPI, RS232, and CAN 2.0A/2.0B, but you can build your own interpreter based on these. You can specify bit order and the format you want the data in. Slave interpreters can be used for specific tasks: with the PS2 they were used to just show the fifth byte, which is the actual button press.

“Triggers” are used to signal specific activity. On the PS2, one was attached to the falling signal on the slave select line. This event means the master is about to start sending data.

The final area worth exploring is “measurements”. These can be frequency or arbitrary time intervals between events. The Logicport has multiple ground connections to eliminate noise from the signal and you’ll have to play with sample rate and logic level to get things running smooth. It’s nice to see how-tos written from the perspective of someone just getting started with the tool.

4 thoughts on “Logicport Overview

  1. Using this would have been a lot easier than turning PICs into SPI-to-serial converters, which is what we did to research our ps2 interface guide: http://www.curiousinventor.com/guides/ps2

    For people looking to emulate a PS2 controller, we recorded the first 600 or so bytes of handshaking between a PS2 and various controllers (dual shock, guitar hero, Chinese knock off–worked about the same as the official DS). The recordings are available in a spreadsheet at the bottom of the guide, as well as a circuit diagram and source code. It’s surprising how much handshaking goes on considering that only a few commands are necessary to setup a controller to use all the analog values (including button pressures) and vibration motors.

  2. OK, seriously — can we stop with the all-lower-case stuff? I had to parse the phrase “It has I2C/TWI, SPI, RS232, and CAN 2.0A/2.0B” about 10 times before I realized that “can” was an acronym.

    At the very least, can somebody point me in the direction of a guide on user styles to let me turn off the lower-casing renderer?

  3. @james:

    I don’t know much about creating user stylesheets, but the actual CSS contents you want are “* {text-transform:none}”.

    I’m working on a greasemonkey script to do it for you. It works in the Firebug console but for some reason Greasemonkey isn’t running it.

    If the Hackaday leadership is reading… seriously, this is ridiculous. Why would you want to make your blog hard to read, particularly in such an acronym-heavy area as this?

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.