Please tell me what you need to know and I will write it up. On Linux or a Mac the upgrade disk disappears completely every time it checks for new files. (about every second or two) This interrupts copies, or truncates them, and umounts the drive about as fast as the OS can mount it. This makes it so that you can’t copy anything reliably. I even tried to write a script to detect the disk had reappears and then did an ordered copy of the files, but that failed as well. Windows seems to tolerate the disk disappearing for a moment, but Linux and Mac os treat it as if the drive was unplugged while active. So the experience on Windows is good, but it is unusable on Mac os or Linux, even from a program trying to interact with it.
Is this what you need or is it something else? I am willing to help, but it is hard to know what someone doesn’t know. If I were going to fix it, I would change the embedded code to wait for a button press before disconnecting to check for new/changed files. That way you could succeed on copying the files on, before the system sees the disk go away as it now does.
When I attach 2.6 in “upgrade” mode on Linux I see that there are no partitions (just the disk) and it don’t mount, when I connect it to mac osx it ignores it and when I connect it on windows I cannot click on my computer any more as it is trying to mount the disk …
any ideas?
EDIT:
I finally managed to solve the problem, 2win machines were not working just like the linux and mac, third win machine worked with it without a problem … weird
You may want to edit your original post in this thread in 3 ways
First, you may want to change your sentence about which software to use because it is too vague. You could list the latest file version number for V2.2 hardware, and also show the first file version numbers for V2.6 hardware. For example, only use verAA or lower for hardware v2.2 and only use verBB and above for hardware v2.6.
Second, explain front end compensation is different from the 10x probe compensation, and that these are both different from Quad calibration (input range scale calibration).
Third, you may want to post only attachments of the most current versions of all files here, and remove obsolete versions to reduce confusion.
The filename for the probe compensation attachment should probably be renamed to “front-end compensation and 10x probe compensation.zip” (or words to that effect) for better clarity.
This is just a suggestion on my part. Keep up the good work.
What I don’t understand is why those informations are not put on the garden.
As stated on the home page of the garden it is a place where to find “A collection of product info pages” and “Includes datasheet, source files, application notes and related application info”
On the product page there is a version tracker (with no information at the moment) no link to any source file or binary file. As we already ask when we download a new version we have no idea of what this version try to correct or add.
Please Please PLEASE make it clear what files have changed and need to be installed onto the quads, if any, in this release. All i see is a list of update with NO IDEA which it the most current. THis request has been made several times now, so much for listening to customer suggestions etc …
I am just starting to use my Quad for the first time as a tool to measure some I2C signals from sonar device. I am seeing a lot of flicker on the screen at 20usec/Div and the system only triggers about 1 time in 5 at 10usec/Div. I am using channels C/D for inputs. Channels A/B just gave me a badly slewed wave that was all but useless to read.
I was also wondering why there is a threshold on the trigger for C/D since they only show as logic 0/1 with a single Div difference. The only sensible trigger for these inputs it leading/falling edge. It gets confusing when you switch between trigger sources C/D only to find that the trigger level is set outside the signal level that you have no control over.
Since the inputs C/D have no signal processing like A/B I can only assume that the firmware is missing trigger events on these channels. I would be expecting to be able to see a 10 meg bandwidth at the very least on these inputs. Perhaps someone can look at the trigger logic for the digital inputs
I just got my DSO Quad HW2.6 today, and started playing with it immediately. It had SYS_134/APP_235 firmwares on it, so I upgraded to the latest sys_141/app_243…
But has anyone else had issues in that it doesn’t save your settings/preferences by hitting the “o” key? It claims it does, but you shut it down and turn it back on, and everything is reset to defaults.
Am I wrong that it shouldn’t save over a power cycle?
yes ,it does. it seems this version of firmware do not support the settings/preserence well . i have sent this bug to designer and he told me it will be modified soon.
