Author Topic: Rigol DG2052 making a screenshot and possible firmware hack  (Read 5325 times)

0 Members and 1 Guest are viewing this topic.

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Rigol DG2052 making a screenshot and possible firmware hack
« on: August 02, 2021, 07:39:22 pm »
Hello,

i messed up my old Rigol DG1022 function generator by trying to update the device.

Anyway, today arrived a brand new Rigol DG2052 function generator. I like the possibility to make screenshots an a device.
Thats working great on the DG2052 in default function generator mode with a touch button in the lower right corner.
But when switching to "(Frequency) Counter" mode , the "Print" touch button to take screenshots disapears.
There is no option to take screenshots in frequency counter mode.

When pressing the "Home" button with active "Counter" button, the display switches from "Counter" mode to default mode and the frequency is shown in a single line on the bottom and one can make a screenshot in this default mode using the "Print" touch button.

I updated to the latest firmware 00.02.06.00.01. Still the same.

The DG2052 has a LXI interface. I never used this before on any device. I found out, that i can capture screenshots from my laptop remote using the LXI interface and this command:

echo ":DISPLAY:DATA? ON,OFF,PNG" | nc -w1 192.168.10.54 5555  | dd bs=1 skip=11 of=image.png

With this command, i can capture a screenshot in "Counter" mode. But after taking the screenshot, the display on the device switches from "Counter" mode to default Mode and the display is locked. I have to manually unlock it using the hardware button.

1. Is there a trick to do a screenshot using one ore more hardware buttons (like on my Keithley DMM6500, i have to press Home+Enter to take a screenshot) in "Counter" mode?

2. Is there a SCPI command i can add to prevent the screen lock when using LXI/SCPI?

3. Can i unlock the device to full DG2102 mode (like on my DS1054Z or other DG series)?

I attached some screenshots i took with the SCPI command.
« Last Edit: August 02, 2021, 08:13:07 pm by JimKnopf »
 
The following users thanked this post: Sonicsx

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #1 on: August 03, 2021, 01:54:36 pm »
I added some pictures from inside the DG2052.
Looks solid to me.
 
The following users thanked this post: TurboTom

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #2 on: August 03, 2021, 01:56:03 pm »
And some more pictures.
 
The following users thanked this post: TurboTom

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1471
  • Country: de
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #3 on: August 03, 2021, 02:04:30 pm »
Compare this to the DG800 / 900 PCB -- Different but still the same...

Jim -- may I ask you to identify U603, the QFN24 next to the PLL? It's got to be some DAC but since on mine it's lasered blank, I haven't been able to figure out what it is exactly (audio codec??). Yours appears to have all the inscriptions still intact, so this shouldn't be too difficut. In your photos, I cannot identify the inscription. It's just something to satisfy my curiosity...  ;)

Btw, great photos and thanks for posting them -- this proves what we already suspected.
« Last Edit: August 03, 2021, 02:17:10 pm by TurboTom »
 

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #4 on: August 03, 2021, 02:20:45 pm »
Has anyone here tried a full memory dump via jtag from DG800/900/2000 series??
Do i only need the bdsl file for Spartan 6?
 

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #5 on: August 03, 2021, 02:48:07 pm »
@TurboTom

U403 is a ADF 4360-7 #2006 31598 and
U603 is a 77A77DU L7322SO
 
The following users thanked this post: TurboTom

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1471
  • Country: de
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #6 on: August 03, 2021, 03:46:06 pm »
Wow, that was fast. Thanks so much! So I was completely wrong with my assumption that this chip has got to be a DAC (for generating the offset voltages and housekeeping stuff) -- there is actually a DAC very nearby on the PCB but I didn't have it on my "radar" - you know, when you're convinced it's got to be a certain way and you're not looking left and right...

This chip is actually an LMH7322SQE high speed dual comparator, and it's used to digitize the rising and falling edges of the frequency counter input signals and feeds them differentially to the FPGA. Rigol actually put quite some effort into the frequency counter section, both hardware- and software-wise. If they only wouldn't have forgotten to put a screen copy function there  :palm:. Whatsoever, a good reason to request another firmware update...  >:D

 

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #7 on: August 03, 2021, 08:18:20 pm »
I'm trying to figure out the settings for TopJTAG to dump the memory. On the mainboard i can see one 2GB Micron BGA NAND (128x16) next to the Spartan 6. On the daughter board is also the same chip and another 4GB ISSI TSOP-48 NAND.
In TopJTAG i have to set the high/low level for signal pins.
I can see the Spartan 6 with TopJTAG and TopProbe. I got the BDSL file for the Spartan 6.
Can someone guide me how to setup the level for the signal pins? There is a guide for the DG1022. Don't know how @Igor_k figured out the pin mapping. Can i just use the level that TopProbe show me as waveform? One can see if the active level is low or high.
I attached some more images.
By the way, in TopJTAG i can't see the processor on the daughter board. It show me only the Spartan 6.
 

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1471
  • Country: de
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #8 on: August 03, 2021, 10:10:46 pm »
I'm not really into software engineering and hacking stuff, so I may not quite understand what your intention is about accessing the FPGA JTAG.

If you want to access the disc partitions, there's a hack or a firmware version (IIRC) that enables the telnet client in the instrument's O/S. If you need more direct access, you can use J2 on the processor board that provides a TTL UART. You should be able to interrupt Uboot (at least on my DG8xx this was possible) and use the shell to access all the instrument's partitions, including the FPGA configuration. Copy the stuff you need to a USB thumb drive and you're ready to go.

You may want to check the DG800 / 900 thread, there's a wealth of information hidden in there.
 

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #9 on: August 04, 2021, 05:59:30 am »
The goal i try is, to have a full memory dump that i can move over when things mess up again like on my DG1022.

I started to read the thread for the DG800/900 devices partly (started from the beginning and from the end) but missed the important part (sum up on page 25). I guess serial port access will work as long as there is a working system. The update on my DG1022 failed and there was no system at all.
I just want to prevent this situation by grabbing a full memory dump.

After that, i want to switch from modell number 2052 to 2102. I don't know if the steps that work on the DG800/900 series will work on DG2000 series. Because the first firmware version for DG2000 was 2.02. Don't know if 1.08 will work on it to switch the modell number.
« Last Edit: August 04, 2021, 06:06:08 am by JimKnopf »
 

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1471
  • Country: de
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #10 on: August 04, 2021, 09:50:51 am »
Okay, now I get your point. But I'm pretty sure that the FPGA JTAG is only meant for debugging. There isn't any non-volatile information that stored inside the generator accessible from there. All the information that make the instrument tick is stored inside the Flash chip located on the CPU plug-in module. J1 (that's only used as an "alignment key" to insert the CPU module the proper way round) may contain a JTAG interface to access the Flash chip when it's still blank (when the module comes fresh from production).

Your best bet (i.e. lowest level of access to the module) with reasonable effort would be via the UART interface to interrupt the Uboot bootloader. There are four copies (partitions) of the bootloader in the Flash so the probability of all of them failing at the same time is basically only the occurance of a massive hardware fault. In which case the instrument would be rendered unusable anyway. Enter Uboot, take images of all the partitions on the flash (to a thumb drive) and you're as safe as you can be.
 
The following users thanked this post: JimKnopf

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #11 on: August 04, 2021, 05:46:34 pm »
@TurboTom Seems you're right. I figured out the pinmapping for TopProbe/TopJTAG and let it read nearly 7 hours for 128MB of empty memory.

I hooked up my Eprom programmer and read out the W25X40CLNIG Eprom. Seems my fear is baseless. The uboot system is on this Eprom. From there i can restore if needed the system. I connected my CP2102 UART serial adapter only to find out that it's either faulty or incompatible for some reasons. Used a cheap CJMCU-232H instead and tried to login.

I did not stopped the boot process. After the system was running i tried to login without entering a name/password and after that failed, i tried root/sardine_uboot combination. But did also not work.

To my surprise, the welcome screen had a funny surprise: Welcome to Rigol DG800 system  :-DD

It's still a DG2052.
« Last Edit: August 04, 2021, 07:30:01 pm by JimKnopf »
 

Offline Sonicsx

  • Newbie
  • Posts: 3
  • Country: us
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #12 on: November 27, 2022, 06:25:15 pm »
Hi there,

Nice job!! I got a question. Did you manage to hack the DG2052 to unlock 100 MHz (sine wave) and 25 MHz (square wave)? The hardware of DG2000 and DG800/900 series are almost the same:

https://www.eevblog.com/forum/testgear/new-rigol-16-bit-function-generators-dg800900-series/msg2420391/#msg2420391

Thank you!
 

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #13 on: November 27, 2022, 06:50:09 pm »
@Sonicsx I tried to flash the DG900 image provided by TV84. The hardware is a bit different. It didn't work. I wasn't able to connect via network to the device. I had a hard time getting it back to work.
 
The following users thanked this post: Sonicsx

Offline ToThePub

  • Contributor
  • Posts: 33
  • Country: au
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #14 on: December 02, 2022, 12:01:02 am »
Have you tried using the DG800 USB stick process and just trying to change the model number with the SCPI :PROJ:MODE DG2102 method?
So, no flashing firmware, just make the usb stick, send the SCPI command to see if the model changes.

Thanks..

*Edit: Some quick research and firmware between the 800/900/2000 is exactly the same (as you kind of saw in the login message!). So hopefully the USB key process might work?
« Last Edit: December 02, 2022, 05:37:08 am by ToThePub »
 

Offline elimenohpee

  • Contributor
  • Posts: 38
  • Country: us
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #15 on: January 25, 2023, 04:45:16 pm »
Have you tried using the DG800 USB stick process and just trying to change the model number with the SCPI :PROJ:MODE DG2102 method?
So, no flashing firmware, just make the usb stick, send the SCPI command to see if the model changes.

Thanks..

*Edit: Some quick research and firmware between the 800/900/2000 is exactly the same (as you kind of saw in the login message!). So hopefully the USB key process might work?
Interested in this as well!
 

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #16 on: January 26, 2023, 09:42:49 pm »
@TothePub
@elimenohpee

Today i gave it a try. But i only get an error.
What i did was:
1. I grabed a 16GB USB Stick with a 2 GB FAT32 partition on it.
2. I created a file DG800_sardinha.bin (touch DG800_sardinha.bin) and open it with with Bless Hex Editor to enter the content "0B0A3B2E5F4CECBE"
3. I checked the file: xxd DG800_sardinha.bin
   result: 00000000: 0b0a 3b2e 5f4c ecbe                      ..;._L..
4. I placed the content to the USB Stick with: dd if=DG800_sardinha.bin of=/dev/sdb1 bs=512 seek=2000000
5. I checked the USB Stick: dd if=/dev/sdb1 of=block.bin skip=2000000 count=1
   cat block.bin
   result: ;._L�Cg>uM��\�%��9�fxl�x����Nn����Q��lJ?�8
6. I put the Stick into the DG2052 and enter this commands:
    echo ":PROJ:MODE DG2102" | nc -w1 192.168.10.54 5555
    and after it failed
    echo ":PROJ:MODE DG992" | nc -w1 192.168.10.54 5555

I only got an error msg. The model number is still the same. Nothing changed.

I grabed an image from Info screen with this commands:
  echo "HCOPy:SDUMp:DATA:Format PNG" | nc -w1 192.168.10.54 5555
  echo ":DISPLAY:DATA? 0" | nc -w1 192.168.10.54 5555  | dd bs=1 skip=11 of=image_2.png

An image of the error msg is attached.

Edit:
To create such a USB Stick, it's easier to do it like this:
mount /dev/sdb1
mkfs.vfat -F 32 /dev/sdb1
echo -n -e \\x0B\\x0A\\x3B\\x2E\\x5F\\x4C\\xEC\\xBE | dd of=/dev/sdb1 bs=512 seek=2000000

Check with:
dd if=/dev/sdb1 skip=2000000 count=1|xxd -l8
      output is:   1+0 Datensätze ein
            1+0 Datensätze aus
            00000000: 0b0a 3b2e 5f4c ecbe                      ..;._L..
            512 Bytes kopiert, 5,6097e-05 s, 9,1 MB/s
« Last Edit: January 27, 2023, 05:41:11 pm by JimKnopf »
 
The following users thanked this post: elimenohpee

Offline ToThePub

  • Contributor
  • Posts: 33
  • Country: au
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #17 on: January 26, 2023, 11:31:37 pm »
Humm... Dam it... Many thanks for trying. Didn't think it would work as that method changed in the latest firmware which its running, but worth a try.
Will need a different method it seems.
 

Offline elimenohpee

  • Contributor
  • Posts: 38
  • Country: us
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #18 on: January 27, 2023, 01:09:59 pm »
@TothePub
@elimenohpee

Today i gave it a try. But i only get an error.
What i did was:
1. I grabed a 16GB USB Stick with a 2 GB FAT32 partition on it.
2. I created a file DG800_sardinha.bin (touch DG800_sardinha.bin) and open it with with Bless Hex Editor to enter the content "0B0A3B2E5F4CECBE"
3. I checked the file: xxd DG800_sardinha.bin
   result: 00000000: 0b0a 3b2e 5f4c ecbe                      ..;._L..
4. I placed the content to the USB Stick with: dd if=DG800_sardinha.bin of=/dev/sdb1 bs=512 seek=2000000
5. I checked the USB Stick: dd if=/dev/sdb1 of=block.bin skip=2000000 count=1
   cat block.bin
   result: ;._L�Cg>uM��\�%��9�fxl�x����Nn����Q��lJ?�8
6. I put the Stick into the DG2052 and enter this commands:
    echo ":PROJ:MODE DG2102" | nc -w1 192.168.10.54 5555
    and after it failed
    echo ":PROJ:MODE DG992" | nc -w1 192.168.10.54 5555

I only got an error msg. The model number is still the same. Nothing changed.

I grabed an image from Info screen with this commands:
  echo "HCOPy:SDUMp:DATA:Format PNG" | nc -w1 192.168.10.54 5555
  echo ":DISPLAY:DATA? 0" | nc -w1 192.168.10.54 5555  | dd bs=1 skip=11 of=image_2.png

An image of the error msg is attached.
bummer, thanks for trying.  I was just about to start this but you saved me the effort.
 

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #19 on: January 28, 2023, 05:33:23 pm »
@TurboTom
How can i write to usb device in uboot?
Steps are not well documented and rarely used in this forum.

I already grabbed the content from SPI eprom. In this eprom-content is the uboot password in plain text "sardine_uboot".
Now i want (just for exercise) read the sardine_uboot.img from nand and write it to a USB Stick.
I plugged in a USB Stick, logged into uboot, and did:

usb start
printenv
           fat_uboot_file=sardine-uboot.img
           fdtaddr=0x88000000
           filesize=ae0000
nand read 0x88000000 0x0 0xae0000
           NAND read: device 0 offset 0x0, size 0xae0000
           11403264 bytes read: OK
save usb 0:1 0x88000000 sardine-uboot.img 0xae0000

But i only get an error msg: ** Unable to write file sardine-uboot.img ** and fatls usb 0:1 show me an empty USB Stick "0 file(s), 0 dir(s)"

I read in some other threads that newer devices are able to use tftp to send files. The DG2052 only has tftpboot to grab files from a server.
How can i save the nand content and maybe the SPI eprom content to a usb device using UART/uboot?
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3345
  • Country: pt
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #20 on: January 28, 2023, 07:51:06 pm »
How can i write to usb device in uboot?
Steps are not well documented and rarely used in this forum.

That depends on the uboot implementation. It's not a generic thing.

Have you looked at all the commands available in uboot?

Alternatively, you can always dump your mem contents to screen (in hex form, for example) and log it in your terminal client. Then, in the PC, you just parse the output and create a bin file. I've done it dozens of times.

Many times uboot USB can't see the partitions and you only see the device. In that case, you must consider writing/reading to the direct raw sectors of the USB device.
 

Offline Njk

  • Frequent Contributor
  • **
  • Posts: 348
  • Country: ru
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #21 on: May 26, 2023, 07:14:18 pm »
The instrument integrates the frequency counter. Similar to that in DG800/900 series, it has the two input couplings, DC and AC. There is at least one confirmed report in the sister thread about the AC coupling issue. When coupling is set to "AC", the center pin of the BNC input connector of the counter is internally tied to -5.3 V voltage level by a high ohm resistor https://www.eevblog.com/forum/testgear/new-rigol-16-bit-function-generators-dg800900-series/msg3591372/#msg3591372. That seems unusual and I wonder if DG2000 is also affected.

According to Rigol, both DG2000 and DG900 series uses essentially similar HW. But let's look at the frequency counter areas of the DG2000 and DG800 PCBs (attached). The difference is not only in the layouts. In both the designs, the input signal from the connector is first routed to the clamping diode array (a SOT-23 part with JY marking, likely BAV199). Concerning the DC path, the signal is then passes through the resistor of 88 (or 66) Ohm. Then there is a switch that is likely related to the AC/DC coupling. That's where the difference is.

In the DG800, the switch is made of the two SOT-23 parts (with 61U and 6K markings, likely old Fairchild JFETs MMBF5461 and MMBF4392 respectively. Perhaps -5.3 V is a bias voltage for the JFETs, so user must bring his own cap for AC coupling). While in the DG2000, the switch is made of single big part, the marking of which is difficult to read. So the analog front ends are apparently different, and the reason is not clear.

Perhaps it's a minor change because of the parts availability. DG2000 was designed later, and in 2019-2020 both MMBF5461 and MMBF4392 were declared obsolete by OnSemi. While MMBF4392 was replaced with MMBF4392L, no substitution was offered for MMBF5461, so Rigol was forced to change the design. The chances are a later DG800/900 HW revisions were also updated accordingly (pure speculation). That's why it's interesting if the AC coupling issue is related only to the old design or not.

All in all, there is a lot of components in the counter PCB area. Dozens of discrete components and 8 op-amps in total. No idea if every the op-amp is related to the frequency counter, but there is also one 1P8T analog switch (HC4051) the purpose of which is not clear. There is only one that part so it's unlikely it's used elsewhere (as the generator has two channels). It's quite complex electrical arrangement for the frequency counter of unspecified accuracy. Moreover, there is a dedicated 16-bit DAC and two fast comparators. With one more DAC, it could be possible to implement two independent triggers, like in more serious counters, allowing to measure e.g. a pulse edge time. But it seems there are too many stoppers in the SW department.

P.S. JimKnopf, thanks for the hi-res PCB images. Hope you're doing well.
 
The following users thanked this post: thm_w

Offline JimKnopfTopic starter

  • Regular Contributor
  • *
  • Posts: 205
  • Country: 00
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #22 on: May 29, 2023, 09:49:09 am »
@NjK

I just tested the counter voltage in DC and AC coupling mode.
I didn't measure negative voltage like -5,x V on center pin. There is no difference between DC and AC coupling.
The AC measurement showing me some normal fluctuating voltage.

I grabbed some scrrenshots from linux terminal using
  echo "HCOPy:SDUMp:DATA:Format PNG" | nc -w1 192.168.10.54 5555
  echo ":DISPLAY:DATA? 0" | nc -w1 192.168.10.54 5555  | dd bs=1 skip=11 of=counter_1.png (or whatever name you want)
  (don't forget to unlock the screen after using SCPI commands by pressing Shift and then Arb|Help/Local button on DG2052).

I'm running Software Version 00.02.06.00.01 on my DG2052.

Activating the counter disables Output 2 (normal behavior, i remember that i read something in the manual about that).
The Counter button LED is flashing when activated instead of the permanent glow like Output 1 and 2 button.

 
« Last Edit: May 29, 2023, 10:13:47 am by JimKnopf »
 

Online TurboTom

  • Super Contributor
  • ***
  • Posts: 1471
  • Country: de
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #23 on: May 29, 2023, 10:46:34 am »
The signal path of the counter circuitry is basically only rounted through discretes (except for final digitization that is). There's a jfet input and some level shifting taking place. @Njk is correct --  the AC/DC switching is arranged diffenetly in the two models, a look at Rigol's most inexpensive oscilloscopes helps here: The SO4 component used in the DG2000 circuitry is a Cosmo solid state (PhotoMOS) relay, used to short out the coupling cap. Since apparently a perfect galvanic isolation from control to signal paths isn't required (which may affect signal fidelity), the older circuitry utilizes here a cheaper, discrete approach.

The TL072 that's apparently routed in the counter's signal path is most likely processing the DC/LF channel of the input amplifier and maybe providing some bias voltages. The signal is then routed through the relay (later more on that) to the LMH7322 comparator (QFN24 with the markings lasered off in the DG800 version) that finally digitizes the counter input signal and feeds it differentially to the FPGA.

The small TSOP8 (DAC8560), the TL072 and TL074 opamps and the 4051 analog multiplexer (sample&hold) are just used to provide several high-resolution (16 bit) analog control voltages to the rest of the circuitry (channel offsets, trigger levels and who knows what). This circuitry block can be found in many Rigol and Siglent AWGs with almost exactly the same components, and even DSOs feature this circuitry.

One detail that's most peculiar and not 100% clear to me is why the AWG pre-driver outputs are routed back to the analog comparator'inputs (via 499R - 68A marking) and (probably) 10kR pullups/grounding resistors. This feedback signal is multiplexed via the relay with the counter input channel, and that's the reason the DG800/900/2000 series of AWGs unfortunately loses one of its AWG channels whenever the counter is enabled. The additionally required fast comparator fell victim to the "bean counters" in these economy AWGs...  Maybe the AWG signal feedback is somewhat related to propagation delay compensation/deskew of the channels?
« Last Edit: May 29, 2023, 10:51:22 am by TurboTom »
 

Offline Njk

  • Frequent Contributor
  • **
  • Posts: 348
  • Country: ru
Re: Rigol DG2052 making a screenshot and possible firmware hack
« Reply #24 on: May 30, 2023, 02:23:34 pm »
I didn't measure negative voltage like -5,x V on center pin. There is no difference between DC and AC coupling.
So another HW difference between DG2000 and DG800/900 is finally revealed. BTW, it seems in DG800 the negative bias produces the two effects. First, it can be measured on the center pin. Second, it affects the comparator. Looks like with AC coupling, the virtual zero level is also biased down to at least -2.5 V and the counter shows nothing unless the trigger level is set to -2.5 V. Even after that, the sensitivity is much worse than with DC coupling, suggesting the virtual ground is actually biased to a deeper minus level, to -5V. Looks like AC coupling is implemented just to check the box. It must be better in DG2000, I presume.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf