Need help hacking DP832 for multicolour option.

[firstcolle]

Many many thanks!!!
DP832 hacked to DP832A
DG1022z hacked to DG1062z

i only miss the 16M option, i can't find the procedure in the thread.

[tv84]

Edit: Of course I could try using :SYSTem:TYPE DM3068    As this would be the natural command, and we know :SYSTem:TYPE? works to find the Model Type.  It seems like it may be low risk? ?   But I don't want to brick my unit.

Edit 2: I used  :SYSTem:TYPE DM3068 plus various combinations of the command structure and nothing worked to do anything.  The plus side is that all is still OK with my DM3058E. So no 6 1/2 digits for it, but its not bricked either.

"I won't brick it..." 5 sec later "Let's do it.."

Well, I think any of those special "set" commands (as always) only work with a vendor USB disk inserted.

[tv84]

i only miss the 16M option, i can't find the procedure in the thread.

The procedure is in the previous msg (to yours)!

[ted572]

Edit: Of course I could try using :SYSTem:TYPE DM3068    As this would be the natural command, and we know :SYSTem:TYPE? works to find the Model Type.  It seems like it may be low risk? ?   But I don't want to brick my unit.

Edit 2: I used  :SYSTem:TYPE DM3068 plus various combinations of the command structure and nothing worked to do anything.  The plus side is that all is still OK with my DM3058E. So no 6 1/2 digits for it, but its not bricked either.

"I won't brick it..." 5 sec later "Let's do it.."

Well, I think any of those special "set" commands (as always) only work with a vendor USB disk inserted.

Hello TV84:  Ok, I'm ready to do it, but what should I use for a 'Vendor USB Disk'?  Can I get one at Walmart, or Amazon?  Hi Hi, Ted
PS  : BTW Hi Hi is similar to Ha Ha.

Edit:  I'm not worried about bricking it as the DM3058 and E version firmware are the same package.  Whereas the DM3068 is apparently different(?).  Although I just noticed and the DM3058/E and DM3068 LDR firmware files are same size.  So that is interesting, maybe at one time the DM3058 was going to be also be used for the DM3068 hardware platform.  Anyway I'm looking forward to going ahead on changing the Model Name, although I don't necessarily have high expectations.

[ted572]

I added color coded labels to my DM832 as part of its conversion to a DM832A.  Unfortunately I used the camera's Flash that ended up washing out the colors, although the actual label colors are quite well matched to those of the LCD's Classic Display.

Edit:  New replacement photo.  I added Color to the three Channel selection buttons.  Had to use Flash again because the ambient lighting wasn't sufficient.

Last Edit: Added information about Using Sharpie Permanent Color Markers for adding LCD matching colors.

The colors are from Sharpie Permanent Color Markers (fine tip). You will have go to where they have a huge selection of different color markers, or otherwise get a large (qty 24) assortment package that you can select your particular colors from (confirm that your colors are included). The DC Output labels can be numbered using Dry-Transfer Decals. I had some old miscellaneous VHF Tape labels that simplified things for me.

My channel Button colors, and DC Output number label colors match the LCD display colors very well. You do have to coat the Buttons several times over a couple of days to get the markers to stain the buttons sufficiently, and the results look great. They will basically be permanent, although you can use a solvent on them to lighten the color if required as you go along. You can use gasoline as a solvent (Suggestion! Stay away from open flames). Gasoline will not affect the number label on the buttons, and it is also safe to use on the front panel's surface.  You may prefer using a less volatile solvent, but this works well for me. 

[Gandalf_Sr]

Hello TV84:  Ok, I'm ready to do it, but what should I use for a 'Vendor USB Disk'?  Can I get one at Walmart, or Amazon?  Hi Hi, Ted

You make it yourself, it's just a USB drive formatted in a particular way with a specific file on it.  Use any old or new USB drive and follow the instructions in this post which is all of 1 page back.

[Gandalf_Sr]

I added color coded labels to my DM832 as part of its conversion to a DM832A.  Unfortunately I used the camera's Flash that ended up washing out the colors, although the actual label colors are quite well matched to those of the LCD's Classic Display.

Sweet! Where did you get those labels from?

[ted572]

I added color coded labels to my DM832 as part of its conversion to a DM832A.  Unfortunately I used the camera's Flash that ended up washing out the colors, although the actual label colors are quite well matched to those of the LCD's Classic Display.

Sweet! Where did you get those labels from?https://www.eevblog.com/forum/Smileys/default/facepalm.gif

Hello Gandalf:  For information on how I added Labels and Color to my PD832 to DP832A conversion Front Panel please see ->    https://www.eevblog.com/forum/testgear/need-help-hacking-dp832-for-multicolour-option/msg2540175/#msg2540175

Thanks for the info on the USB Image file that you provided a path to for me.  It hasn't helped, but I don't know if the USB Disk Image is the problem.  Or if it is just that the hack for the DM3058E doesn't do anything, which I kind of expected before (that it wouldn't work).  I have to play with this some more, and also see if I can reformat (low level of course) the USB drive back to its original 256 GB.  Right now its total capacity is at about 31 MB.  So the image must have been 31 MB, although the size of the image file itself was around 16.4 MB.  I know that this is what happens when you transfer a disk image file to a USB drive, so I'm not concerned.  But as I said I don't know if the image process worked properly yet.

Thanks for your assistance, Ted

Edit: Added Link for information about using Sharpie Permanent Color Markers for adding LCD matching colors, etc, and nothing requires disassembly.

[Gandalf_Sr]

@ted572
You're welcome.  If the USB drive reads and has a single file on it then it's almost certainly good and not the reason things aren't working for you.  Mine worked in a DG1022Z and DP832.  If you issue the model command via tenet and get a message like "unrecognized command" on the screen on the screen of device you're trying to upgrade but do get responses to *IDN? then it's probably a bad USB drive - maybe one that the device doesn't like for some reason.  However, a drive you created from the disk image is more likely to work than one you created yourself by formatting and copying the file to the drive.

I don't know if it's possible to upgrade a DM3058E using the USB method, has anyone else done that?

[TurboTom]

The DM3068 DMM's digital circuitry is built around an Analog Devices Blackfin DSP, I assume it's a similar situation with the DM3058(E). It appears that only Rigol's more recent gear that's based on the Freescale/NXP i.MX or Texas Instrument Sitara ARM Core SOCs can be accessed via the "Magic Stick" method. So your attempts to "talk to" your DM3058E may be futile... 

[ted572]

Thank you Gandalf and Tom for your comments.  Yes I believe that the USB SCPI commands aren't going change this to a DM3068.  I never had high expectations for it, but I wanted to give it a shot.  The DM3058 firmware wold need to modified to do the job of getting 6 1/2 digit display, and that is beyond my capability.

Side note: I send the Rigol SCPI commands via USB using 'Messinstrumente' (Measuring instruments - program for data transfer and control) which is very easy and always works for me.  You enter the SCPI command in the command window and then press Send/Receive.  The command goes out and a second later you see the results as received data.  A good test to see that all is working OK is to send *IDN?, and you should see a reply (Receive Data) with your Model Number and S/N.  Other commands may reply with something like 'Command Executed OK'.  If the command is invalid the program will simply time out 'without a reply', or 'Invalid Command', etc. in 3 - 6 seconds.

I just wondered why I didn't read about anyone else using this for the DP832 to DP832A Mod?  There is a USB type B connector on the back of the unit for this, in addition to the USB type A connector for the USB drive.  It seemed to me that everyone was using LAN or RS232 when the USB is so easy.

Rigol Ultra Sigma would also work for sending USB SCPI commands, but at the expense of adding about 500 GB to your computer, and not being able to uninstall it ALL without manually searching for left over Files and Registry entries.  Even using the more complete Uninstallers such as 'Revo Uninstaller', they won't catch everything, as there will still be well over ten items that won't be automatically cleaned out.

PS:  'Messinstrumente' is a portable program that doesn't get installed on your computer.  You can simply run it from a USB drive, the Desk Top, etc.

Edit: By request, here is a English link to 'Messinstrumente' (Measuring instruments - program for data transfer and control) ->  https://translate.google.com/translate?hl=en&sl=de&u=http://peter.dreisiebner.at/messinstrumente/index.htm

[das_strobel]

Ok, 1-2 weeks ago i've modified riglol 1.03d for DG1000Z generation/calculation

here is a full source code:
...

I tried to make use of this code. I downloaded the sources from http://gotroot.ca/rigol/riglol/ and replaced the original riglol.c with your code. It didn't compile first, because all the #includes where missing. I added them and it compiled. But still no cigar. The compiled executable runs in general (putting out the help text etc.) but if I try to generate the 16MB option key it just hangs without any message. I can kill the program with Ctrl-C, though.

I did all that using Ubuntu 18.04 running in the native Linux environment on Win10.

Any idea?

[firstcolle]

i tried to compile with c compiler but it give me some errors..
wich compiler should i use?

i only miss the 16M option, i can't find the procedure in the thread.

The procedure is in the previous msg (to yours)!

[tv84]

i tried to compile with c compiler but it give me some errors..
wich compiler should i use?

That's a tricky question because the riglol / rigup source codes have some bugs (in terms buffer overruns, unallocated pointers, 32 bits vs 64 bits compilation, etc...). Most guys that are able to compile them do some corrections in order to accomplish it.

If all was good, any compiler should work.

For riglol try compilation in 32 bits or 64 bits, to start.

[mike47203]

Starec;

Thanks so much for the code you posted for the modified riglol. I was able to make that work. I did find that one line was missing that caused the program to hang. In the ecssign function at line 41 in your post "instr(a, curve_a)" is missing. Once I added that, it work perfectly. Much appreciated.

It seems that may be the problem other people were having. If you diff the posted code against the original riglol.c it is apparent what needs to be changed. I had no trouble compiling and running in Linux. Can't say if it works for any other platform.

[das_strobel]

It seems that may be the problem other people were having. If you diff the posted code against the original riglol.c it is apparent what needs to be changed. I had no trouble compiling and running in Linux. Can't say if it works for any other platform.

Thanks, mike47203! This did the trick also for me. I changed the line, compiled again on my Ubuntu on WSL on Win10, and voila the program runs and the generated key works.

[starec]

In the ecssign function at line 41 in your post "instr(a, curve_a)" is missing. Once I added that, it work perfectly. Much appreciated.

Yes indeed,
i wrote my own application in Windows and was all in there. This copied code was from riglol source itself. I only added my changes and no checked the remaining code so i didn't notice the missing line - my fault. However as tv84 been noted the riglol source codes have some bugs. I'd added (at least) releasing of acquired memory in the fn ecssign as follows

Code: [Select]

mirkill(a);
mirkill(b);
mirkill(p);
mirkill(q);
mirkill(Gx);
mirkill(Gy);
mirkill(d);
mirkill(k);
mirkill(r);
mirkill(s);
mirkill(k1);
mirkill(zero);
mirkill(f1);
mirkill(f2);
mirkill(f3);
mirkill(f4);
mirkill(hash);
epoint_free(G);
epoint_free(kG);
mirexit();


[tv84]

I'd added (at least) releasing of acquired memory in the fn ecssign as follows

Yep, even this simple thing is missing...  When one runs a single time, less important but if we start reusing, etc, etc all type of weird things start to happen.

Of course the way mem is allocated and the var types/casts are the biggest problem.

riglol is more polished, rigup is much worse. Nonetheless the authors deserve all the credits for creating those tools.

[Marc M.]

... The USB drive must be formatted as FAT, not FAT32 or exFAT. On...

For some reason this isn't always the case.  I just grabbed a brand new 8Gb pre-formatted FAT32 card (older SanDisk HC1), stuck the file on it and powered the supply up with the USB adapter plugged in.  I connected to a Windows laptop with UltraSigma installed and sent IDN to confirm the connection, then issued the :PROJ.... command.  I think it spit out an error but I saw an OK at the bottom so I went ahead and power cycled the supply.  It came up in not-so glorious color.  Arrggh, the pale color pallet of grey, white, and light blues is terrible, but I do like the 3 color classic main display. 

Aesthetics aside, I had to jump thru some hoops before I got the above result.  I bought an early supply with the original hardware and firmware (1.04 maybe?) on it.  When I tried it on that firmware it flipped me off with an error.  I remembered there was an issue with newer firmware and hacked options which was no reversible so I never bothered to update it.  Since this hack changes it to an A model, all options are  turned on automatically so any risk to previously hacked options won't matter.  I updated the boot loader, then the firmware, and finally the analogs with the latest revision I found somewhere on Rigol's site.  After that was complete, I reconnected, issued the PROJ command and it worked without a problem.  So SD cards are just hit/miss as I violated both the 2 to 4 gig limit and the no FAT32 rules. YMWV but I'd try whatever card you have at hand.

On my already way too long, I'll be dead long before half of it gets done To Do list, I plan on pulling the front panel off and changing out the green LEDs behind the channel enable buttons to reflect the channel color to help differentiate them (at least while they're turned on). Anyone happen to know what size they are?  I voided my warranty long ago dealing with the overheating regulator issue, and I've probably had it longer than 3 years anyway.  Rigol could make a killing selling replacement 832A buttons!

[Gandalf_Sr]

Changing the LEDs to match the channel colors is a great idea.  I found that my drive was formatted to FAT worked so I think that FAT32 is not absolutely essential.

[tv84]

These equipments use Linux filesystems so all 3 FAT types should work when we are reading/writing files.

The only limitation is that some Rigol equipments do some USB vendor disk verification (when one wants to do the "upgrades") with direct disk access functions and those should match a specific FAT type or may end up in unpredictable results.

[Marc M.]

A special thanks again to everybody in the EEVBlog Community who contributed to all the reverse engineering efforts within the Rigol product range which allowed me to maximize the potential of my DSA815, DS2072, and now DP832.  My only regret was buying a DG4162 instead of a 4062  .  You guys rock!

I said screw it, stayed up late and swapped out the LED's which were 0806's.  I didn't have any in purple, so I stuck a red one in for now.  Got some purple and some hopefully yellower yellow LEDs heading this way from China.  All I can say is Wow! what a difference.  I was worried the replacements wouldn't be bright enough but I was wrong, they are quite a bit brighter than the stock green ones.  I'm so happy with the results, one of these days I'm going to pull my Rigol DS2072 apart and replace the front panel LEDs on that because the green ones on that are barely visible.

I was also surprised to see provisions for a set of 4th channel buttons both on the PCB and the molding in the front case.  I had sniffed around looking for a photo of the front keyboard to determine the LED size ahead of time but couldn't find one.  Dave didn't pull the front board when he did his teardown either so here's a shot of mine for the curious.

[1anX]

Marc M where are you getting your smd 0806 leds from?
Looks great with the coloured leds and if cheap from China I think I will do the same to mine just for fun!

[ted572]

DP800 Firmware 16 (re. DP832/A, etc.) initial 00.01.16.00.00 was a Beta version, although the current version 00.01.16.00.02 (2019-1-31) is a official released version.

Edit: Added applicable improvements.
     
    Support for USB-GPIB
    Fixed *OPT? command
    Fixed cursor settings
    Fixed LAN Library (network stability)
    Other. . . .

[Marc M.]

... where are you getting your smd 0806 leds from?...

I can't say for sure, had them for several years.  My guess is either Fleabay or AliExpress, I think I just bought an assortment of 5 colors for stock.  The purpler red and hopefully yellower yellow LEDs I ordered for this are coming from Fleabay.