The spectrograph function does this, shift Ch D input to SPEC. Ch A or B must be turned on, with Ch A
having precedence over B. This plots frequency on the vertical axis against time on the horizontal axis,
with changes in color representing the intensity. Change frequency range with the time/div control, which
will also control the horizontal scan speed up to a certain point. Intensity range can be varied with the FFT
sensitivity control (log > auto > manual from 0db to +42 db).
Time span for one screen varies from about a few seconds at the highest scan rates down to perhaps several
minutes for very slow time bases. If device is not triggered with a signal, AUTO timebase mode can be used
to display background.
An amplitude envelope can also be superimposed by pressing center right toggle while menu is on SPEC. See
the user guide for more info.
Thanks Wildcat for the update, i’ll try it out tomorrow. Btw i manage to get us DFU v3.42 which apparently supports Windows 8/8.1/10
<LINK_TEXT text=“http://www.minidso.com/forum.php?mod=vi … 897&extra=”>http://www.minidso.com/forum.php?mod=viewthread&tid=897&extra=</LINK_TEXT>
I’m assuming FTDI usb to serial should work with programming. Guess i should try it out:) Anyone knows if i need to backup the serial/license key too?
Wildcat, just tested this version on my dso, this one copies 3/4 before disconnecting and manages to write some data leading to the attached boot screen. You seem on the right track as the versions before only copied like 2/4 before disconnecting in the middle of the copying operation. Also this version seemed to overwritten PAWN while the v4.4 “3-slot” and “reduced rom + ram” which install fine don’t overwrite PAWN.
edit: open the attachment image in new tab as it does not re-scale properly in the forum
DID IT! I updated my hw v2.81 to DFU v3.45C and activated with my license key! Now the DFU drive works in Windows 10!
Also Wildcat i tested your v4.4 (4-slot version, + v2.81 v4.4 test version) and they still don’t work. “3-slot” version, “reduced rom + ram” + pawn still work perfectly.
I will be making a tutorial on flashing DFU so stay tuned:)
This last post was an attempt to help with possible issues with a properly loaded program. Other than
a verified and fixed issue of the ROM being overwritten past a certain point, it looks to me like all the
problems so far have been with the inability of the OS used to properly load the hex files onto
the DFU as well as problems with formatting the 8MB drive. If the program is not loaded properly,
you can’t expect it to work.
There have been problems with using Windows 8 and later, possibly with hex files above a
certain size. There have been issues with Windows 8 and earlier devices as well. I would suggest
using an earlier version of Windows, and make sure you extract the files from the zip archive
before flashing.
And yes, this last test post will overwrite PAWN, as it was stated “will overwrite slot 4” and
recommend downloading from the archive on page 41. All of the “test” posts are for testing
purpose only.
Look, it seems you are confusing two different problems. DFU drive support in Windows 8/8.1/10 is one problem, which has been now fixed with DFU v3.45C. The second problem is installing your v4.4 "4-slot" version in hw v2.81 devices. This done under XP/7/10 will fail due to how you wrote your program. It has nothing to do with the OS. I wished i had the money to buy you a hw v2.81 so you could develop on but seeedstudio/minidso they should at least send you one for free for your efforts!
edit: Flashing tutorial is up! http://www.seeedstudio.com/forum/viewtopic.php?f=26&t=6186
Hi, I have Hardware 2.81 with MCU Type STM32F103VE Running:
DFU 3.40C
SYS1.62
APP is Wildcat 4.4 from Page 41 and
PAWN ver 0.11
SYS, APP and Pawn can be loaded with no errors using Windows XP or Windows 7
The APP 4.4 stops loading every single time under Windows 8.1
The 4.3 APP can occasionally be loaded successfully under Windows 8.1 but loads every time under Windows 7
My understanding for this combination of 2.81 hardware and 3.40C DFU is the errors are related to the size of the file and Windows 8.1 failing to load to the DFU volume, not the arrangement of APP slots used.
It is possible with a newer DFU that Windows 8.1 might load 4.4 without errors but the DFU 3.40C Window 8.1 problem is one identified by the support team for the authors of the DFU.
I don’t think the errors loading the file are anything to do with Wildcats 4.4 APP other than the size exceeds what ever limit causes loading to fail under Windows 8.1 and DFU’s 3.42 and below. USE Windows 7 and 4.4 loads and runs (either version) remembering the version on page 41 allows space for PAWN.
I have spent days on this, I could be wrong and please do your own tests. If someone had told me before Wildcat 4.4 was available “Only use Windows XP or 7 when loading APP’s and SYS files” I would have 30+ hours of my life back.
I am still very happy because Wildcats 4.4 in my view is well worth the time I spent to get it working, especially if it helps other people avoid the swamp.
Hi, I would not be confident DFU version 3.45C has resolved APP loading issues with Windows 8.1 and 10 until this was tested carefully.
Wildcat 4.4 is the largest APP yet written for this platform and was not available for testing when DFU 3.45C was written. My understanding is it was written to address flakey copying of 2 and 3 slot applications and possibly allow Mac OS to copy files.
The 8MB volume supposedly needed at least SYS 1.64 to work with Mac OS but SYS 1.64 can cause other problems with crashing at launch.
Again I can only test what I have and I agree someone, probably SEEED? should sent Wildcat several units with 2.81 hardware and DFU 3.40C and on a second unit the latest shipping version.
On the last note yes i too believe Wildcat should be sponsored a hw v2.81 unit at least.
Regarding testing, DFU v3.45C has been around for a couple of months already, and did my testing too on Windows 10, and there are no disconnection problems. On the other hand the large .hex app file disconnection issue could be either workaround in the app software by Wildcat or either in the DFU but let’s be honest, how many people would open the device and flash using an RS232 adapter?
TheNaughtyFantasy Hi, I agree many may avoid serial flashing but thanks to your DFU adventure and file archive upgrading is at least doable, I certainly will give it a go.
One reason I have been more inclined to think large APP (4.4) + Windows 8.1 is causing issues is my cheese and chalk experience loading the same files on Windows 7 VS 8.1
There is no doubt the APP still has to sit inside the boundaries of available/legal flash but I believe version 4.4 - the page 41 version does this. Hopefully DFU 3.45C is golden but I would not be surprised if it took another revision to get it behaving with these very large APP sizes and Windows 8.1/10.
Do you think it’s worth us each PayPal-ing $5-10 to Wildcat to buy the new version?
In regard to the disconnection problems not seen in Windows 10, in Windows 8.I never saw disconnections using the DFU, in fact it almost always seemed like thinks were ok and files would often load and show .RDY but still be not loaded properly (they showed .ERR regularly as well). If I can load Wildcat 4.4 using Windows 7 and everything is working my belief is that code is good. We do need a way of loading large APP’s reliably with Windows 8.1 and 10 and that might involve a new DFU version for something as big as 4.4 - perhaps we should get whoever wrote DFU 3.45C to test it out and see if it is possible. Whatever - your point about the users not re-flashing their DFU is bang on and they will not want to buy new hardware to get the new DFU either so perhaps some clever code that loads as an APP and then updates the DFU might do it, or be impossible for whatever reason. Perhaps SEEED could consider selling the right serial cable setup ready to go to help users update. It may to be a bigger nose bleed for many users to get Windows 7 or XP happening than refresh their DFU if a version that makes it all wonderful is available, perhaps with a script that backs up everything first and allows recovery without skillz.
Awesome. That’s what I thought the Spectrograph function was for. But when I used I had always gotten a vomit of colors and figured it was a different type of spectrograph than what I was hoping for. Anyway, it works. I will need to tinker with this a bit and delve into the manual. 
Thanks!
You’re welcome
This “vomit of colors” is just background noise, which can become prominent if FFT gain is set
high or on LOG or AUTO with no signal. To adjust gain, with menu on CH D, press button 4 to
change menu item, which will access the gain setting. Then use left toggle to change setting. The
user guide simply states “adjust gain the same way as for FFT”, which may not be clear unless you
look that up.
That’s the weird thing…in my device even under windows 7 v4.4 “4-slot” version will not install. Anyways i’m planning to test all of the versions from v4.1 + test versions again with sys 1.62 + sys 1.64 and make a list of what works and what doesn’t.
We could make some paypal crowd funding but it’s better to make a thread first so that we gather more people and so the seeedstudio sees it and hopefully helps us a bit.
TnF Hi, If you have a chance try loading Wildcat 4.4 under SYS 1.62 - changing to 1.62 from SYS 1.64 stopped my apps from crashing when launched. It might not be the same on your device but it could be worth a try.
I have ordered the same 3.3v USB/Serial converter (less than $3 delivered via that auction site). I have plenty of others but they are 5v or the wrong chipset and it’s jut not worth $3 to futz with the issues.
I agree a thread to to get some people/momentum behind getting the latest hardware to Wildcat is the way to go, are there any rules or forum etiquette about how we make that happen?
I did test…major test, took me 1-2 hours to finish. I never had the problems you are describing. If it installs correctly it works on my device. Yes they are pretty cheap. You could used a level converter in your case if you had one lying around. I’m not sure of the donation rules, maybe you are willing to make a thread about it and notify Seeedstudio to see if they can help us out? As long as everyone has paypal i don’t see the problem.
So Wildcat here’s my latest test. All done under Windows 10 with DFU v3.45C which supports Windows 8/8.1/10. SYS 1.64 and HW 2.81
I repeated the test with SYS 1.62, but got the exact damn results. I was going to test SYS 1.63 afterwards but i don’t think it will change anything. Largest file that can be loaded correctly is v4.3 403KB, but always needs a second try to give a RDY file, even though it looks to work correctly on first try. However it seems that the filesize plays role in copying the file over, rest it depends on the program; for example “REDUCED ROM” is 385KB but doesn’t work, it gives .ERR.
It is worth noting that i did multiple installation tries on every problematic .hex. Minimum 3 each, and for v4.4 4-slot over 6 tries. Also when i downgraded my SYS to 1.62 i had to reinstall PAWN again. It will always give me .ERR (even back when i bought my DSO), and needs several tries to work (5-7 tries) even though it will always give .ERR. I wonder why is that since it will always give the same .ERR…
TnF hi again. Seriously, what you describe, especially with SYS 1.62 is exactly my experience with Windows 8.1. Give it a try with XP or 7.
I just tried to load V4.4 from a Win 7 machine with Win 7 displaying the zip archive as a
directory, and it would not work. I suspect you have to extract the files first…
Loading the same hex file as a stand alone with the same Win 7 machine worked just fine.
Could you download the attached file? This is a copy of the HEX file from page 41.
NOTE that this is NOT a RAR archive, but a HEX file renamed with a RAR extension, the forum will not let me upload HEX extensions. RENAME the file from app1.RAR to app1.HEX and see if it will load and work with a Win 7 machine. Thanks
This is the same issue i had with Win 7 and sys 1.62. Anyway i’ll try it again with my new 3.45C DFU and see if there is any difference. Also i always extract the files before copying them. Not directly even though in reality it makes no difference as the extraction takes place in a temp folder. And i checked the hash of the files for any corruption and there is none. Either way i will make a video because it seems i’m not getting through. I will reload the fpga too this time, just in case it has somehow “corrupted” and causes this issue.
EDIT: Just tested it and i’m uploading the video right now.
In the video i initially show hash comparison between the hex.rar file you provided with the original extracted. Completely the same. The environment is obviously WIN 7. I show the 1.62 SYS version and DFU v3.45C. I have re-installed fpga 2.81 prior to the video. As you can see following that, v4.4 “4-slot” fails to install with disconnection of the DFU drive as i’ve described in my previous test list. Following that failure i attempt to install v4.4 “reduced rom and ram”. While the file copies it doesn’t give a RDY file on the first try (even though it has been installed correctly and does work), but it gives on the 2nd try. This is the same thing as i described in the test list above: “Wildcat v4.3 403KB 3-slot NO RDY on first try, although it worked, since it completely copied the hex file over; 2nd try gave RDY file as normal”. Further testing shows this type of error will happen for every proper app that is attempted to be installed after installation of any problematic v4.4 version (the ones that the drive disconnects while copying the file like v4.4 “4-slot version”).
What I need to know is if you have tried to INSTAL the app1.rar file I uploaded…
I know you compared it to the file in the archive, but when you make statements like
“Not directly even though in reality it makes no difference as the extraction takes place
in a temp folder” you are not being very clear about just how you are doing this.
Also, I don’t see any links to the video you uploaded.