Need full firmware (full dump flash) oscilloscope Atten ADS 1062CML

[alexitaly]

Tell me the responses to the SCPI commands.

I'm trying and i've little driver problems.

With EasyScopeX ?
Please see attached tips for correcting them.

please wait, it's another speech and we will gladly discuss it later.

Actually, i'm using NI driver: I've just reinstalled them, before I've used Keysight IO libraries.

[alexitaly]

Tell me the responses to the SCPI commands.

I can't find the commands that you want in this document:

https://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/ProgrammingGuide_forSDS-1-1.pdf

Do you need other special commands?

I think that, if you can, you have to change also product type in ATTEN fw with product_ID=79 (siglent): from ADS1102CAL to SDS1102CNL... what do you think?
Thanks!

[tv84]

Tell me the responses to the SCPI commands.

I can't find the commands that you want in this document:

https://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/ProgrammingGuide_forSDS-1-1.pdf

Do you need other special commands?

I think that, if you can, you have to change also product type in ATTEN fw with product_ID=79 (siglent): from ADS1102CAL to SDS1102CNL... what do you think?
Thanks!

You can't find those commands because Siglent doesn't want to publicize them. They are internal commands.

About the Prod_ID: I included Atten FW in 79 and 80 versions. If that was the filter, it would work. There is another check and I think we need a memdump to find out.

[alexitaly]

Tell me the responses to the SCPI commands.

I can't find the commands that you want in this document:

https://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/ProgrammingGuide_forSDS-1-1.pdf

Do you need other special commands?

I think that, if you can, you have to change also product type in ATTEN fw with product_ID=79 (siglent): from ADS1102CAL to SDS1102CNL... what do you think?
Thanks!

You can't find those commands because Siglent doesn't want to publicize them. They are internal commands.

About the Prod_ID: I included Atten FW in 79 and 80 versions. If that was the filter, it would work. There is another check and I think we need a memdump to find out.

Hi tv84.

Excuse me, i think I expressed myself wrong.
I've tried both version (79 and 80 versions) of your Atten FW.
But the "79" version have PRODUCT_ID field modified, not PRODUCT_TYPE too, or am i wrong?
If i'm not saying wrong things, can you try to modify also "PRODUCT_TYPE" field in "79" version please?

Tell me the responses to the SCPI commands.

You can see the responses in the images attached...

THANKS!

[tv84]

Alex,

See here a parsing of the Atten .ADS FW:

Code: [Select]

ATTEN_ADS1000CAL_V100R003B01D01P31R16.ADS  /  CRC32: 3195554C
File Header Size: 00000048
00000000 - File Checksum: F55C9872 [00000004-0018773E] (with only the File Header decrypted)  CKSM OK
00000004 - File Size: 001876F7 (without 0x48 bytes of the File Header)
00000008 - # Blocks: 0000935B
0000000C - Blocks Area Size: 0010AF87  [0007C770-001876F6]
00000010 - Product_ID: 80
00000026 - Contents:     The help info   
0000003A - Version:     2.0.3.10 
****************************************************
Decrypting the 0x2800 and 0x1400 blocks...
Reversing file...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x000C3B7C until 0x001876F6
****************************************************
00000000 - Section Checksum: FD8543B6  [00000004-0007C76D]  CKSM OK
00000004 --- 0007C76D  ***** Menus / Help Section *****
****************************************************
0007C770 - Removing block encapsulations from Block Area [0007C770-001876F6]

Total bytes extracted (from the blocks): 000DCEA4    Block area processed OK

Buffer Size: 00006DEA bytes (after converting from 16 to 8 bits)

00000000 ---    0x00000000  DXE 0000 (Data Size: 00006DD4) [00000000-00006DE1]
Processor Type: ADSP-BF533/534/536/537/538/539 (boot address: 0xFFA00000)
Orig Offset: Offset: Block: Target Add: Byte Count: Flags: [  start -   end  ]
00000000 +++ 0x00000000 0000 FF800040 00000004 0012 [0000000A-0000000D]  resvect ignore
0000001C +++ 0x0000000E 0001 FF800000 000022B0 0002 [00000018-000022C7]  resvect
00004590 --- 0x000022C8 0002 FF8022B0 00000010 0003      zero-fill resvect
000045A4 --- 0x000022D2 0003 FF8022C0 00000010 0002 [000022DC-000022EB]  resvect
000045D8 --- 0x000022EC 0004 FF8022D0 0000029E 0002 [000022F6-00002593]  resvect
00004B28 --- 0x00002594 0005 FF80256E 0000000E 0003      zero-fill resvect
00004B3C --- 0x0000259E 0006 FF80257C 000009BA 0002 [000025A8-00002F61]  resvect
00005EC4 --- 0x00002F62 0007 FF802F36 000000AA 0003      zero-fill resvect
00005ED8 --- 0x00002F6C 0008 FF802FE0 0000000C 0002 [00002F76-00002F81]  resvect
00005F04 +++ 0x00002F82 0009 FF902000 00000004 0002 [00002F8C-00002F8F]  resvect
00005F20 --- 0x00002F90 000A FF902004 00000068 0003      zero-fill resvect
00005F34 +++ 0x00002F9A 000B FFA00000 00003E32 0002 [00002FA4-00006DD5]  resvect
0000DBAC +++ 0x00006DD6 000C FFA00000 00000002 000A [00006DE0-00006DE1]  resvect init

0000DBC4 --- ZLIB Decompressed Size: 001FC96C
0000DBCC --- ZLIB Compressed Block Size: 000CF2D0 [0000DBD4-000DCEA3]
****************************************************
  Section Processed OK
As you can see, the FW header has a Product_ID but it doesnt have a Product_Type! So, I don't know what they can be verifying.

I asked routerfan for a memdump so that we can see what they might be verifying.


BTW, what FW do you have flashed at this moment?

Has to be the Atten FW. Because the Siglent CNL/CML would return something like this:

https://www.eevblog.com/forum/repair/need-full-firmware-(full-dump-flash)-oscilloscope-atten-ads-1062cml/msg3038990/#msg3038990

[alexitaly]

As you can see, the FW header has a Product_ID but it doesnt have a Product_Type! So, I don't know what they can be verifying.

 Ok

I asked routerfan for a memdump so that we can see what they might be verifying.

We hope that he will be able to do the memory dump and that we will be able to understand what test is being performed... It will be necessary to fight 

BTW, what FW do you have flashed at this moment?
Has to be the Atten FW. Because the Siglent CNL/CML would return something like this:

No, i've the Siglent CNL FW (the same version of routerfan i think) with the Atten .cfg configuration file that you have posted, as you can see.
However, the keyboard response, in my opinion, is not good (and i've already changed all the encoders).

Thanks!

[alexitaly]

OK, Alex.

In that case, let's do an experiment: Flash the CNL .cfg file and try to see the responses to the 3 SCPI commands that I said.

Here is the .cfg file.

Hi tv84,
i've tried, the result is the same as you can see in the images attached.

I've a question: can you see the fw section that manages waveform writing in the buffer in case of long acquisition times? Because i think that the bug that plagues the oscilloscope is there. I imagine some wrong pointer (perhaps because the designer has forgotten that the oscilloscope does not have 2M points but only 40k points).

Thanks.

[alexitaly]

Ok i'm trying 

Please, can you write the exact syntax of the commands?
Exactly what you want me to type on the keyboard. Thanks

EDIT:
I can say that with the siglent configuration (siglent.cfg file) the updating of the waveform on the time axis seems to have more bugs than with the atten configuration.

[alexitaly]

And show me the other half of the attributes tab:

With siglent or with atten configuration?

[alexitaly]

Can be with Atten or Siglent .CFG.

ok, please wait.

Tell me this:

When you try to upgrade with Atten FW ProdID=79 or Atten FW ProdID=80 the error is exactly the same? About Product Type?

yes

Try flashing this file (Prod_ID=59).

ok, please wait

EDIT

you can see the attributes tab in the images attached.

I've tried with Prod_ID=59, but the result is the same: "PRODUCT TYPE DOES NOT MATCH"

[alexitaly]

SCPI commands: look at the different answers with siglent.cfg file and with atten.cfg file.
The only working SCPI command is SRLN.

[alexitaly]

Did you try it after .CFG Atten or .CFG SIGLENT ?

I want that you try it in both.

I've tried in both cases.

[tv84]

SCPI commands: look at the different answers with siglent.cfg file and with atten.cfg file.
The only working SCPI command is SRLN.

So, this means only Siglent implements those SCPI commands.

That's good to know.

I think this may represent a GREAT discovery!!!! 

-------------------------------------------------------------------------

Running out of ideas...

Flash this .CFG file and then try the Atten .ADS files (79, 80, 59).

[alexitaly]

Running out of ideas...

Flash this .CFG file and then try the Atten .ADS files (79, 80, 59).

Product type does not match 

[alexitaly]

Ok, one moment please

EDIT

I've tried: now, even the IDN command no longer works.

Flashing atten 79, 80, 59: product type does not match.

[alexitaly]

With this last .CFG please show a photo of the Hardware version in system menu.

Here is the requested photo.
Thanks for your help!

[tv84]

So that you understand what I'm trying to do:

Reversing 1st part of the file [00000000-000000D7]...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x0000006C until 0x000000D7

00000000 - Main Checksum: FC5AD47B [00000004-00052517]  CKSM OK
00000004 - Product_Type: ATTEN
00000024 - CFG Type: SDS1204CF
00000038 - Manufacturer: ATTEN
00000043 - CML/CNL flag: 0
00000044 - Product_ID: 79
00000048 - Image Size: 00052440 (112 320 pixels)
0000004C - USBTMC_Product_IDs: EE39 EE38 EE3A
00000052 - USBTMC_Vendor_ID: F4EC
00000054 - Product Family: ADS
00000058 - Manufacturer_Name: Atten Technologies Co,. Ltd.
00000098 - CFG Flags: 01 00 00 00 00 00 00 00 0000 00
000000C8 - ***** Boot Logo image (480x234 RGB24) ***** [000000C8-00052517]  CKSM: FC5AEA31
00052518 - Footer Checksum: FFFF9C53 [0005251C-000525B8]  CKSM OK
00052520 - Model Name 0:
0005252F - Model Name 1:
0005253E - Model Name 2: ADS1062CAL
0005254D - Model Name 3: ADS1102CAL
0005255C - Model Name 4: ADS1152CAL
0005256B - Model Name 5:
0005257A - Model Name 6:
00052589 - Model Name 7:
00052598 - Model Name 8:
000525A7 - Model Name 9:

The .CFG file has some "flags" that seem to influence the way the scope will work. I've tried messing with some of them. Everytime you change one, you have to correct the 1st Checksum.

This list describes the contents of this latest Atten_CAL_all0.cfg.  I changed a lot of flags to 00. To see which influences IDN, for example, we must turn on one by one.

[alexitaly]

So that you understand what I'm trying to do:

Excuse me, i've tried to reply, but i've written wrong things.

But... CFG Type should be ADS1102CAL... otherwise some pointers may point to wrong memory addresses: SDS1204CF has 24kpoint memory, ADS1102CAL 40kpoints memory (at this point... i hope).

EDIT

The .cfg file flashed is the first ATTEN file that you have posted.
I've tried to update to 5.01.2.32 fw release, update ok and oscilloscope appear as ADS1102CAL. The fw update did not affect the configuration.

I can confirm that the time update of the track is much better than with SIGLENT.cfg, but it is not regular: some points are lost. I think it depends on the wrong model (SDS1204CF) in .cfg file.
Can you try with SDS1102CNL or ADS1102CAL please?
Thanks.

[tv84]

I updated the previous mail.

The green part is fixed in ALL .CFG files. Atten, Lecroy, Siglent...  I think the CF means "Config Format".

The string that decides the scope model are the ones in blue, and are chosen accordingly to the BW of your scope.

[tautech]

So that you understand what I'm trying to do:

Reversing 1st part of the file [00000000-000000D7]...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x0000006C until 0x000000D7

00000000 - Main Checksum: FC5AD47B [00000004-00052517]  CKSM OK
00000004 - Product_Type: ATTEN
00000024 - CFG Type: SDS1204CF
00000038 - Manufacturer: ATTEN
00000043 - CML/CNL flag: 0
00000044 - Product_ID: 79
00000048 - Image Size: 00052440 (112 320 pixels)
0000004C - USBTMC_Product_IDs: EE39 EE38 EE3A
00000052 - USBTMC_Vendor_ID: F4EC
00000054 - Product Family: ADS
00000058 - Manufacturer_Name: Atten Technologies Co,. Ltd.
00000098 - CFG Flags: 01 00 00 00 00 00 00 00 0000 00
000000C8 - ***** Boot Logo image (480x234 RGB24) ***** [000000C8-00052517]  CKSM: FC5AEA31
00052518 - Footer Checksum: FFFF9C53 [0005251C-000525B8]  CKSM OK
00052520 - Model Name 0:
0005252F - Model Name 1:
0005253E - Model Name 2: ADS1062CAL
0005254D - Model Name 3: ADS1102CAL
0005255C - Model Name 4: ADS1152CAL
0005256B - Model Name 5:
0005257A - Model Name 6:
00052589 - Model Name 7:
00052598 - Model Name 8:
000525A7 - Model Name 9:

The .CFG file has some "flags" that seem to influence the way the scope will work. I've tried messing with some of them. Everytime you change one, you have to correct the 1st Checksum.

This list describes the contents of this latest Atten_CAL_all0.cfg.  I changed a lot of flags to 00. To see which influences IDN, for example, we must turn on one by one.

A red flag to me is:
00000024 - CFG Type: SDS1204CF

Unknown old model to me however if it aligns with the later 7" display SDS1204CFL ......2 GSA/s and tiny 24 Kb memory:
https://int.siglent.com/products-overview/sds1000cfl/

[alexitaly]

I updated the previous mail.

The green part is fixed in ALL .CFG files. Atten, Lecroy, Siglent...  I think the CF means "Config Format".

The string that decides the scope model are the ones in blue, and are chosen accordingly to the BW of your scope.

Ok BW... but... memory depth? The bug that plagues my oscilloscope is related to wrong writes in memory with slow time bases... this is why i want to downgrade to an old fw version. I want to verify if in that version there is the same bug. 

[tv84]

Gentlemen,

Look at this image that sums up all the known .CFG files so that you understand what I'm saying.

The SDS1204CFL is a feature in all files. It doesn't have nothing to do with the specific model.

[tautech]

Ok BW... but... memory depth? The bug that plagues my oscilloscope is related to wrong writes in memory with slow time bases... this is why i want to downgrade to an old fw version. I want to verify if in that version there is the same bug. 

Part of this might just be the memory depth management at differing timebases.
Max mem depth is ~1ms/div and it falls away at both faster and slower timebase settings and also Sampling speed falls at slower timebase settings, all of which are intended for best management of HW performance over the range of operating conditions.
The same principles of memory management are used in latest models for the same reasons however as they are 14+ Mpts the impact on mem depth available has a much lesser effect on what the user can achieve.

[alexitaly]

In this moment i have both oscilloscopes (ADS1102CAL and SDS1102CML) turned on on the bench. I can confirm that the ATTEN version, with atten .cfg file, with a time base of 100ms or more slow, is completely wrong in acquiring the signal 

Tomorrow i will do further test 

EDIT

With SDS1102CNL .cfg file the bug seems to be not present in single shot mode. In roll mode (slow time bases) signal representation is completely wrong BUT in single shot mode it seems to be all ok.

[tv84]

Or test with the CML .CFG file, to see if the CML flag makes any difference.