DPS5005 - Revision history

Leo: Linked to OpenDPS

2021-06-09T05:42:23Z

Linked to OpenDPS

← Older revision		Revision as of 05:42, 9 June 2021
Line 2:		Line 2:
	The DPS5005, and related DPS3005, DPS5015, DP50V5A, are smart buck regulators and can be used as a budget 'bench' power supply modules. These units are powered by a STM32F100 microprocessor and includes a 1.44" TFT color LCD display.		The DPS5005, and related DPS3005, DPS5015, DP50V5A, are smart buck regulators and can be used as a budget 'bench' power supply modules. These units are powered by a STM32F100 microprocessor and includes a 1.44" TFT color LCD display.

	The more recent versions of DP50V5A and the DPS5005 are virtually identical except for the difference in firmware. The DP50V5A has an inferior firmware which makes the interface laggy along with a slight difference in how the M1/M2 buttons are mapped. Despite these differences, OpenDPS can be installed and the button mappings can be made to work in the same manner.		The more recent versions of DP50V5A and the DPS5005 are virtually identical except for the difference in firmware. The DP50V5A has an inferior firmware which makes the interface laggy along with a slight difference in how the M1/M2 buttons are mapped. Despite these differences, [[OpenDPS]] can be installed and the button mappings can be made to work in the same manner.

	==STM32 ~~Flash Information~~==		== Custom firmware ==
			You can load a customized open source firmware called [[OpenDPS]]. All you need is a STLink and some fine wire to connect to the JTAG on the back of the unit and a computer that can run OpenOCD.

			==STM32 flash information==
	The STM32F100 has a 64KB/(128KB?) flash. The original firmware is protected and cannot be read. You can disable readout protection by unlocking the STM32 microcontroller but this will wipe all existing data.		The STM32F100 has a 64KB/(128KB?) flash. The original firmware is protected and cannot be read. You can disable readout protection by unlocking the STM32 microcontroller but this will wipe all existing data.

Leo: Moved OpenDPS content to OpenDPS

2021-06-09T05:40:31Z

Moved OpenDPS content to OpenDPS

Show changes

Leo at 08:56, 22 May 2021

2021-05-22T08:56:56Z

← Older revision		Revision as of 08:56, 22 May 2021
Line 7:		Line 7:
	The stock firmware can be overwritten with an open source firmware called OpenDPS. The official project repo is at https://github.com/kanflo/opendps.		The stock firmware can be overwritten with an open source firmware called OpenDPS. The official project repo is at https://github.com/kanflo/opendps.

	I have added additional features to OpenDPS including the colorful DPS-like display from the original firmware and can be found on my private repo under the <code>dps_mode</code> branch at~~<nowiki/>~~https://git.steamr.com/others/opendps/-/tree/dps_mode/opendps		I have added additional features to OpenDPS including the colorful DPS-like display from the original firmware and can be found on my private repo under the <code>dps_mode</code> branch at https://git.steamr.com/others/opendps/-/tree/dps_mode/opendps

	Some additional features that OpenDPS has include:		Some additional features that OpenDPS has include:
Line 18:		Line 18:
	===Compiling and installing===		===Compiling and installing===

	==== Software requirements ====		====Software requirements====
	You will need the following to get OpenDPS running on your power supply:		You will need the following to get OpenDPS running on your power supply:

Line 58:		Line 58:
	}}		}}

	==== Hardware ====		====Hardware====
	[[File:STLink DPS Pinout.jpg\|thumb\|right\|300px]]To begin, connect your STLink to the DPS as per the pinout in the picture on the right. Connect the STLink to your computer and then apply power to the DPS power supply. OpenOCD should be able to detect the device.		[[File:STLink DPS Pinout.jpg\|thumb\|right\|300px]]To begin, connect your STLink to the DPS as per the pinout in the picture on the right. Connect the STLink to your computer and then apply power to the DPS power supply. OpenOCD should be able to detect the device.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 81:		Line 81:
	}}		}}

	In case your device is unique and has no support, use the bundled {{code\|ocd-client.py}} script to generate a log file with all registers, hardware peripherals including ADC and DACs, timers, GPIOs, etc. If you are working on a supported device (~~ie.~~ the {{code\|dps-models.h}} file has mention of your model), you should be safe to skip this step. Create a few dumps of the device in different states (Off / On and set to different voltages) in order to make it easier to identify which GPIO pins and ADC/DACs are in use and for what purpose. The stock firmware will freeze when OpenOCD is used. The only work-around is to configure the device with the STLink disconnected and the re-connect the STLink when you are ready to create a dump.		In case your device is unique and has no support, use the bundled {{code\|ocd-client.py}} script to generate a log file with all registers, hardware peripherals including ADC and DACs, timers, GPIOs, etc. If you are working on a supported device (that is, the {{code\|dps-models.h}} file has mention of your model), you should be safe to skip this step.

	Dumps are created with {{code\|ocd-client.py}} script like this:		If your device isn't listed in the <code>dps-models.h</code> header file, it's recommended that you create a few dumps of the device in different states (Off / On and set to different voltages) in order to make it easier to identify which GPIO pins and ADC/DACs are in use and for what purpose. The stock firmware may freeze when OpenOCD is used. The only work-around is to configure the device with the STLink disconnected and the re-connect the STLink when you are ready to create a dump. Dumps are created with {{code\|ocd-client.py}} script like this:{{highlight\|lang=terminal\|code=
	{{highlight\|lang=terminal\|code=
	$ python ocd-client.py all > dump.txt		$ python ocd-client.py all > dump.txt
	}}		}}

	==== Compiling ====		====Compiling====
	To compile and flash OpenDPS on your device, clone the OpenDPS repository. I will be using my <code>dps_mode</code> branch in the examples below, but you may substitute it with the official OpenDPS repository.		To compile and flash OpenDPS on your device, clone the OpenDPS repository. I will be using my <code>dps_mode</code> branch in the examples below, but you may substitute it with the official OpenDPS repository.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 105:		Line 104:
	Adjust the make flags as desired. I leave most features disabled as I prefer to only have the DPS screen and settings screen without the features.		Adjust the make flags as desired. I leave most features disabled as I prefer to only have the DPS screen and settings screen without the features.

	===== Troubleshooting compile issues =====		=====Troubleshooting compile issues=====
	If you get an error similar to: <code>opendps/libopencm3/include/libopencm3/dispatch/nvic.h:8:11: fatal error: libopencm3/stm32/f1/nvic.h: No such file or directory</code>, try running make without any arguments. This should pull in and build the libopencm3 dependency. This issue seems to be an issue with the Makefile on a clean build directory.		If you get an error similar to: <code>opendps/libopencm3/include/libopencm3/dispatch/nvic.h:8:11: fatal error: libopencm3/stm32/f1/nvic.h: No such file or directory</code>, try running make without any arguments. This should pull in and build the libopencm3 dependency. This issue seems to be an issue with the Makefile on a clean build directory.

Leo at 08:53, 22 May 2021

2021-05-22T08:53:29Z

Show changes

Leo: Adding info on how I built my branch

2020-11-01T18:46:37Z

Adding info on how I built my branch

← Older revision		Revision as of 18:46, 1 November 2020
Line 91:		Line 91:

	====DPS Mode Screen====		====DPS Mode Screen====
	The DPS Mode screen shows the voltage, current, and power output being supplied by the power supply and was designed to look and feel as close to the original DPS firmware as possible while retaining a cleaner user interface.		The DPS Mode screen shows the voltage, current, and power output being supplied by the power supply and was designed to look and feel as close to the original DPS firmware as possible while retaining a cleaner user interface. Until this feature is merged in the official repo, you can get it by merging the pull request or use the [https://git.steamr.com/others/opendps/-/tree/d4 d4 branch on my repo]. This feature is enabled by default using the <code>DPSMODE_ENABLE</code> flag. When building from this branch, the options I used were: <code>make -C opendps flash -j 9 MODEL=DPS5005 INVERT_ENABLE=0 CC_ENABLE=0 CL_ENABLE=0 CV_ENABLE=0 POWER_COLORED=1 POWER_OFF_VISIBLE=1 THERMAL_LOCKOUT=0 SETTINGS_ENABLE=1</code>

	[[File:DSP5005 Interface.png\|frame\|center\|DSP5005 Interface]] Buttons work as you would expect: {{code\|V}} will allow editing of the maximum voltage. {{code\|A}} will allow editing of the maximum current.		[[File:DSP5005 Interface.png\|frame\|center\|DSP5005 Interface]] Buttons work as you would expect: {{code\|V}} will allow editing of the maximum voltage. {{code\|A}} will allow editing of the maximum current.

Leo: /* OpenDPS */

2020-11-01T18:41:40Z

OpenDPS

Show changes

Leo: Added category

2020-06-14T23:28:30Z

Added category

← Older revision		Revision as of 23:28, 14 June 2020
Line 245:		Line 245:
	== See Also ==		== See Also ==
	* https://stackoverflow.com/questions/32509747/stm32-read-out-protection-via-openocd		* https://stackoverflow.com/questions/32509747/stm32-read-out-protection-via-openocd

			{{Navbox Tinkering}}[[Category:Tinkering]]

Leo: /* DPS Mode Screen */

2019-10-06T02:42:19Z

DPS Mode Screen

← Older revision		Revision as of 02:42, 6 October 2019
Line 88:		Line 88:
	The DPS Mode screen shows the voltage, current, and power output being supplied by the power supply and was designed to look and feel as close to the original DPS firmware as possible while retaining a cleaner user interface.		The DPS Mode screen shows the voltage, current, and power output being supplied by the power supply and was designed to look and feel as close to the original DPS firmware as possible while retaining a cleaner user interface.

			[[File:DSP5005 Interface.png\|frame\|center\|DSP5005 Interface]] Buttons work as you would expect: {{code\|V}} will allow editing of the maximum voltage. {{code\|A}} will allow editing of the maximum current.

			The user interface can be locked by holding the {{code\|Rotary}} down until a padlock symbol appears near the bottom of the screen. Conversely, the interface can be unlocked by holding the {{code\|Rotary}} down until the padlock symbol disappears.

			-----

			[[File:DSP5005 Third Item Interface.png\|center\|frame\|DSP5005 Third Item Interface]] The third value on the screen can be changed using the {{code\|Rotary Press}} + {{code\|Rotary Turn}} combination. Values that are displayed in the third row can be edited using {{code\|Rotary Press}}, or by navigating through the interface using {{code\|SET}} + {{code\|M1}} or {{code\|SET}} + {{code\|M2}}. The DPS Mode screen currently supports editing of:
			* Power Output / Power Limit
			* Timer (time until power off, or time since power on)
			* Brightness
			* Watt-Hour Meter (measured in milliwatt-hours).
			------

			[[File:DSP5005 Power Interface.png\|center\|frame]] When the DPS unit is turned on, you will see either {{code\|CC}} or {{code\|CV}} signifying whether the device is in constant current or constant voltage mode. Depending on the power output limit that is set, a power output warning may be seen when power output exceeds 80% of the power limit. Exceeding the power limit will automatically turn the output off.
			------

			[[File:DSP5005 Preset and Timer.png\|center\|frame]] The DPS screen supports up to two recall preset settings. Each preset setting saves the voltage, current limit, power limit, and timer value. Recall a preset by holding {{code\|M1}} or {{code\|M2}}. Save a preset by holding {{code\|SET}} + {{code\|M1}} or {{code\|SET}} + {{code\|M2}}.

			If a timer is set prior to power on, a hourglass icon will flash signifying that a timer is set. When the timer elapses, power will automatically be shut off. If the timer is not set prior to power on, the timer will act as a clock and will show the duration since power on.

	=== Calibration ===		=== Calibration ===

Leo at 23:56, 5 October 2019

2019-10-05T23:56:37Z

← Older revision		Revision as of 23:56, 5 October 2019
Line 2:		Line 2:
	The DPS5005, and related DPS3005, DPS5015, DP50V5A, are variable 'bench' power supply modules. It contains a STM32F100 microprocessor and a 1.44" TFT color LCD display.		The DPS5005, and related DPS3005, DPS5015, DP50V5A, are variable 'bench' power supply modules. It contains a STM32F100 microprocessor and a 1.44" TFT color LCD display.

	The DP50V5A and the DPS5005 are virtually identical except for the difference in firmware. The DP50V5A has an inferior firmware which makes it laggy along with a slight difference in how the M1/M2 buttons are mapped. Despite these differences, OpenDPS can be installed and the button mappings can be made to work in the same manner.		The more recent versions of DP50V5A and the DPS5005 are virtually identical except for the difference in firmware. The DP50V5A has an inferior firmware which makes the interface laggy along with a slight difference in how the M1/M2 buttons are mapped. Despite these differences, OpenDPS can be installed and the button mappings can be made to work in the same manner.

	== OpenDPS ==		== OpenDPS ==
Line 50:		Line 50:
	}}		}}

	To ~~load~~ OpenOCD on your device, clone the OpenOCD repository.		To compile and flash OpenOCD on your device, clone the OpenOCD repository.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	$ git clone https://github.com/kanflo/opendps		$ git clone https://github.com/kanflo/opendps
	}}		}}

	On the project root directory:		On the project root directory, start OpenOCD and compile the project.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	## Open a OpenOCD if not done already		## Open a OpenOCD if not done already
Line 63:		Line 63:

	## Compile OpenDPS and then flash it on the device:		## Compile OpenDPS and then flash it on the device:
	$ make -C opendps flash -j 9 MODEL=~~DP50V5A~~ INVERT_ENABLE=0 CC_ENABLE=0 CL_ENABLE=0 CV_ENABLE=0 POWER_COLORED=1 POWER_OFF_VISIBLE=1		$ make -C opendps flash -j 9 MODEL=DPS5005 INVERT_ENABLE=0 CC_ENABLE=0 CL_ENABLE=0 CV_ENABLE=0 POWER_COLORED=1 POWER_OFF_VISIBLE=1 THERMAL_LOCKOUT=0

	## Flash the boot loader:		## Flash the boot loader:
Line 71:		Line 71:
	It is normal for the device to have a blank screen after the OpenDPS flash. It should boot up after flashing the {{code\|dpsboot}} bootloader. This is a bug with the build system and you will always have to flash both OpenDPS and the DPSBoot bootloader for the device to function.		It is normal for the device to have a blank screen after the OpenDPS flash. It should boot up after flashing the {{code\|dpsboot}} bootloader. This is a bug with the build system and you will always have to flash both OpenDPS and the DPSBoot bootloader for the device to function.

	If you have issues compiling, try ~~to run~~ {{code\|make}} on the root directory once and then try again~~. There is something wonky with the build system where targets aren't build in the right order or something~~.		If you have issues compiling and get an error {{code\|/home/pi/opendps/libopencm3/include/libopencm3/dispatch/nvic.h:8:11: fatal error: libopencm3/stm32/f1/nvic.h: No such file or directory
			}}, try running {{code\|make}} on the root directory once (it will error on something else, but it shouldn't matter) and then try again.

	If buttons aren't working, then your hardware might be using different GPIO pins. Refer to the dump made above to determine any necessary changes needed to the code.		If buttons aren't working, then your hardware might be using different GPIO pins. Refer to the dump made above to determine any necessary changes needed to the code.

	If voltages and currents are off, you need to calibrate the device by adjusting the {{code\|dps-models.h}} file.		If voltages and currents are off, you need to calibrate the device by adjusting the {{code\|dps-models.h}} file.

			=== Usage ===
			OpenDPS makes use of multiple screens, each with a different set of functions. The key combinations used to switch screens are {{code\|SET + Rotary}}.

			Power is controlled using the {{code\|ON / OFF}} switch.

			To protect from accidental changes while powered on, the interface can be locked or unlocked by pressing and holding {{code\|Rotary}}. When locked, no interface or settings can be changed.

			==== DPS Mode Screen ====
			The DPS Mode screen shows the voltage, current, and power output being supplied by the power supply and was designed to look and feel as close to the original DPS firmware as possible while retaining a cleaner user interface.



	=== Calibration ===		=== Calibration ===
	~~There~~ are 2 DAC and 2 ADCs ~~in use~~. The ~~pair of~~ DACs ~~are used to~~ control voltage ~~and current limits~~ while the ADCs ~~are used to detect~~ the voltage ~~and current being supplied~~. Typically, you will need to calibrate these DACs and DACs in order to have accurate ~~readings~~.		Voltage and current are controlled using a pair of DAC and ADCs. The two DACs control the output current and voltage while the two ADCs measure the current and voltage. Typically, you will need to calibrate these DACs and DACs in order to have accurate values.

	Calibration involves finding the slope (K) and offset constant (C) of the DAC/ADC curve. The curve is linear and can be found by finding two points. For DACs, we want to map the input value to the DAC (0 ~ 4096) to the actual output value (voltage or current limits). For ADCs, we want to map the ADC output (0 ~ 4096) to its actual value (voltage or current).		Calibration involves finding the slope (K) and offset constant (C) of the DAC/ADC curve. The curve is linear and can be found by finding two points. For DACs, we want to map the input value to the DAC (0 ~ 4096) to the actual output value (voltage or current limits). For ADCs, we want to map the ADC output (0 ~ 4096) to its actual value (voltage or current).

	Default values are defined in {{code\|dps-model.h}} and any changes will need to be made to this file directly.		Default values are defined in {{code\|dps-model.h}} and any changes will need to be made to this file directly.

			In either case, use the spreadsheet to calculate the DAC and ADC values.

	==== DAC ====		==== DAC ====
	The DAC is the simplest to calibrate. Hit M1 and M2 buttons simultaneously to enter the calibration menu. From this menu, you can set the input DAC values for both voltage and current DACs. Alternatively, you can set the voltage DAC value by writing to register DHR12R1 at address 0x40007408 and the current DAC by writing to register DHR12R2 at address 0x40007414.		The DAC is the simplest to calibrate. Hit M1 and M2 buttons simultaneously to enter the calibration menu. From this menu, you can set the input DAC values for both voltage and current DACs. Alternatively, you can set the voltage DAC value by writing to register DHR12R1 at address 0x40007408 and the current DAC by writing to register DHR12R2 at address 0x40007414.

	We will map this voltage value to the actual voltage that is measured with a reference multimeter.		We will map this voltage value to the actual voltage that is measured with a reference multimeter.
Line 125:		Line 140:
	=== Development ===		=== Development ===
	[[File:DPSmode-Display.jpg\|thumb\|right\|DPS Mode on OpenDPS running on a DP50V5A]]		[[File:DPSmode-Display.jpg\|thumb\|right\|DPS Mode on OpenDPS running on a DP50V5A]]
	OpenDPS is opensource and is very easy to add new features ~~into however the code base currently could be cleaner~~ and the ~~UI system could be more consistent~~.		OpenDPS is opensource and is very easy to add new features. The project is relatively active and new features are being added all the time.

	==== Fonts ====		==== Fonts ====

Leo: /* Installation */

2019-10-01T05:26:11Z

Installation

← Older revision		Revision as of 05:26, 1 October 2019
Line 16:		Line 16:

	=== Installation ===		=== Installation ===
			[[File:STLink DPS Pinout.jpg\|thumb\|right\|300px]]
	You will need the following to get OpenDPS running on your power supply:		You will need the following to get OpenDPS running on your power supply:
	* A STLink or STLink clone		* A STLink or STLink clone
	* A computer with OpenOCD, ARM cross compiler (gcc-arm-none-eabi)		* A computer with OpenOCD, ARM cross compiler (gcc-arm-none-eabi)

	~~[[File:STLink DPS Pinout.jpg\|thumb\|right\|300px]]~~
	To begin, connect your STLink to the DPS power supply as per the pinout in the picture. Connect the STLink to your computer and then apply power to the DPS power supply. OpenOCD should be able to detect the device.		To begin, connect your STLink to the DPS power supply as per the pinout in the picture. Connect the STLink to your computer and then apply power to the DPS power supply. OpenOCD should be able to detect the device.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=