| 1 |
allgemeine Kategorie / UHSDR Firmware / Re:Virtual keypads |
am: Heute um 10:22:11 |
| Begonnen von Michael_K | Letzter Eintrag von DD4WH |
Hi Slawek,
take your time!
If I can be of any help in preparing Wiki texts, please let me know and I will write up something, which you can then use and correct, if you want.
As you know, I am working on fully free adjustable filters for the OVI40 at the moment, so I am not sure how useful a button approach for those filters would be. But for F4 users, a button approach could be useful (however it could turn out, that freely adjustable filters could also be implemented on the F4, but that is totally unsure at the moment). But you are right, the encoder approach implemented at the moment is already really nice and useful.
Also I cannot promise any time frame for the new filter implementations due to my time restrictions ;-).
73 Frank |
  
|
| 3 |
allgemeine Kategorie / mcHF Projekt Deutsch / English (here you can discuss everything related to mcHF) / Re:mcHF V0.6: DSP button does not work |
am: Heute um 08:29:46 |
| Begonnen von WD8BXS | Letzter Eintrag von DF8OE |
I upload EVERY new firmware (of couse) and that never happens here (not on F4 / F7 / H7)... Cannot reproduce.
vy 73
Andreas |
|
|
| 4 |
allgemeine Kategorie / mcHF Projekt Deutsch / English (here you can discuss everything related to mcHF) / Re:mcHF V0.6: DSP button does not work |
am: Heute um 07:40:09 |
| Begonnen von WD8BXS | Letzter Eintrag von SP3OSJ |
After uploading a new firmware, or in the menu settings, the buttons in DSP turn off.
This is happening.
You need to know where to look for DSP activation. |
|
|
| 5 |
allgemeine Kategorie / mcHF Projekt Deutsch / English (here you can discuss everything related to mcHF) / Re:mcHF V0.6: DSP button does not work |
am: Heute um 06:52:10 |
| Begonnen von WD8BXS | Letzter Eintrag von DF8OE |
Hmmm....
pressing long deactivates (or activates) the posibility of choosing a method by "touching short". If it is deactivated by touching long (visible at the box which is around it) you cannot choose it by accident. If you want to have it back again touch long. I think this is intended - or do you mean something other?
vy 73
Andreas |
|
|
| 6 |
allgemeine Kategorie / UHSDR Firmware / "12KHz firmware issue" |
am: Heute um 06:45:23 |
| Begonnen von DF8OE | Letzter Eintrag von DF8OE |
This is a frequently upcoming theme in Yahoo NG. Here in our group I never have had heard about it. I am reading in Yahoo, but I do not write there since nearly a year. But I want to help people who can see this issue at their rigs.
Sympthoms:
If you tune with VFO over the bands you can hear strong signals appearing every 12KHz. You can definitely hear them, you very rarely see them on scope / WF. This is independent of band, Xlate setting, working mode and any other setting you can change. Yes: you can cycle through ALL user changeable settings and reset them to DEFLT and the issue will persist!
How to get rid of it
Power down rig, press simultaneously F1-F3-F5. Hold this three buttons pressed while rig is powering up until you see the standard screen. This forces ALL values to be reset to working defaults. There are many values that are stored which are not directly accessible by users. Doing this you will get rid off the "12KHz issue" - but of course you will loose all your settings and have to rework them manually! Important is that you do not cut power supply - this would rewoke your old config! Power down rig via power button (or store active setting using long-press-F1).
The following two "solutions" do not work:
- backup your config in flash, do a "full reset" as described above and then restore your old settings from flash
- backup your config to PC, do a "full reset" as described above and then restore your old settings using the file saved on PC
In both cases you will reeimplement the issue! I have tested some hours about the issue with no big success - but I can tell something about it:
- the issue is 100% a "settings issue" - I call it "infected" from now on. You can carry an infected configuration to any other mcHF and this rig will have the issue, too from now on. (The possibility of carrying configs to other machines is only available for newer firmwares where you can read/write settings via USB and small python script using PC). This is regardless of the firmware and bootloader version. I have checked all versions where we do hold binaries in our archive (this is back to 2.5.57) All of these versions can become the "12KHz issue" when I start them with an infected config. How to check if you cannot fit config via PC to rig because the firmware does not support "python method"? Very simple. Apply the infected config with a newer firmware and "backup it to flash" after you have powered down and up mcHF. Very important is powering down and up after you apply the config because this is the point it walks into your EEPROM. Now you have a mcHF where you can use any firmware back down to Clints firmware because of the config is not changed during firmware udates/downgrades (except version string in it) and now resides in both flash and EEPROM.
- starting with implementation of very good new AGC the issue was much clearer to hear than before. That means it is present at older firmwares, too but you may think it is gone when you use firmware where new AGC is not present. Old AGC decreases sensitivity of mcHF if you have a strong signal in visable spectrum/scope ! That means: If you do have a signal which will be heard every 12KHz it would be so strong that old AGC will remove these spurs because of your sensitivity gets much lower
 !!
- So definitely this issue resides very long. For testing how long you must rebuild old firmware versions and flash them to a mcHF which has already infected config. You have to play with AGC settings (or switch it off) to identify clearly if the issue is present or not. This is very time intensive. And maybe the issue is already present in Clints last firmware - I do not have tested - but that is a good idea I got now and will do it next time.
In summary:
Is it a firmware issue?
Yes and no.
"Yes" because it is 100% code related
"No" because it only pops up if you do have a screwed configuration.
Sorry we have not yet investigated which setting (or mostly it will be a combination of valid setting which together becomes screwed) is the bad one. I have alredy bisect the infected config but could not 100% identify the problem. It is 100% in the second half of setting values - but that are more than 170...
Perfect solution would be if we can identify the problem and if such a configuration is detected when mcHF is powered on by the testing routines it will be corrected automatically to valid ones. So you would not loose all your settings. But again: my first idea of a "fast success" was shattered because of the issue is very, very old but was not identified because of bad working old AGC.
There are only a handful of rigs which do have the issue. So actually there is no other possibility to get rid of it using the method I mentioned above.
If someone can reproduce the way he awakes the issue this would very appreciated! This would give us strong hints where to search.
EDIT:
I am 100% sure that settings of IQ (RX / TX) are **NOT** the cause of this issue and individual settings which are written down before cleaning can be reentered after full reset. Settings for PA (ALL settings) are not critical, too.
I would stop at filter settings, display settings, NR settings and so on. All these might be involved in the issue.
And the boundary of "first half" is at <amount of all settings> / 2
vy 73
Andreas |
|
|
| 7 |
allgemeine Kategorie / mcHF Projekt Deutsch / English (here you can discuss everything related to mcHF) / Re:mcHF V0.6: DSP button does not work |
am: Heute um 06:42:50 |
| Begonnen von WD8BXS | Letzter Eintrag von SP3OSJ |
Press (short) the "DSP" icon on the LCD
Press "NR" for a long time (the subtitles will turn black)
Press "AAUTO NOTCH" for a long time (the subtitles will turn black)
...............
...............
Look my movie: https://youtu.be/i5HKMnpkQio
73
Artur |
|
|
| 8 |
allgemeine Kategorie / mcHF Projekt Deutsch / English (here you can discuss everything related to mcHF) / Re:mcHF V0.6: DSP button does not work |
am: Heute um 05:45:55 |
| Begonnen von WD8BXS | Letzter Eintrag von DF8OE |
Have you checked in button test if it is only one button detected and it is named as "G2"?
vy 73
Andreas |
|
|
| 9 |
allgemeine Kategorie / mcHF Projekt Deutsch / English (here you can discuss everything related to mcHF) / mcHF V0.6: DSP button does not work |
am: 17. August 2018, 23:55:14 |
| Begonnen von WD8BXS | Letzter Eintrag von WD8BXS |
New V6 build here, the DSP (G2) button does not work, I here the beep when I press it, but it does not change the DSP.
Any ideas??
DE Chuck WD8BXS |
|
|
| 10 |
allgemeine Kategorie / UHSDR Firmware / Re:Virtual keypads |
am: 17. August 2018, 21:20:27 |
| Begonnen von Michael_K | Letzter Eintrag von SP9BSL |
Hi Frank,
thanks, I'm guilty because of lack of wiki for all this, the info is here in this thread only. I will prepare wiki in a few days, now I'm little busy working with 2...4GHz stuff and 800x480 driver for OVI40. I have some concepts about filter selection keypad, but as yet I do not see it better useable than we have today with E3 knob... |
|
|
Zurück zur Foren-Übersicht.
|
|
|
