Title: {done} how to change the band cut-of frequency?
Post by: Keine Ahnung wer der Idiot ist:p on 08. July 2019, 07:48:57
Hi OM, YL, SWL's
my direct question is, at which part of programmer software I can optimize the band cut-of frequency's for my own need like region-1 exactly! Second, I have extended license in germany to work for BW & THW in a spezial part of 60m band. I want to configure the firmware by my self for my personal commitment. Thanks for all information to this topic, bro.
I setup on MacOS High Sierra the eclipse software and compilers too. I can build whiteout errors a firmware file on my system now. But, I don't know on which part of the whole project I have to do my changes. I need you to get it done, thanks.
73 Dirk de DL |
Title: Re:how to change the band cut-of frequency?
Post by: Keine Ahnung wer der Idiot ist:p on 08. July 2019, 07:55:27
The goal is to optimize all amateur band cut-of frequency's to region-1 and activate the differences on the band I have to work on the extended license management for the emergency radio activities (THW).
The last step is to build many more different fw files every for the event I do, like sota gma activities in only ft-8 or others modulations to get fast and simple in action;) But this is future, first I need to know how to optimize the bands I need. |
Title: Re:how to change the band cut-of frequency?
Post by: dl8mby on 08. July 2019, 09:08:18
Dir Dirk,
as I'm working with Linux, I look inside .h und .c
Files for pattern FREQ (lower & upper case -i grep parameter)
cd UHSDR-active-devel/mchf-eclipse/basesw/mcHF/
find . -name \*.h -exec grep -i -H 'FREQ' {} \;
find . -name \*.c -exec grep -i -H 'FREQ' {} \;
UHSDR/UHSDR-active-devel/mchf-eclipse/drivers
find . -name \*.h -exec grep -i -H 'FREQ' {} \;
./ui/ui_configuration.h:#define EEPROM_BAND0_FREQ_HIGH <<== perhaps the right place!
I found the ui_configuration.h file with BAND defines.
But it seems that this are binary values directly for the freq. synthesizer chip to programm.
vy73
Markus
....
|
Title: Re:how to change the band cut-of frequency?
Post by: Keine Ahnung wer der Idiot ist:p on 08. July 2019, 09:48:32
Hi Markus,
first thank y for answer.
Oha.. I think I have to do a look but on point, we need the exactly informations how to change. I also suspect that inside the complete jumper labels and environment variable in use to define. But this is just my first impression;)
Ok.. back to the point. How and where I optimize the cut-out frequencies for alle the bands. In the actually firmware I can't find just one band is right for region 1 :-D How ever, let's fix this up together, I'm just a loan in programming but a specialist for hf engineering. |
Title: Re:how to change the band cut-of frequency?
Post by: dl8mby on 08. July 2019, 12:35:45
Dirk,
a more important thing to take into consideration are the HW filters (BP and TP)
inside the mchf which have to be adapted for you needs.
So it's not only a sw issue to move the rx/tx frequencies but hw issue too.
vy73
Markus
|
Title: Re:how to change the band cut-of frequency?
Post by: DD4WH on 08. July 2019, 14:29:06
Hi Dirk,
have a look here:
https://github.com/df8oe/UHSDR/blob/active-devel/mchf-eclipse/drivers/ui/radio_management.c
Is this what you are looking for (line 97)?
73 Frank DD4WH |
Title: Re:how to change the band cut-of frequency?
Post by: Keine Ahnung wer der Idiot ist:p on 08. July 2019, 15:18:08
Hi Frank,
right.. this looks like I want to optimize for region 1.
Can anybody other confirm this?
PS: Markus, sure.. but first I want only optimize the correct cut's. |
Title: Re:how to change the band cut-of frequency?
Post by: Keine Ahnung wer der Idiot ist:p on 08. July 2019, 16:18:21
// IARU Region 1
const BandInfo bandInfo[] =
{
{ .tune = 1810000, .size = 190000, .name = "160m"} ,
{ .tune = 3500000, .size = 300000, .name = "80m"} ,
{ .tune = 5351500, .size = 150000, .name = "60m"} ,
{ .tune = 7000000, .size = 200000, .name = "40m"} ,
{ .tune = 10100000, .size = 50000, .name = "30m"} ,
{ .tune = 14000000, .size = 350000, .name = "20m"} ,
{ .tune = 18068000, .size = 100000, .name = "17m"} ,
{ .tune = 21000000, .size = 450000, .name = "15m"} ,
{ .tune = 24890000, .size = 100000, .name = "12m"} ,
{ .tune = 28000000, .size = 1700000, .name = "10m"} ,
{ .tune = 50000000, .size = 2000000, .name = "6m"} ,
{ .tune = 70150000, .size = 500000, .name = "4m"} ,
{ .tune = 0, .size = 0, .name = "Gen"} ,
}; |
Title: Re:how to change the band cut-of frequency?
Post by: DF8OE on 09. July 2019, 06:40:14
Definition of bands is a complicated thing. You have to look at the regions, and for some bands and specific countries there are special regulations. So it is not set up a simple "region switch" but you have to define specific regulations, too. So we decided to stay on a mix of setings which should cover all regions and countries without programming difficult lists ::)... We hope everyone is able to look what he is allowed to do and what not...
vy 73
Andreas |
Title: Re:how to change the band cut-of frequency?
Post by: DB4PLE on 09. July 2019, 12:03:54
Hi,
of course, the way we do this, it is possible to implement region switching in a fairly simple way, just define multiple bandinfo sets (one per region, with the default one being the one we have today). However, things changing the number of bands would need further investigation to be sure this is not going to cause problems. Eventually, of course, not a real problem, just more work.
Although I would spend a little more effort to integrate also the name of the bandInfo into the data set. Also more work but pays off.
Just like this (and some more changes like settings in the config menu, not shown):
Code:
// IARU Region 1
const BandInfo* bandInfos[] =
{
{
{ .tune = 1810000, .size = 190000, .name = "160m"} ,
{ .tune = 3500000, .size = 300000, .name = "80m"} ,
{ .tune = 5351500, .size = 150000, .name = "60m"} ,
{ .tune = 7000000, .size = 200000, .name = "40m"} ,
{ .tune = 10100000, .size = 50000, .name = "30m"} ,
{ .tune = 14000000, .size = 350000, .name = "20m"} ,
{ .tune = 18068000, .size = 100000, .name = "17m"} ,
{ .tune = 21000000, .size = 450000, .name = "15m"} ,
{ .tune = 24890000, .size = 100000, .name = "12m"} ,
{ .tune = 28000000, .size = 1700000, .name = "10m"} ,
{ .tune = 50000000, .size = 2000000, .name = "6m"} ,
{ .tune = 70150000, .size = 500000, .name = "4m"} ,
{ .tune = 0, .size = 0, .name = "Gen"} ,
},
// IARU Region 2
{
{ .tune = 1810000, .size = 190000, .name = "160m"} ,
{ .tune = 3500000, .size = 300000, .name = "80m"} ,
{ .tune = 5351500, .size = 150000, .name = "60m"} ,
{ .tune = 7000000, .size = 200000, .name = "40m"} ,
{ .tune = 10100000, .size = 50000, .name = "30m"} ,
{ .tune = 14000000, .size = 350000, .name = "20m"} ,
{ .tune = 18068000, .size = 100000, .name = "17m"} ,
{ .tune = 21000000, .size = 450000, .name = "15m"} ,
{ .tune = 24890000, .size = 100000, .name = "12m"} ,
{ .tune = 28000000, .size = 1700000, .name = "10m"} ,
{ .tune = 50000000, .size = 2000000, .name = "6m"} ,
{ .tune = 70150000, .size = 500000, .name = "4m"} ,
{ .tune = 0, .size = 0, .name = "Gen"} ,
},
};
|
|
73
Danilo |
Diskussions- und Newsboard des DARC-Ortsverbandes I40 | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.
|