CurrentViewer interactive data plot for LowPowerLab CurrentRanger. It was designed to make it easier to capture, save and share power state profiles for IoT devices that swing between multiple power states (deep sleep, low power, full power).
It works on:
- Windows 10
- Linux
- Raspberry Pi
Example above is CurrentViewer in action (exported from the app itself via GIF function).
Note: CurrentViewer is not a replacement for an osciloscope, as the readings are done via the internal ADC in SAMD21 Microchip's ARM® Cortex®-M0+ which has its limitations. But it might be more convenient way to use CurrentRanger. Sometimes the noise (Vpp) can be comparable with entry level oscilloscopes, but the measurements can be off: CurrentRanger has to be properly calibrated in order for the measurements to match what multimeter or oscilloscope displays.
- Runs on Windows and Linux (MacOS coming soon)
- Live Interactive chart with:
- 100k samples in view and can do millions: the raw readings are noise-filtered (sub-sampling and average) to improve visualization
- Last Raw and Window Average mesurements and SPS (Samples per Second - how fast CurrentRanger sends samples over USB)
- Point annotations: hover the mouse over a certain sample so see the exact value
- Logaritmic plot: makes it easy to read any swings from 1 nanoamp to 1 amp. Works with CurrentRanger in AUTORANGE as well as manual mode.
- Data Export: CSV and JSON but it can also save the animated chart as .GIF - for a convenient way to publish measurements on the web. Look for current0.gif, current1.gif, etc in the current folder
- Command line options to tune for performance or batch mode (headless logging). Should be able to display as fast as the instrument can measure and send data over USB-Serial: currently this is around 600-800 samples/second (depends on firmware and features enabled on CR)
- Automatically turns on streaming on CurrentRanger (and if you use the new firmware feature with SMART AutoOff now the instrument will stay on as long as CurrentViewer is connected to it).
- [Pause] streaming if you want to zoom/pan into the data. The data is still being captured behind (live buffer), when you resume you see an instant refresh
First clone the repo locally
git clone https://github.com/MGX3D/CurrentViewer
Recommended environment is Python3 (tested with 3.6+) with matplotlib/mplcursors/pyserial installed. To install all the requirements automatically:
pip3 install -r requirements.txt
or
pip3 install -r requirements.txt
First you need to identify the COM port CurrentRanger is plugged into (eg COM3 or /dev/ttyACM0). CurrentViewer is typically being tested with direct USB connection only but it should work with BlueTooth as well (however BT is not an area of focus for CurrentViewer due to lower bandwidth)
On Windows:
python3 current_viewer.py -p COM9
On Linux/Raspberry:
python3 current_viewer.py -p /dev/ttyACM0
If everything is working well you should see an image like this below:
There is also a console window which displays regular SPS and a debugging log file - current_viewer.log that displays more details, down to individual sample errors (eg negative readings, wire corruptions, etc). For the time being the logging is enabled by default to help with diagnostics, but there is an option to disable it (--no-log)
A number of options can be passed in command line to control export data to CSV/JSON, to control the charting speed and behavior, etc
CurrentViewer v1.0.2
usage: current_viewer.py -p <port> [OPTION]
CurrentRanger R3 Viewer
optional arguments:
-h, --help show this help message and exit
--version show program's version number and exit
-p PORT, --port PORT Set the serial port (backed by USB or BlueTooth) to
connect to (example: /dev/ttyACM0 or COM3)
-s <n>, --baud <n> Set the serial baud rate (default: 115200)
-o <file>, --out <file>
Save the output samples to <file> in the format set by
--format
--format <fmt> Set the output format to one of: CSV, JSON
--gui Display the GUI / Interactive chart (default: ON)
-g, --no-gui Do not display the GUI / Interactive Chart. Useful for
automation
-b <samples>, --buffer <samples>
Set the chart buffer size (window size) in # of
samples (default: 100000)
-m <samples>, --max-chart <samples>
Set the chart max # samples displayed (default: 2048)
-r <ms>, --refresh <ms>
Set the live chart refresh interval in milliseconds
(default: 66)
-v, --verbose Increase logging verbosity (can be specified multiple
times)
-c, --console Show the debug messages on the console
-n, --no-log Disable debug logging (enabled by default)
--log-size <Mb> Set the log maximum size in megabytes (default: 1Mb)
-l LOG_FILE, --log-file LOG_FILE
Set the debug log file name
(default:current_viewer.log)
python current_viewer.py -p COM9 -g --out data.csv
This is useful for automation scenarios, where data needs to be logged for long periods of time and the charting is not needed.
python current_viewer.py -p COM9 -g -n -c -vvv
The file log (current_viewer.log) is now capped to 1MB and automatically rotated so it won't use the entire disk space by accident, but even then it can still be noisy (eg protocol errors) and generate lots of IO/writes. In some cases - for example SD/USB cards with limited write cycles - this might be undesirable, so now it's possible to disable disk logging completely with -n / --no-log option.
python current_viewer.py -p COM9 -m 100 -r 1000
The charting library is CPU intensive, so setting a slower refresh (1fps instead of 15fps) or drawing fewer samples 100 (instead of 2048 which is the default with 4K monitors in mind) can reduce CPU consumption and increase rendering speed. The other parameter that can affect performance - in this case memory consumption - is -b/--buffer, this is the in-memory buffer, this represents the maximum view of the chart (-m is the # of data points in that range). For example if your CR is sending 600 samples/second at 100K sample buffer you get a history of roughly 3 minutes. Note that the buffer setting only affects the chart (how much is in view) and it does not affect the logging to CSV/JSON: exported data is saved to file directly from the acquisition loop so in theory should work for hours or days without issue.
python current_viewer.py -p COM9 -vvv --log-size 128
This increases the log maximum size to 128 megabytes from the default of 1 (alteratively --log-size 0.1 would cap the log at ~100Kb). It could be useful in capturing hard to reproduce errors. Note there are two logs on disk: the current one (current_viewer.log) and the rotated one (current_viewer.log.1), so the total log on disk is actually double this parameter.
There are currently two data formats that CurrentViewer can save: CSV and JSON. See options --out and --format. If the format is not specified CurrentViewer tries to guess it based on extension (ie --out foo.json or --out bar.csv should be sufficient)
Timestamp, Amps
2020-11-09 11:21:08.510715,-0.00081
2020-11-09 11:21:08.526342,-0.0004
2020-11-09 11:21:08.526342,-0.00081
2020-11-09 11:21:08.526342,-0.0004
2020-11-09 11:21:08.526342,-0.00121
2020-11-09 11:21:08.526342,-0.00121
2020-11-09 11:21:08.526342,-0.00121
2020-11-09 11:21:08.526342,-0.00121
2020-11-09 11:21:08.526342,-0.00121
2020-11-09 11:21:08.526342,-0.00081
2020-11-09 11:21:08.526342,-0.00121
2020-11-09 11:21:08.541963,-0.00121
2020-11-09 11:21:08.541963,-0.00121
2020-11-09 11:21:08.541963,-0.00081
2020-11-09 11:21:08.541963,-0.00121
2020-11-09 11:21:08.541963,-0.00081
2020-11-09 11:21:08.541963,-0.00081
{
"data":[
{"time":"2020-11-09 11:51:08.439275","amps":"4.07e-08"},
{"time":"2020-11-09 11:51:08.439275","amps":"7.938e-08"},
{"time":"2020-11-09 11:51:08.439275","amps":"1.652e-08"},
{"time":"2020-11-09 11:51:08.439275","amps":"2.01e-09"},
{"time":"2020-11-09 11:51:08.439275","amps":"-2.74e-08"},
{"time":"2020-11-09 11:51:08.439275","amps":"-2.78e-08"},
{"time":"2020-11-09 11:51:08.439275","amps":"-2.74e-08"},
{"time":"2020-11-09 11:51:08.439275","amps":"-1.692e-08"},
{"time":"2020-11-09 11:51:08.454900","amps":"-4.03e-09"},
{"time":"2020-11-09 11:51:08.454900","amps":"3.949e-08"},
{"time":"2020-11-09 11:51:08.454900","amps":"5.883e-08"},
{"time":"2020-11-09 11:51:08.454900","amps":"6.125e-08"},
{"time":"2020-11-09 11:51:08.454900","amps":"1.168e-08"},
{"time":"2020-11-09 11:51:08.454900","amps":"4e-10"},
{"time":"2020-11-09 11:51:08.454900","amps":"-2.78e-08"},
{"time":"2020-11-09 11:51:08.466614","amps":"-2.78e-08"},
{"time":"2020-11-09 11:51:08.467614","amps":"-2.78e-08"}
]
}- Some runtime errors on MacOS / Python 3.8.5.
- Not tested with the BlueTooth add-on yet
- Cannot always put the device in a predictable USB streaming mode (check the troubleshooting steps below)
- Negative data (or noisy data) - this is what's coming from the device. As the firmware improves (Felix has some ideas) this will improve as well.
Note: Do not direct CurrentViewer support requests to LowPowerLab, this is not an official tool, it's provided AS-IS. This is a side-project for me (and first time dealing with matplotlib in particular, so I will try to address issues as time (and skill) allows :)
-
This was tested with Python 3.6-3.8 (on Windows 10), 3.7.3 (Linux ARM / Rasppberry), 3.8.5 (in Linux x64) . Currently not working on MacOS 10.15 (although it should - but no time to debug). The dependencies that are critical and might break in the future are:
- matplotlib (tested with 3.1.1)
- mplcursors (tested with 0.3)
- numpy / pandas - these are new dependencies added in 1.0.1. There are already known issues with Python 3.9 and matplotlib/numpy, if you run into those stick to 3.8 or use virtual environments
If you encounter errors with installing numpy or matplotlib, be sure to check out this full thread (and the temporary workaround) https://developercommunity.visualstudio.com/solutions/1257144/view.html
-
Make sure you can connect to the COM port (using Arduino, Putty, etc) and you see the CurrentRanger menu (type '?'). Then enable USB streaming (command 'u') and check if the data is actually coming in the expected exponent format (see below)
-
CurrentViewer expects only measurements in the exponent format ('-0.81e-3') streamed over USB. if you have other things enabled (such as Touch debugging) you might see a lot of errors or inconsistent data. CurrentViewer measures the error rate and if above a certain threshold (50%) will stop.
I typically test with my branch of the firmware (https://github.com/MGX3D/CurrentRanger) as I only have one CurrentRanger but I try to not rely on features that are not available in the official firmware.
-
Make sure your CurrentRanger is set to auto-off=SMART (make sure you have firmware 1.0.0 or newer, connect to the port and send 'a' command until it says "AUTOOF_SMART" then confirm with '?' - the setting will be now persisted in EEPROM)
-
Check current_viewer.log (and its rotate log current_viewer.log.1) and look for hints. If no luck, open an issue on github and attach the log(s). Do describe your hardware setup as well, and perhaps check how the device behaves with other tools (Arduino, Putty, etc)
Contributions are welcome (note the MIT license), best to fork the project and submit a PR when done. Try to keep the changes small so they are easier to merge.