Siglent CML+ Firmware ?

[tautech]

Thanks for identifying another issue that needs be sorted.
I've whacked another query to the factory asking when the new FW is due or to get a link to it that I can pass on to you.

[StillTrying]

Any date for the next FW?

[tautech]

Any date for the next FW?

Not as yet.

Another beta, this one "hot off the press" is on its way to you via email.
Please report its fixes and failings.

When finalised the new version will be added to Siglent websites.

[StillTrying]

Oh dear, all the same 'features' are still there in P18.

All the Print BMPs I saved, saved as 751kB, they used to be 1.1MB, don't what that is yet.

I'll make a list.

[tautech]

Oh dear, all the same 'features' are still there in P18.

All the Print BMPs I saved, saved as 751kB, they used to be 1.1MB, don't what that is yet.

I'll make a list.

Sorry I can't confirm anything you raise until some new stock arrives.

To be sure it's updated correctly, can you run the FW update again and check the version is correct and listed in Utilities>System ?

As we don't have install instructions or a changelog for this beta I'm thinking it might need to installed twice as is required for new FW in some other Siglent instruments.

There was some talk of adding other Print filetype's to the UI of Siglent equipment or are they still BMP's ?

Feel free to put your list here and/or email it to me.

[StillTrying]

First thing I did was check the version had changed, however I'll update again later just to make sure.

I don't think the Save Print filetype's have changed, still just waveform or picture.

Edit. Updating the firmware again, reformatting the memory stick, reboots, self-calibrations = no difference as expected.


Pressing STOP while Long Memory is enabled doesn't freeze the displayed waveform, it clears the screen and waits/acquires 1 new trigger, makes it near impossible to capture slower/infrequent events at the higher sampling rate and record length of Long Memory.


Long Memory gets confused on changes of timebase speed, and a forced trigger doesn't clear it, FWs .12, .16, P18 all the same screens: https://www.eevblog.com/forum/testgear/siglent-cml-firmware/msg1091615/#msg1091615


No persistence on 100ns with 2 channels in use. No persistence on 100ns and 50ns with 1 channel in use.
No persistence on the expanded waveforms in Zoom/Delay mode.

ETS is slow and unstable, but that goes with saying!

[tautech]

P18 firmware:
http://www.siglentamerica.com/gjjrj-xq.aspx?id=5074&tid=15

Haven't looked at it yet.

[StillTrying]

"Haven't looked at it yet."
Don't rush, all 8,105,542 bytes and bits 100% match the one you already sent to me!

They need to supply a list of the fixes.

[tautech]

They need to supply a list of the fixes.

Siglent have, it's in the 2nd file of the unpacked download and titled Revision History:

1.   Fixed the bug: Wave trace departs from zero line while there is offset
2.   Fixed the bug: Sample rate of zoom changed after STOP in dot display mode
3.   Fixed the bug: All measurements are on, select source on a disable channel. Reboot the Scope, then the software hang on the boot screen
4.   Adjusted keyboard scan method to optimize recognizing keyboard value
5.   Modified BMP from 24 bit to 16 bit while save/get BMP form Scope

[StillTrying]

"Siglent have"

After you mentioned it I remember clicking on it from the rar, but it didn't open so I forgot about it!
They're saving the 16bit BMPs from the bottom to the top for some reason.

Meanwhile.
LongMemory, Dots, 100MS/s.
About every 6th of my infrequent triggers is showing a corrupted display.

[StillTrying]

I've managed to 'reset' something or other.
Took me quite a while to notice, but missing the (rarely used) LongMem option and "Siglent" off the screen!
Tried reloading the FW .18.
Any simple fix? Although nothing seems to be effecting my normal usage.

[tautech]

I've managed to 'reset' something or other.
Took me quite a while to notice, but missing the (rarely used) LongMem option and "Siglent" off the screen!
Tried reloading the FW .18.
Any simple fix? Although nothing seems to effect my normal usage.

I'll get someone from Siglent to contact you.

[StillTrying]

OK thanks, it's not life threateningly urgent, you may pass on my email if you want, but I tend to only check it once or twice a week.

When I confirmed 'Load' over the .18 FW file name, I was expecting it to go away for a few seconds and then say something like "FW .18 already installed. Continue ?", but it just switched straight to the "Updating firmware" screen.

[tautech]

OK thanks, it's not life threateningly urgent, you may pass on my email if you want, but I tend to only check it once or twice a week.

When I confirmed 'Load' over the .18 FW file name, I was expecting it to go away for a few seconds and then say something like "FW .18 already installed. Continue ?", but it just switched straight to the "Updating firmware" screen.

Yep, these do no matter how many times you try to install the same FW.
I've got a customer with the same issue, Siglent will sort it for you.

You're fine to continue using it. 

[Neukyhm]

When I confirmed 'Load' over the .18 FW file name, I was expecting it to go away for a few seconds and then say something like "FW .18 already installed. Continue ?", but it just switched straight to the "Updating firmware" screen.

It may has something to do with this line in "update instructions" docx: Before updating the ADS file, the ADS file need to be renamed and ensured it’s name less than 9 letters.

[tautech]

When I confirmed 'Load' over the .18 FW file name, I was expecting it to go away for a few seconds and then say something like "FW .18 already installed. Continue ?", but it just switched straight to the "Updating firmware" screen.

It may has something to do with this line in "update instructions" docx: Before updating the ADS file, the ADS file need to be renamed and ensured it’s name less than 9 letters.

The reason it is recommended to do this is the SDS1k**L UI can't display a full filename longer than 9 characters.
Therefore it's easy to select the wrong update file from a USB stick as only the first few character and the last few get displayed.
What I do is take note of the update file size (I have a lot of .ads update files on a USB stick) and that helps you select the correct one.
TBH I never rename update files but I do take extreme care of the file I select to install.

[StillTrying]

Pressing STOP while in Math, Dots+Persistence mode gives the whiteout every time.
Doesn't happen in Interpolation mode.

[StillTrying]

The maximum sensitivity you can set on the math waveform is 1pV / div.
LOL

[tautech]

Shifting a reply on Math measurements to here where it's more on topic:

Should we ask Siglent if this can be implemented ?

That would be very nice. As I said, I thought that I would see the option to measure whatever math function you are using in "Measure" menu, I expected to find that option just where you select to measure CH1 or CH2, I mean, I expected it to also measure "Math".

I too think there need be some SDS1kCML+ Math measurements and I will send a request to Siglent that at least a good basic selection be offered in future FW.

I looked at a SDS1kX and while the UI is quite different there are 24 OSD measurement types offered for the Math function.

[Neukyhm]

Shifting a reply on Math measurements to here where it's more on topic:

Should we ask Siglent if this can be implemented ?

That would be very nice. As I said, I thought that I would see the option to measure whatever math function you are using in "Measure" menu, I expected to find that option just where you select to measure CH1 or CH2, I mean, I expected it to also measure "Math".

I will send a request to Siglent that at least a good basic selection be offered in future FW.

Thank you very much. Let's see if Siglent does it.

[StillTrying]

I've seen this effect many times on all the firmwares, so I've captured one, actually captured a few.

NormalMem. LOL!

The first image correctly shows 3 peaks of smps noise near the peak of a 150kHz sine with the trigger position on the largest middle pulse.

If I expand the STOPped waveform by 1 timebase speed the trigger position moves to the 1st of the 3 pulses.

If I expand it by 1 more timebase speed, the trigger position (of the STOPped capture) moves back to the middle pulse.

I don't expect to capture all the details of the 150kHz sine and the 30MHz pulses in one capture, but it seems a strange effect to me.

[Neukyhm]

I will send a request to Siglent that at least a good basic selection be offered in future FW.

Have they replied?

[tautech]

I will send a request to Siglent that at least a good basic selection be offered in future FW.

Have they replied?

Yep. It's still in discussion of what Math OSD measurements to include.

Suggestions ?

[StillTrying]

They've got more than enough to be getting on with in this thread.

[Neukyhm]

I will send a request to Siglent that at least a good basic selection be offered in future FW.

Have they replied?

Yep. It's still in discussion of what Math OSD measurements to include.

Suggestions ?

I was thinking that they should add "Math" to the Measure menu, just like if Math waveform were a physical input of the oscilloscope.