--- RD60062_V1.28.3.bin ---
+ Added setting for current cutoff in battery charger mode.
+ Added setting for batt temp. cutoff in battery charger mode.
+ Added Battery Charger Layout
+ Added Setting to skip keypad lock when connect with software.
+ |MEM| + |.| — now used to reset Wh, Ah
gif (from simulator)
The source code would fit really well on github, if it isn't already and if you have time/want to. I'm sure once people have a base they would happily contribute to it. Really cool project overall! As for the keypad, any chance you could patch the firmware to enable the keypad while communicating with the computer? Or would something bad happen? Thanks!
I can't post sources... it contains private encryption keys to encrypt firmware,
I don't think that developers will be happy to see it in public...
As for the keypad, any chance you could patch the firmware to enable the keypad while communicating with the computer?
Done
--- RD60062_V1.32.1.bin ---
* Updated to version V1.32
* Bugfixes
+ while editing option "СutOff current", |
<| and |
>| can be used to select the step (1\10\100).
Is it possible to flash the firmware from Linux?
--- RD60062_V1.32.1.bin ---
* Updated to version V1.32
* Bugfixes
+ while editing option "СutOff current", |<| and |>| can be used to select the step (1\10\100).
Thank you, great job done!
I've quickly tested both 1.28 and 1.32, no bugs to write about so far (maybe later...
)
...
Excellent work.
Can you now fix that display layout so it's readable ? The UI definitely needs space inbetween the 3 main lines (V / A / W), 50% of the line height is a good value, and smaller characters.
Can you now fix that display layout so it's readable ? The UI definitely needs space inbetween the 3 main lines (V / A / W), 50% of the line height is a good value, and smaller characters.
I don't understand what exactly you want to get.
50% of the line height is 30px (for large digits), notice menu items is 24px,
what for you want so large spaces?
Now large numbers is 32x64px ('.' (dot) is a half width, ie 16x64),
But resolution of display is too small, so developers draw this lines at 0,60,120 (so 4px overlapped).
If anyone have any interesting ideas about layouts let me know.
Better if you will make a sample image (for example in Paint.NET)
One other thing I heard some people mention in the review of the original product is that the color coding doesn't really mean anything, so it would be cool if you could fix that!
What do you mean "color coding"?
What exactly need to fix?
Oh looking back at the EEVBlog review, it was actually him who said this, at 10 minutes in. He says, "The colour coding doesn't make much sense e.g Purple for input voltage and output power." Basically the coloring of different things on the menu seem a tad random. It's really isn't a huge deal, though, more of a stylistic thing I suppose. I installed the latest version of your custom firmware and the units for each of the outputs seems to be below the number, for example the V doesn't align with the numbers, but it's slightly below. I don't know if this was on purpose or not and it's stylistic, so it doesn't matter that much.
Can you now fix that display layout so it's readable ? The UI definitely needs space inbetween the 3 main lines (V / A / W), 50% of the line height is a good value, and smaller characters.
I don't understand what exactly you want to get.
50% of the line height is 30px (for large digits), notice menu items is 24px,
what for you want so large spaces?
Now large numbers is 32x64px ('.' (dot) is a half width, ie 16x64),
But resolution of display is too small, so developers draw this lines at 0,60,120 (so 4px overlapped).
If anyone have any interesting ideas about layouts let me know.
Better if you will make a sample image (for example in Paint.NET)
The reason I am asking for it is I see it as the biggest problem in terms of user interface; in the original UI the lines are too close together and difficult to read. Line spacing of 150% (character height + 50% space) is close to the optimal value. See here more details:
https://www.justinmind.com/blog/best-ux-practices-for-line-spacing/I think 48x24 characters at the same 0, 60, 120 lines would make this much easier to read. See quick attempt in Paint:
...in the original UI the lines are too close together and difficult to read.
I think 48x24 characters at the same 0, 60, 120 lines would make this much easier to read.
Not many will like it, added as an option.
Is it OK?
--- RD60062_V1.32.2.bin ---
* Bugfixes
+ Option "Digits Style", can select style for large digits (32x64, 12x24, 7-Seg)
+ Decreased minimum battery voltage from 900mV to 300mV
Incredible work from Unisoft.
I agree the smaller font does not help with readability, the screen is so small already so a large font works best, at least for me.
Incredible work from Unisoft.
I agree, the only thing I can think of that this is missing now is wifi!
As for the smaller text, it's really down to personal preference. I like the larger text because it's easier to see, but the smaller text diffidently is nicer on the eyes. It really doesn't hurt to have as an option either way
--- RD60062_V1.32.3.bin ---
+ Support WIFI
* Bugfixes
The Wifi connection doesn't seem to be working for me. Following the steps from RDTech, once the app connects to the RD6006, the RD6006 seem to skip connecting to the network and continues to the main screen. Is this a bug or am I doing something wrong?
Not the type of PSU I am interested in, however, I just got an email about the RD6012 which has a 12A current limit. It is on sale for $53 at Banggood, thought I would share it with the community in case you are in the market for this type of device.
I have nothing to do with the commerce site or the product.
Any chance getting the TTL (interface) mode working? Front USB connector is less than ideal (and doesn't appear to be isolated?), so ability to connect isolated USB to TTL-serial adapter to the connector at the back (for the WiFi module) would be really nice.
Any chance getting the TTL (interface) mode working? Front USB connector is less than ideal (and doesn't appear to be isolated?), so ability to connect isolated USB to TTL-serial adapter to the connector at the back (for the WiFi module) would be really nice.
TTL should work.
Protocol (Modbus) is the same for all interfaces...
USB interface is complete isolated!!! This IC is used (p122U31):
https://datasheet.lcsc.com/szlcsc/2001070603_2Pai-Semi-p122M31_C471594.pdf
FWIW, there was a video where something metallic slipped under/near the usb outside ground and the negative terminal and ever since, people have assumed it's not isolated..
FWIW, there was a video where something metallic slipped under/near the usb outside ground and the negative terminal and ever since, people have assumed it's not isolated..
I can’t even imagine how he managed to burn the connector.
But this is certainly not because of what he is talking about.
USB is completely isolated and has no common ground.
FWIW, there was a video where something metallic slipped under/near the usb outside ground and the negative terminal and ever since, people have assumed it's not isolated..
I can’t even imagine how he managed to burn the connector.
But this is certainly not because of what he is talking about.
USB is completely isolated and has no common ground.
Earlier in the thread, @BlackFX confirms the cause as being a mounting screw on the SMPS shorting the +VE output to the chassis ground.
Seems to imply that the power supply front panel -VE was at a potential of -58v.
At least thats what I understood...
FWIW, there was a video where something metallic slipped under/near the usb outside ground and the negative terminal and ever since, people have assumed it's not isolated..
I can’t even imagine how he managed to burn the connector.
But this is certainly not because of what he is talking about.
USB is completely isolated and has no common ground.
Earlier in the thread, @BlackFX confirms the cause as being a mounting screw on the SMPS shorting the +VE output to the chassis ground.
Seems to imply that the power supply front panel -VE was at a potential of -58v.
At least thats what I understood...
Spot on, there is a screw that fouls the main output cap on the SMPS I am using. You will see I later repaired the damage.
This guy had the same issue but discovered it before any magic smoke
Any chance getting the TTL (interface) mode working? Front USB connector is less than ideal (and doesn't appear to be isolated?), so ability to connect isolated USB to TTL-serial adapter to the connector at the back (for the WiFi module) would be really nice.
TTL should work.
Protocol (Modbus) is the same for all interfaces...
There seems to be some kind of bug, if interface is changed to "TTL" it works, but after unit has been powered off and on again, unit doesn't respond to modbus queries anymore...
However, unit will start responding after one goes to the communication settings and to the interface menu option (no need to actually change the value...seems to be enough just scroll down to the menu option and then exit out from the menu....