bin file for testing

OpenDPS

Give your DPS5005 the upgrade it deserves

OpenDPS is a FOSS firmware replacement for the DPS5005 (and DPS3003, DPS3005, DPS5015, DP50V5A, DPS5020 and possibly others) that has the same functionality, has a less cluttered user interface and is remote controllable via wifi (ESP8266) or via a serial port.

There are three accompanying blog posts you might find of interest:

Part one covers the reverse engineering of the DPS5005.
Part two describes the design of OpenDPS.
Part three covers the process of upgrading stock DPS5005:s to OpenDPS.

Upgrading your DPS5005

If you are eager to upgrade your DPS5005, you may skip directly to part three. Oh, and of course you can use OpenDPS for more than a programmable power supply. Why not use it as an interface for your DIY sous vide cooker :D

Cloning & building

First build the OpenDPS firmware:

git clone --recursive https://github.com/kanflo/opendps.git
cd opendps
make -C libopencm3
make -C opendps flash
make -C dpsboot flash

Check the blog for instructions on how to unlock and flash your DPS5005.

Second, build and flash the ESP8266 firmware. First you need to create the file esp8266-proxy/esp-open-rtos/include/private_ssid_config.h with the following content:

#define WIFI_SSID "My SSID"
#define WIFI_PASS "Secret password"

make -C esp8266-proxy flash

Setup dpsctl.py

The script runs with python2 and python3. The libraries pycrc and pyserial are required:

pip install -r requirements.txt

Usage

A vanilla OpenDPS device will support two functions, constant voltage (cv) and constant current (cc). A tool called dpsctl.py can be used to talk to an OpenDPS device to query functionality and supported parameters for each function.

Once upgraded and connected to an ESP8266, type the following at the terminal to find its IP address:

% dpsctl.py --scan
172.16.3.203
1 OpenDPS device found

Enable constant voltage (cv) at 3.3V limited to 500mA:

% dpsctl.py -d 172.16.3.203 -f cv
Changed function.

% dpsctl.py -d 172.16.3.203 -p voltage=3300 current=500
voltage: ok
current: ok

% dpsctl.py -d 172.16.3.203 -o on

Query the status of the device:

% dpsctl.py -d 172.16.3.203 -q
Func       : cv (on)
  current  : 500
  voltage  : 3300
V_in       : 12.35 V
V_out      : 3.33 V
I_out      : 0.152 A

List supported functions of the device:

% dpsctl.py -d 172.16.3.203 -F
Selected OpenDPS supports the cv and cc functions.

List supported functions parameters of current function:

% dpsctl.py -d 172.16.3.203 -P
Selected OpenDPS supports the voltage (mV) current (mA) parameters for the cv function.

Additionally, dpsctl.py can return JSON, eg.:

% dpsctl.py -d 172.16.3.203 -q -j
{
    "command": 132,
    "cur_func": "cv",
    "i_out": 151,
    "output_enabled": 1,
    "params": {
        "current": "500",
        "voltage": "3300"
    },
    "status": 1,
    "v_in": 12355,
    "v_out": 3321
}

Upgrading

As newer DPS:es have 1.25mm spaced JTAG pins (JST-GH) and limited space for running the JTAG signals towards the back of the device, a permanent soldered JTAG is somewhat cumbersome. People not activly developing OpenDPS will not need JTAG anyway. To facilitate upgrade, OpenDPS comes with a bootloader enabling upgrade over UART:

% make -C opendps bin
% dpsctl.py -d /dev/ttyUSB0 -U opendps/opendps.bin

If you accidentally upgrade to a really b0rken version, the bootloader can be forced to enter upgrade mode if you keep the SEL button pressed while enabling power.

The display will be black during the entire upgrade operation. If it stays black, the bootloader might refuse or fail to start the OpenDPS application, or the application crashed. If you attempt the upgrade operation again, and upgrading begins, the bootloader is running but is refusing to boot your firmware. But why? Well, let's find out. If you append the -v option to dpsctl.py you will get a dump of the UART traffic.

Communicating with /dev/ttyUSB0
TX  9 bytes 7e 09 04 00 27 86 0c b2 7f
RX 9 bytes 7e 89 00 04 00 03 66 0f 7f

The fourth byte from the end in the received data (0x03 in this example) will tell us why the bootloader refused to boot the firmware. See protocol.h for the different reasons.

Custom Fonts

If you would like to use a your own font for OpenDPS you may do so by doing the following:

% make -C opendps fonts \
    METER_FONT_FILE=<path_to_font> \
    METER_FONT_SMALL_SIZE=18 \
    METER_FONT_MEDIUM_SIZE=24 \
    METER_FONT_LARGE_SIZE=48 \
    FULL_FONT_FILE=<path_to_font> \
    FULL_FONT_SMALL_SIZE=15

Supported fonts are .ttf or .otf

Source code organisation

The project consists of four parts:

dpsboot/ The OpenDPS bootloader.
opendps/ The OpenDPS firmware.
esp8266-proxy/ The ESP8266 firmware for wifi connected OpenDPS:es.
dpsctl/ A Python script for controlling your OpenDPS via wifi or a serial port.
emu/ Xcode project and GNU makefile for running an emulated OpenDPS.

What about other DPS:es?

OpenDPS has been verified to work with other models in the DPSx0xx series, such as the DPS3003, DPS3005, DPS5015 and DPS5020. The maxium settable output current can be defined when building opendps, see the makefile. Plese note that the hardware design might change at any time without any notice (I am not affiliated with its designer). This will render OpenDPS unusable until fixed.

Licensed under the MIT license. Have fun!

	static void number_draw(ui_item_t *_item)
	{
	uint32_t cur_digit = 0;
	ui_number_t item = (ui_number_t) _item;
	uint32_t value = item->value;
	uint32_t w, h;
	switch (item->font_size) {
	case 18:
	w = font_18_widths[4]; /** @todo: Find the widest glyph */
	h = font_18_height;
	break;
	case 24:
	w = font_24_widths[4] + 2; /** @todo: Find the widest glyph */
	h = font_24_height + 2;
	break;
	case 48:
	w = font_48_widths[4] + 2; /** @todo: Find the widest glyph */
	h = font_48_height + 2;
	break;
	}
	uint16_t xpos = _item->x - w;
	switch(item->unit) {
	case unit_volt:
	tft_putch(item->font_size, 'V', xpos, _item->y, w, h, false);
	break;
	case unit_ampere:
	tft_putch(item->font_size, 'A', xpos, _item->y, w, h, false);
	break;
	default:
	assert(0);
	}
	xpos -= item->font_size == 18 ? 2 : 4;
	for (uint32_t i = 0; i < item->num_decimals; i++) {
	bool highlight = _item->has_focus && item->cur_digit == cur_digit;
	xpos -= w;
	tft_putch(item->font_size, '0'+(value%10), xpos, _item->y, w, h, highlight);
	value /= 10;
	cur_digit++;
	}
	xpos -= item->font_size == 18 ? 4 : 10;
	tft_putch(item->font_size, '.', xpos, _item->y, item->font_size == 18 ? 4 : 10, h, false);
	for (uint32_t i = 0; i < item->num_digits; i++) {
	bool highlight = _item->has_focus && item->cur_digit == cur_digit;
	xpos -= w;
	tft_putch(item->font_size, '0'+(value%10), xpos, _item->y, w, h, highlight);
	value /= 10;
	cur_digit++;
	if (!value && !_item->has_focus) { /** To prevent from printing 00.123 */
	xpos -= w;
	tft_fill(xpos, _item->y, w, h, 0);
	break;
	}
	}
	}

kanflo / opendps Goto Github PK

opendps's Introduction

OpenDPS

Give your DPS5005 the upgrade it deserves

Upgrading your DPS5005

Cloning & building

Setup dpsctl.py

Usage

Upgrading

Custom Fonts

Source code organisation

What about other DPS:es?

opendps's People

Contributors

Stargazers

Watchers

Forkers

opendps's Issues

Recommend Projects

Recommend Topics

Recommend Org