New Rigol 16-bit function generators DG800/900 series

[bulba99]

DG800 / DG900 do not work with USB network cards on the AX88179 chipset:
https://www.asix.com.tw/products.php?op=pItemdetail&PItemID=131;71;112
 

[bulba99]

DG800 / DG900 do not work with USB network cards on the AX88179 chipset:
https://www.asix.com.tw/products.php?op=pItemdetail&PItemID=131;71;112
 

... but the USB card on the AX88772B chipset works very well 

[bulba99]

Hi,

either I'm doing something wrong, or help mode doesn't work in FW 2.2.
I have modified FW 1.8.0.1 several times as described, and there is no downgrade.
The GEL file is loaded, the device does not restart and version 2.2 remains.

Can anyone help me?

P.S.
Can anyone write how to launch Help Mode?
I don't have three dots under the RIGOL logo, but there is a progress bar during booting.

 

[bulba99]

Hi,

either I'm doing something wrong, or help mode doesn't work in FW 2.2.
I have modified FW 1.8.0.1 several times as described, and there is no downgrade.
The GEL file is loaded, the device does not restart and version 2.2 remains.

Can anyone help me?

P.S.
Can anyone write how to launch Help Mode?
I don't have three dots under the RIGOL logo, but there is a progress bar during booting.

 

OK, I found information about FW Help Mode in another thread.
Now everything works fine.
Thank you very much to everyone who shared their knowledge.
Greetings.

[Gandalf_Sr]

So my DG811 arrived and it's Firmware Vn 00.08.00.01 which means it should be OK for the magic USB upgrade right?

I have a 'magic' USB drive that worked on the DG1022Z and when I plug that in if the USB A port on the back, I see the USB symbol appear on the top right of the display but when I go into the store function it's not clear to me whether the drive is mounted as all I can see is C:

I installed Ultra Sigma on my PC and was able to connect to the DG811 by USB but the *IDN? command seems unreliable, I can send the command but often have to click read reply then send command and then read reply before I see the response "Rigol Technologies,DG811,DG8Axxxxxxxxx,00.01.08.00.01" - often it's an error message and, so far, my :PROJ:MODE DG992 commands haven't worked. I see the command echoed on the Ultra Sigma screen when I click on [Send] but I see nothing on the DG811 and power cycling always gets me back to DG811 - some questions:

1. Is the magic USB drive different for the DG800 series than the one I made that works on the DP832?
2. Am I supposed to see a different drive letter on my DG811 after I plug in the magic USB drive?

I will try a different USB drive tomorrow but I don't have an up to date Linux machine ready. Any ideas or suggestions?

[tv84]

The DG800 USB disk has nothing to do with the DP800!!! (Where did you get that idea?)

Use my 1st upgrade post only as instructions.

And don't upgrade any FW BEFORE you get yourself a DG992 machine.

[TurboTom]

Hint: Here's the post @tv84 is talking about.

[Gandalf_Sr]

It was a massive assumption but I assumed that the Rigol code was making the same check to the drive as the DP832.  Anyway, now I know that's not the case, I have a path forward.

Thanks.

[randphysguy]

Could someone reupload the 1.08.01 official firmware?
I think it is not available through the web archive of Rigol's webpage anymore.

[Powernun]

Could someone reupload the 1.08.01 official firmware?
I think it is not available through the web archive of Rigol's webpage anymore.

It's still in the archive https://web.archive.org/web/20190820203337/https://www.rigolna.com/firmware/

[Gandalf_Sr]

So I followed the steps in this post back on page 10 and was successful.  Everything was done on a Windows 10 64 bit PC.

The following slight variations might be useful to someone.  In the HxD editor, after getting to sector 2000000, I was unable to paste the sequence 0B 0A 3B 2E 5F 4C EC BE so I just typed it in then clicked on [Save].  The drive was an older 8 GByte drive that came from a trade show with a TI logo on it, I full-formatted it as FAT32 first using Windows Explorer.  I used Rigol's Ultra Sigma code to communicate via USB - Ultra Sigma was a 500 MByte download which could be a problem for some.

In the post I linked above, thm_w talks about using Ethernet at the end but, although I have an USB-Ethernet adapter that works with the DG811 and I can communicate with the DG811 using "Telnet xx.xx.xx.xx 5555", I don't see how you can issue the SCPI command to change MODEl using the Ethernet adapter as it only seems to work on the USB Type A port on the back and that leaves no place for the magic drive.

[randphysguy]

It's still in the archive

My mistake. Thanks for pointing to it.

[maxwell3e10]

Do we know if there is any difference between v00.02.02 and v00.02.04, except for the rewritten boot-scripts (that kills the hack)?
Looks like v00.02.02 was the feature/bugfix release, while v00.02.04 is just just closing the hack for now.

I checked that v00.02.02 still has the offset bug, where the output goes negative for a few msec when it is turned on with an offset.

[Powernun]

Received the Rigol DG811 with firmware 02.04 (latest) and I can confirm that the following works:

• Downgraded the firmware to 1.08.01 as per the instructions of evgbog. The DG811 changes into a DG992 model after this.
• Updated the model to DG992 by following the instructions of tv84
• Updated the serial back to the original one by following the instructions of Ashdash
• Updated to 02.02 using the firmware by tv84
• I attempted to update to 02.04 and that reverted the model number back to DG811. So I just downgraded to 02.02.
• I also used the GOOJODOQ USB to RJ45 adapter for LAN and it works just fine. It arrived in the UK in less than 2 weeks.

Thanks all for the instructions.

[tv84]

Thanks all for the instructions.

Do you want to do a new experiment?

[Powernun]

Thanks all for the instructions.

Do you want to do a new experiment?

I am always up for experiments.

[bulba99]

Do we know if there is any difference between v00.02.02 and v00.02.04, except for the rewritten boot-scripts (that kills the hack)?
Looks like v00.02.02 was the feature/bugfix release, while v00.02.04 is just just closing the hack for now.

I checked that v00.02.02 still has the offset bug, where the output goes negative for a few msec when it is turned on with an offset.

You will have to wait for someone to share the solution for FW 02.04.
I am also currently on FW 02.02.
I tried to analyze the main app but found no solution. 

[tv84]

I tried to analyze the main app but found no solution. 

As requested, here is an image of the MTD13 of a stock DG832_fw00.01.08.00.01.

Code: [Select]

sd.xx file format:
04 bytes - model type
14 bytes - S/N encoded (if num +0x4F ; if letter +0x48)
02 bytes - CRC16  = calc_CRC16(0x1021, 0xEBCC, 0, false, false, ref buffer, start, end)

The _pubkey.tet is the brainpoolP256t1 ECC public key. It's different for each DG.

The MTD13 of a stock DG8xx_fw00.01.09.00.00 has no files !   

[ultranalog]

TV84 did it again!

The latest version of 1.08 downgrade (v5) keeps your "tweaks" to the model number when upgrading to 2.04:

Code: [Select]

 * Connected to: TCPIP::192.168.1.75::INSTR
-> *IDN?
<- (Return Count:55)
Rigol Technologies,DG992,DG8A123456789,00.01.08.00.01

-> :PROJ:MODE DG992
-> *IDN?
<- (Return Count:55)
Rigol Technologies,DG992,DG8A123456789,00.01.08.00.01


------------- flash 2.04 and reboot -----------------


 * Connected to: TCPIP::192.168.1.75::INSTR
-> *IDN?
<- (Return Count:55)
Rigol Technologies,DG992,DG8A123456789,00.02.04.00.00

Just to be clear, my serial is not 123456789 and my model according to the store invoice is not a DG992.

[tv84]

I was the enabler that helped but the true discoverer of this alternative method was bulba99. 

(when he told me the simple operation he had tried I was sure that he had solved it...)

I crafted this script so that all who were waiting this last step can finish the 2.04 upgrade.

This is a supplement to the rest of the upgrade process not a replacement!

[ultranalog]

The true discoverer of this alternative method was bulba99. 

Dziękuję serdecznie!

[bulba99]

The true discoverer of this alternative method was bulba99. 

Dziękuję serdecznie!

Proszę bardzo 

[Powernun]

I can also confirm that it worked and I now have a DG811 "upgraded" to DG992 running firmware 2.04.

For me the process of downgrading with 1.08.00.01 v5 and then upgrading to 2.04 did not work and resulted in the device becoming a DG811 again. But after using the  Finish_Upgrade_2.04 script the device reverted back to being a DG992.

Thank you bulba99 and tv84!

[netdudeuk]

I can also confirm that it worked and I now have a DG811 "upgraded" to DG992 running firmware 2.04.

For me the process of downgrading with 1.08.00.01 v5 and then upgrading to 2.04 did not work and resulted in the device becoming a DG811 again. But after using the  Finish_Upgrade_2.04 script the device reverted back to being a DG992.

Thank you bulba99 and tv84!

So a £215 instrument now works exactly like a £976 instrument ?

[Powernun]

I can also confirm that it worked and I now have a DG811 "upgraded" to DG992 running firmware 2.04.

For me the process of downgrading with 1.08.00.01 v5 and then upgrading to 2.04 did not work and resulted in the device becoming a DG811 again. But after using the  Finish_Upgrade_2.04 script the device reverted back to being a DG992.

Thank you bulba99 and tv84!

So a £215 instrument now works exactly like a £976 instrument ?

It's not exactly like that. The DG8XX instruments are calibrated up to 40MHz. Frequencies above that provide weird waveforms. I haven't personally tested that but there are a few posts discussing it in this thread. In theory, if we find out the calibration procedure/mechanism then it should be possible to calibrate DG8XX devices to the DG9XX standard.