PulseView

As in previous years various sigrok developers will be at the Chaos Communication Congress (31C3) in Hamburg, Germany. The conference takes place December 27th to 30th, 2014. There will be a sigrok assembly (on all 4 days) with a few tables and ... [More] chairs to allow for sigrok hacking and development planning, various demos and Q&A for visitors, and so on. Apart from sigrok hacking the conference also features the usual set of awesome talks related to security, hardware hacking, and lots of other interesting topics that you shouldn't miss. If you're interested in sigrok as user or developer, please drop by and say hello. Bring your gear (if possible) for reverse engineering and driver writing purposes. Chat with us, give us your suggestions which features you'd like to see, which devices you want to be supported, which protocol decoders you'd like to have, or even help us write some drivers/decoders!   [Less]

As in previous years various sigrok developers will be at the Chaos Communication Congress (31C3) in Hamburg, Germany. The conference takes place December 27th to 30th, 2014. There will be a sigrok assembly (on all 4 days) with a few tables and ... [More] chairs to allow for sigrok hacking and development planning, various demos and Q&A for visitors, and so on. Apart from sigrok hacking the conference also features the usual set of awesome talks related to security, hardware hacking, and lots of other interesting topics that you shouldn't miss. If you're interested in sigrok as user or developer, please drop by and say hello. Bring your gear (if possible) for reverse engineering and driver writing purposes. Chat with us, give us your suggestions which features you'd like to see, which devices you want to be supported, which protocol decoders you'd like to have, or even help us write some drivers/decoders!   [Less]

So here I am hanging out at the local hacker space in Richmond. We, the group that meet up every Tuesday evening are small, yet perfectly formed. This evening Paul (MØTZO), a friendly radio ham, and co-founder of our group brought along an ... [More] interesting device to encode GPS location data in APRS (Automatic Packet Reporting System) packets. These packets are fed into to a VHF radio transmitter which transmits the signal at 144.8 MHz. A network of receivers, run by amateur radio operators receives the packets, and streams them over the internet. An interesting device indeed. Tonight we were just playing with Paul's GPS board, which contains a U-Blox Neo 6 GPS receiver. As with most GPS receivers, simply powering it on is enough to make it emit coordinates encoded in NMEA 0183 sentences transmitted over UART at 9600bps. These are trivial to receive with an fx2-based logic analyzer and sigrok-cli: $ sigrok-cli --driver=fx2lafw --config samplerate=50k \ --continuous -P uart:baudrate=9600:tx=0 -B uart=tx With the UART protocol decoder and the ASCII binary output, we can see the NMEA sentences: Here we can see that we're locked on and receiving coordinates. "cat -v" is used to protect the terminal state from being clobbered by any errant binary data being emitted. Yawn. Let's make this more interesting. There is a very interesting package called gpsd. This is a GPS location server than can connect to various types of GPS devices, and can serve the position information over the network. And best of all, thanks to the power of UNIX pipes, we can feed the data from sigrok directly into it: $ gpsd -N <(sigrok-cli --driver=fx2lafw --config samplerate=50k \ --continuous -P uart:baudrate=9600:tx=0 -B uart=tx) There are a variety of gpsd clients available. There's a nice ncurses based client, gpsmon: And best of all, KDE's Marble integrates with gpsd. Here we see Marble, showing a live stream of location data captured by the fx2lafw firmware, decoded by sigrok, handled by gpsd, plotted by Marble on OpenStreetMap map data - a complete free-software stack! Pretty freetarded: [Less]

So here I am hanging out at the local hacker space in Richmond. We, the group that meet up every Tuesday evening are small, yet perfectly formed. This evening Paul (MØTZO), a friendly radio ham, and co-founder of our group brought along an ... [More] interesting device to encode GPS location data in APRS (Automatic Packet Reporting System) packets. These packets are fed into to a VHF radio transmitter which transmits the signal at 144.8 MHz. A network of receivers, run by amateur radio operators receives the packets, and streams them over the internet. An interesting device indeed. Tonight we were just playing with Paul's GPS board, which contains a U-Blox Neo 6 GPS receiver. As with most GPS receivers, simply powering it on is enough to make it emit coordinates encoded in NMEA 0183 sentences transmitted over UART at 9600bps. These are trivial to receive with an fx2-based logic analyzer and sigrok-cli: $ sigrok-cli --driver=fx2lafw --config samplerate=50k \ --continuous -P uart:baudrate=9600:tx=0 -B uart=tx With the UART protocol decoder and the ASCII binary output, we can see the NMEA sentences: Here we can see that we're locked on and receiving coordinates. "cat -v" is used to protect the terminal state from being clobbered by any errant binary data being emitted. Yawn. Let's make this more interesting. There is a very interesting package called gpsd. This is a GPS location server than can connect to various types of GPS devices, and can serve the position information over the network. And best of all, thanks to the power of UNIX pipes, we can feed the data from sigrok directly into it: $ gpsd -N <(sigrok-cli --driver=fx2lafw --config samplerate=50k \ --continuous -P uart:baudrate=9600:tx=0 -B uart=tx) There are a variety of gpsd clients available. There's a nice ncurses based client, gpsmon: And best of all, KDE's Marble integrates with gpsd. Here we see Marble, showing a live stream of location data captured by the fx2lafw firmware, decoded by sigrok, handled by gpsd, plotted by Marble on OpenStreetMap map data - a complete free-software stack! Pretty freetarded: [Less]

libsigrokdecode now supports yet another protocol decoder, rfm12. This one decodes the SPI-based protocol of the HopeRF RFM12 and RFM12B wireless FSK transceiver modules. These devices can transmit and receive in the 433MHz, 868MHz and 915MHz bands ... [More] (depending on chip). Thanks a lot to Sławek Piotrowski for contributing the decoder (as well as an example file for sigrok-dumps)! We've also added a small test-case in the sigrok-test repository to be able to keep track of any potential regressions that might occur later. [Less]

libsigrokdecode now supports yet another protocol decoder, rfm12. This one decodes the SPI-based protocol of the HopeRF RFM12 and RFM12B wireless FSK transceiver modules. These devices can transmit and receive in the 433MHz, 868MHz and 915MHz bands ... [More] (depending on chip). Thanks a lot to Sławek Piotrowski for contributing the decoder (as well as an example file for sigrok-dumps)! We've also added a small test-case in the sigrok-test repository to be able to keep track of any potential regressions that might occur later. [Less]

We're happy to announce that libsigrok now supports the Manson HCS-3xxx series of programmable power supplies (PPS). Thanks a lot to Matthias Heidbrink for improving the driver and extending it to support more models in this series! See the model ... [More] overview for more details. There are various rebadged versions sold by Conrad/Voltcraft, PeakTech, and probably other resellers. All power supplies in this series have one channel only, featuring various voltage/current/power combinations though. They're connected to the PC via a (built-in) USB-to-serial IC (e.g. the SiLabs CP2102 in the Manson HCS-3202). A relatively simple ASCII-based protocol is used to communicate with the devices and control them. You can control the power supplies e.g. via sigrok-cli like this: $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --show manson-hcs-3xxx - Manson HCS-3202 with 1 channel: CH1 Supported configuration options: output_current: 0.000000 output_current_limit: 0.000000 output_enabled: on (current), off output_voltage: 3.390000 output_voltage_target: 0.000000 $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --samples 2 -O analog CH1: 3.300000 V DC CH1: 0.000000 A CH1: 3.380000 V DC CH1: 0.000000 A $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_voltage_target=5.0 --set $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_enabled=yes --set The code was tested on the Manson HCS-3202 and the Voltcraft PPS-11815. Please let us know if you are able to test any of the other devices the driver is supposed to support, and/or whether you experience any issues.   [Less]

We're happy to announce that libsigrok now supports the Manson HCS-3xxx series of programmable power supplies (PPS). Thanks a lot to Matthias Heidbrink for improving the driver and extending it to support more models in this series! See the model ... [More] overview for more details. There are various rebadged versions sold by Conrad/Voltcraft, PeakTech, and probably other resellers. All power supplies in this series have one channel only, featuring various voltage/current/power combinations though. They're connected to the PC via a (built-in) USB-to-serial IC (e.g. the SiLabs CP2102 in the Manson HCS-3202). A relatively simple ASCII-based protocol is used to communicate with the devices and control them. You can control the power supplies e.g. via sigrok-cli like this: $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --show manson-hcs-3xxx - Manson HCS-3202 with 1 channel: CH1 Supported configuration options: output_current: 0.000000 output_current_max: 0.000000 output_enabled: on (current), off output_voltage: 3.390000 output_voltage_max: 0.000000 $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --samples 2 -O analog CH1: 3.300000 V DC CH1: 0.000000 A CH1: 3.380000 V DC CH1: 0.000000 A $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_voltage_max=5.0 --set $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_enabled=yes --set The code was tested on the Manson HCS-3202 and the Voltcraft PPS-11815. Please let us know if you are able to test any of the other devices the driver is supposed to support, and/or whether you experience any issues.   [Less]

We're happy to announce that libsigrok now supports the Manson HCS-3xxx series of programmable power supplies (PPS). Thanks a lot to Matthias Heidbrink for improving the driver and extending it to support more models in this series! See the model ... [More] overview for more details. There are various rebadged versions sold by Conrad/Voltcraft, PeakTech, and probably other resellers. All power supplies in this series have one channel only, featuring various voltage/current/power combinations though. They're connected to the PC via a (built-in) USB-to-serial IC (e.g. the SiLabs CP2102 in the Manson HCS-3202). A relatively simple ASCII-based protocol is used to communicate with the devices and control them. You can control the power supplies e.g. via sigrok-cli like this: $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --show manson-hcs-3xxx - Manson HCS-3202 with 1 channel: CH1 Supported configuration options: output_current: 0.000000 output_current_limit: 0.000000 output_enabled: on (current), off output_voltage: 3.390000 output_voltage_target: 0.000000 $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --samples 2 -O analog CH1: 3.300000 V DC CH1: 0.000000 A CH1: 3.380000 V DC CH1: 0.000000 A $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_voltage_target=5.0 --set $ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_enabled=yes --set The code was tested on the Manson HCS-3202 and the Voltcraft PPS-11815. Please let us know if you are able to test any of the other devices the driver is supposed to support, and/or whether you experience any issues.   [Less]

libsigrokdecode now supports the spdif decoder. The Sony/Philips Digital Interface Format (S/PDIF) is a (nowadays standardized in IEC 60958) digital audio protocol that is used in various devices and supported by a number of ICs, such as the TI ... [More] PCM2707 and many others. A short description of the protocol is available on the respective wiki page, along with pointers to further reading. Thanks a lot to Guenther Wenninger for contributing the decoder! [Less]