| Products > Test Equipment |
| FeelTech FY6600 60MHz 2-Ch VCO Function Arbitrary Waveform Signal Generator |
| << < (423/450) > >> |
| DaveR:
Well, I've given Fremen's control software a good thrashing over the last two weeks and, functionally, it has stood up very well. Bugs were very few: 1. Run-time error 384 followed by crash if you try to minimise the window to the taskbar. 2. Run-time error 380 when trying to start software when FY6600 is already running (not every time, but persistent when it happens). Program starts, but fails to open COM port and shows extreme values in parameter boxes. Only cure is to close both program and FY600, then restart program followed by startup of FY6600 and manual instigation of comms. *** SEE BELOW *** 3. Run-time error 6 in Calibration, if out of range number is entered into "Ch1 L:0.5 Min" box (eg accidentally enter a +ve number). The value is saved, but the program shuts down when the message box is closed. Every feature was tested for operation and works as it should (as far as I can tell, anyway); the only shortcut I took was to only partially test Ch2 with some random settings. Sweeps using VCO input were tested using an FY6800 feeding the VCO of the FY6600 (and kept me amused for hours watching the results on the scope). The main improvements needed are now to the usability of the control software, some cosmetic, and some to the data entry method. 1. After seeing that popup box appear a thousand times when entering a new parameter, I would just love to see direct entry into the value boxes enabled! If the popup has to stay, then a bigger, bolder font is required to ease eyestrain. 2. Can a shortcut method of number entry be implemented, eg 50m instead of 50000000, 10.7m instead of 10700000, and 455k instead of 455000? Besides being difficult to read and decipher long strings of zeros, I think I'm getting RSI from bashing the zero key! 3. Remove all Chinglish from labels and popups, such as "Forth&Back" in the Sweep - Direction label (which strangely changes to the more usual Back&Forth once the Source has been changed to VCO and back to Time). As Forth, Back, and Back&Forth are not really descriptive of what happens in most of the sweep modes, "Increasing", "Decreasing" and "Alternating" may be better general terms. (Or Rising, Falling, Alternating ?) In the Waveform Window, the "Reset Waveform" button doesn't really describe what it does, ie "Clear Waveform" or "Erase Waveform", and the popup it opens is a good example of Chinglish gobbledegook, when it really means "Are you sure? Unsaved data will be lost." 4. Calibration window - it would be preferable if the first data entry popup opens as soon as the item buttons are pressed, as it's too easy to look away from the screen after clicking on a button and enter the first value from the DVM, only to then find that the popup window hasn't been open... Again, direct entry would be preferable to the popup. 5. Move the Waveform and Text windows to the RHS, so that the most used windows (Control and Configuration) are in their "natural" positions at the left? 6. Provision for naming uploaded waveform slots something other than "RandomXX" would be very good to have. How do you know what you put in Slot 51 a couple of weeks after the upload, let alone six months later? *** This actually happened again while I was writing this tome, but this time it wasn't recoverable after an hour of trying different things. The only way back this time was a full bluepill erase and reprogram. The full error message showed "Invalid parameter value", and was there even after a simple reprogramming without erasure, so the problem appears to be corruption of the data storage area in the STM32 chip. The first time it happened was after I'd closed the software and turned off the boxes, although they were still connected to the PC which was left running overnight doing other things; the problem occurred the next day, for no apparent reason, when I turned the boxes and software back on again for another session but, as stated earlier, I managed to get everything up again pretty quickly and worked for several more hours without a hitch. This time I'd pressed "Send Data" in the Waveform Window when there was only a blank waveform on screen; wondering if I'd accidentally overwritten the factory sine wave in Slot 1, I went back to the Control Window to check, and error 380 appeared again. (Which reminds me - that "Send Data" button needs a confirmation popup along the lines of "Ensure selected Loading Area is correct. Send / Cancel" to stop accidental overwriting of uploaded waveforms.) I think soundtec said he'd been struck by the same, or similar, error just a few days ago, but I don't know if he's overcome it yet. I'll keep playing with the software to see if I can find any clues as to what might be happening. Regards, Dave |
| DaveR:
--- Quote from: Miti on October 05, 2019, 01:24:29 am --- I should have done it two days ago. I've attached it in the original post. --- End quote --- Cheers, Miti! Dave |
| soundtec:
Thanks for that Dave , Yeah its very similar to the issue Ive had , like you I found it best to run up the software before the machines connected ,then manually select the com after . I did get a couple of lock ups on both software and the Generator ,but a power down and back up of FY and restart of the software cleared the problem . Without any software connected I find the FY to work fairly well , its putting out the waves or functions its supposed to do. One thing I found a bit superfluous was the menu within menu , so for instance say you have a choice of two variables , Trig or counter input , instead of source button toggling trig/counter you have to go down another menu level to select between two variables , I think multiple presses to cycle through the options is better and easier than another layer of submenu , I must reflash my on-board Stm32 , I'll be more carefull this time , Ive a feeling there could have been a grounding issue between the computer and the FY6600 last time ,a ground loop and hum I think could upset the flashing of memory , I'll run the laptop off batteries only this time when I run the update . Maybe screening both the ST link and the FY6600 in a biscuit tin for the duration of the update might be a plan too . |
| CDaniel:
No issues flashing the microcontroller ... you should do it with the face off , so the power is only from programmer . |
| DaveR:
Hi soundtec - it's possible that Run-time error 380 is covering two different types of problem: the minor one which we've both had and found a workaround for, and the major one I had last night. Although recovery from that isn't that big a deal once you know what's happened, it's not something you'd want to happen regularly, as you lose all your saved setups and calibration details each time. It would be prudent to take a screenshot of your calibration figures so that they can be quickly re-entered without needing the DVM every time. Regards, Dave |
| Navigation |
| Message Index |
| Next page |
| Previous page |