I did at some point get annoyed when dialing up the frequency past 20MHz (I think 20 was the limit), and having the Vpp click down from 10Vpp to 5Vpp
It should not change the offset or amplitude just because you are changing frequency. Instead, refuse to set the new frequency.
Yes I understand that this could be annoying at some point but it's the way it is done in several FG I have (Siglent, Hantek, even Feeltech...). This is the "Frequency priority" function and seems to be a standard way to do. When starting the FG you could also be annoyed that you first have to change your voltage to be able to select a frequency...
Anyway, it's not a big deal to add a configuration switch that inhibate this functionnality if you find it annoying. I will do it.
On the other hand, if you want to go up to 30Mhz, and it is not letting you, it would be nice if it indicated why not. Maybe by flashing the amplitude inverted red every time you try to tick past 20MHz. Same if you try and up the amplitude and it will not let you: flash inverted red the frequency or limits.
Yes this would be a nice way. I could also add it to the PC Software but it's a matter of time and priority. I will see where I can place it in my Doto list which goes on growing
As I explain some time ago, I used the Feeltech Software as a front end because it was already there plus Feeltech made the source code available. So that was the quickest way to go with the possibility to change things, should it be necessary.
The fact is that I had to change things in this software much earlier than I had expected. Actually this PC software has been developped with Visual Basic 6.0. A 20 years old IDE, more than obsolete for a long time now. So this is clearly not the best choice for an application that is suppose to grow.
I know that all the functions I add in the firmware, even if it's in the BP now, wil be usable later on with the onboard LCD.
Not sure about what will happen with the functions that I add in the PC Software now. There are things that I also want to add like Frequency/Period switch, Amplitude&Offset/Voltage High&Voltage-low switch, mHz/Hz/kHz/Mhz choice, .... but all of this is time and this may be wasted work/energy as long as we don't know what will be the final PC front-end..
This is not exactly what you asked about of course, but related and I was reminded of it.
No problem. This is the exact right place to discuss those things
As to locking the relays/range:
I noted that when you change frequency, the FPGA does that seamlessly. Not a single sample missed in the signal train, it even stays in phase, just at a higher frequency.
Except when it also changes range, then you loose signal for a few ms while it ticks over. So I can see a locked relay being useful sometimes.
Yes that was exactly the point.
In the original FG firmware, you will notice that feeltech added a 4ms slot time with no signal when switching ranges. This a bit overkill so at the moment I just change range and send the new scale value at the same time...does not seem to be that bad but it's a point that may be improved in the future. Tests will tell...