Let's Promote bitxmap.com Re: [BITX20] bitxmap.com and mark your spot in the world
Let's Promote
Can HF Signals put an announcement and link to BitxMap on their web site?
At the end of these emails have a link and some text about ?
It would be neat with our UBitX connected to our PC's, there would be an app to directly update Bit Map from the UBITX.
Let's keep BitMap going.
Dave WD8AJQ ?
5
toggle quoted message
Show quoted text
On May 17, 2021, at 11:03 PM, Doug W < dougwilner@...> wrote: If you are new here you probably have no idea what I am shouting about.? In addition to this list, we have a map at? where you can mark your location and see the worldwide span of the community you are now part of as one of us.? Go check it out at
--
|
Hello friend Arora here Carlos PT9EB I wish you well with your family. I don't know if you managed to solve E-BITX IF as you reported. I've been looking at your comments and it looks like you've made changes to the transistors and I hope it worked because the transistors listed in the project are perfect for the radio to work properly. BF494 I want you to leave it on the PCB, it has greater efficiency as a whole. Step 5 place the xtal carcass for gnd. In Step 6, check the voltages of the transistors in TX and RX, but remember that the VFO / BFO must be connected to the board and other accessories of the TX / RX volume led set with a clamp or a touch tip on the C30- on Base Q5) You will hear a noise in the AF indicating that the previous steps are ok. In the following steps you need to be very careful with the windings of the toroids in relation to the spacing between the turns and tightening so that it is as fixed as possible on the toroid that after inspecting the turns externally and internally so that the spacing is perfect then you can use a plastic product to fix the loops as well as I used and you can see in the video that indicates the supplier. In this step 7 you use the 1N4148 diode, it is easier to measure it yourself if you use the BAT54S, but use the 1n. Making sure everything is fine in Step 8 after mounting and checking the voltages, do a test on the Base of the (Q7) BF494 then you will hear the noise of the ok strip. And follow your assembly according to the instructions of each stage. In BPF you have to be very careful with the winding because there is a beginning and an end of each inductor and not all are the same. If you need some support, even with engineering training, we always have the opportunity to learn from friends with bench experience. I have more training and radio work. I'm about 30 years old on the radio, but I'm always learning from former teachers. and amateur radio friends. If you need better information my phone and whatzapp is: +55 64999629242
Hi, it is with the STOCK firmware that BFO and VFO are not independent of each other.
With Raduino V2, I have done necessary modifications to
1) Hold the PTT low so the Dial lock goes away
2)VFO pot is smooth
3)Did the necessary changes to have it oscillate to 14Mhz.
I have been provided with the original sketch that Sunil Has. If you guys want it either let him post, or I can do the need ful if no body minds( technically it is open source, right?)
Measurement Apparatus is CADDO 35MHz CRO which is soon going to be upgraded with a MSO or DSO by month end which has 100MHz Bandwidth.
Technique to measure:-
I am not counting the numbers or using ms/div scale to calculate the frequency.
It is common sense that the sinusoidal graph should etiher compress or expand (VOLTAGE TIME) for either BFO or VFO depending on which one is selected.
I tried it with load (ie EBITX CONNECTED TO DDS) and without load (JUST DDS)
If i change bfo, vfo changes too and vice a versa.
Shall post raduinov2 sketch on GIT for E.Bitx.....do let me know what more can be done :)
--
Atenciosamente.
Carlos Fraga
|
Hi, it is with the STOCK firmware that BFO and VFO are not independent of each other.
With Raduino V2, I have done necessary modifications to
1) Hold the PTT low so the Dial lock goes away
2)VFO pot is smooth
3)Did the necessary changes to have it oscillate to 14Mhz.
I have been provided with the original sketch that Sunil Has. If you guys want it either let him post, or I can do the need ful if no body minds( technically it is open source, right?)
Measurement Apparatus is CADDO 35MHz CRO which is soon going to be upgraded with a MSO or DSO by month end which has 100MHz Bandwidth.
Technique to measure:-
I am not counting the numbers or using ms/div scale to calculate the frequency.
It is common sense that the sinusoidal graph should etiher compress or expand (VOLTAGE TIME) for either BFO or VFO depending on which one is selected.
I tried it with load (ie EBITX CONNECTED TO DDS) and without load (JUST DDS)
If i change bfo, vfo changes too and vice a versa.
Shall post raduinov2 sketch on GIT for E.Bitx.....do let me know what more can be done :)
|
Re: Bonehead mistake, hard to detect
Yes, you could.
Jack, W8TEE
On Tuesday, May 18, 2021, 11:49:47 PM EDT, jerry@... <jerry@...> wrote:
>> The C compiler my company marketed had a Picky Flag that could be
>> set from 0 to 10. Level 10 was infuriating. Indeed, Level 7 said
>> that any_ printf()_ call had to be of the form:
>>
>> _? successfulConversionsMade = printf("whatever...");_
*** Wow.? That *is* fussy.? Could you at least cast it to (void)?
? ? ? ? ? ? ? ? ? - Jerry
-- Jack, W8TEE
|
Sunil, good to see you jump in here!
It is good that you have the Easy Bitx available, especially now that?
most other single band kits such as the Bitx40 from hfsignals.com
and the Bitx20A from qrpkits.com are no longer available.
I am not aware of any issues with getting the Easy Bitx to work,
many people have had success with it.
If someone is using unknown firmware instead of your stock firmware,
there is little point in attempting to figure out this moving BFO issue.? ??
Generally speaking, when asking for help it is best to include complete information
on exactly what equipment you are working on, what measurement equipment
you are using, what you have done, what code you are using, how you made
your?measurements, and what those measurements are.
Best Regards,
Jerry, KE7ER
toggle quoted message
Show quoted text
On Tue, May 18, 2021 at 09:41 PM, Sunil Lakhani wrote:
The easy bitx been successfully build by many hams in India and abroad?
I shall be posting links and DDS sketch soon.?
Mr Arora is building bitx for first time.
I advised him to strictly follow the manual .
But he is porting the code with some other sketch which we do not recommend.
Since he is an engineer I do not doubt his knowledge.?
But first build basic kit . Take some help from some ham who is a good home brewer .
Second don't change the transistors untill you have completed the kit . Then experiment?
We shall post some working easy bitx build by hams around the?world.
I have build a dozen of easy bitx for 40mt as well as 20mt.
Last year made many contacts including dx just with 2 watts hi hi?
?
Here is first link see how well the DDS works
?
?
We shall be posting more info soon .
?
Best regards
Sunil vu3sua?
|
Re: #ubitxv6-help Adding the W2AEW AGC to the uBitx v6
#ubitxv6-help
The big advantage of the circuit you have chosen is that it is portable between
different pieces of equipment, just plug it into the headphone jack.
You do need to supply 12v to it somehow, and it needs its own amplifier.
A search for "LM386 Module" will find a very cheap amplifier that should be suitable.
Jerry, KE7ER
toggle quoted message
Show quoted text
On Tue, May 18, 2021 at 10:59 PM, Michael wrote:
Jerry,
thank you very much. This is most helpful.
I think I'm going to buy AA 143 germanium diodes. Strange that they are 1,35€ each in comparison to the 0,04€ for each transistor.
Will keep you in the loop!
73
Michael
|
Transistors are all compatible.
The Hfe of stock transistors is barely between 150-190
The 550c that I have put have a fairly equal compatibility. Original Bitx design says all transistors to be 547s (which is also 550 Equivalent)
except Q1 which has to be 2sc2570A in our case BF494.
--
|
CRO is 30MHz. I am pretty sure it can do 9Mhz by nyquest theorem.
Also 14 or 13 Mhz atleast by the same crude logic.
Why would BFO and VCO shift when only one is altered?
--
|
Re: #ubitxv6-help Adding the W2AEW AGC to the uBitx v6
#ubitxv6-help
Jerry,
thank you very much. This is most helpful.
I think I'm going to buy AA 143 germanium diodes. Strange that they are 1,35€ each in comparison to the 0,04€ for each transistor.
Will keep you in the loop!
73
Michael
|
It appears that things have been mixed. BFO should be near about 9.996 Mhz and not 9.96. Measure frequency for VFO at 17 Mhz for 40mtrs and 4 Mhz for 20 mtr version? An oscilloscope shall be inadequate for precise frequency measurements.? Seek help of experienced homebrewer having access to a frequency counter.?
On Wed, 19 May 2021 at 10:11 am, Sunil Lakhani <vu3sua@...> wrote: The easy bitx been successfully build by many hams in India and abroad? I shall be posting links and DDS sketch soon.? Mr Arora is building bitx for first time. I advised him to strictly follow the manual . But he is porting the code with some other sketch which we do not recommend. Since he is an engineer I do not doubt his knowledge.? But first build basic kit . Take some help from some ham who is a good home brewer . Second don't change the transistors untill you have completed the kit . Then experiment? We shall post some working easy bitx build by hams around the?world. I have build a dozen of easy bitx for 40mt as well as 20mt. Last year made many contacts including dx just with 2 watts hi hi?
Here is first link see how well the DDS works
?
We shall be posting more info soon .
Best regards Sunil vu3sua?
|
The easy bitx been successfully build by many hams in India and abroad? I shall be posting links and DDS sketch soon.? Mr Arora is building bitx for first time. I advised him to strictly follow the manual . But he is porting the code with some other sketch which we do not recommend. Since he is an engineer I do not doubt his knowledge.? But first build basic kit . Take some help from some ham who is a good home brewer . Second don't change the transistors untill you have completed the kit . Then experiment? We shall post some working easy bitx build by hams around the?world. I have build a dozen of easy bitx for 40mt as well as 20mt. Last year made many contacts including dx just with 2 watts hi hi?
Here is first link see how well the DDS works
?
We shall be posting more info soon .
Best regards Sunil vu3sua?
|
Re: Bonehead mistake, hard to detect
The C compiler my company marketed had a Picky Flag that could be
set from 0 to 10. Level 10 was infuriating. Indeed, Level 7 said
that any_ printf()_ call had to be of the form:
_ successfulConversionsMade = printf("whatever...");_
*** Wow. That *is* fussy. Could you at least cast it to (void)? - Jerry
|
Re: Bonehead mistake, hard to detect
Warnings are a mixed blessing. It is so frustrating to be not able to eliminate them.? I have a similar struggle with kicad, the pcb design software. I dont understand much of it but, there is a sanity check that throws up all kinds of warnings with no clue as to what's causing it.? I have suffered bad pcbs long enough to know not to ignore them. - f
The C compiler my company marketed had a Picky Flag that could be set from 0 to 10. Level 10 was infuriating. Indeed, Level 7 said that any printf() call had to be of the form:
??? successfulConversionsMade = printf("whatever...");
Most felt this was a tad too fussy, so most people ran at level 4 until production was ready. Several customers tried to shoot us...
Jack, W8TEE
On Tuesday, May 18, 2021, 9:29:13 PM EDT, Gerald Sherman < ve4gks@...> wrote:
Just as an aside - I used to do CNC programming in the RS-274
G-Code language.? We had a graphic analyser that ran on a PC, but
there were a few discrepancies between how the analyser ran and
how the machine ran.? I could tell a few stories.
Gerry
Sent by the Thunderbird
On 2021-05-18 7:48 p.m., Tom, wb6b
wrote:
On Sun, May 16, 2021 at 01:40 PM, jerry@... wrote:
Absolutely. I always ran gcc in "pedantic". Any bug
that the warnings find - is a freebee.
This is a very good idea for the development phase, but be careful
in the production phase.
I was contributing to a Google open source project. One of the
Google developers, for software religious reasons decided that the
-Wall complier needed to be set. But, the developers were one
compiler revision behind from what people setting up a fresh
development environment were using.?
The next push to Github and dozens or more of company projects
that incorporated this Google project crashed to the ground. This
release did have some other important enhancements and bug fixes
that users were waiting for.?
The -Wall switch turned a new compiler warning about something
that wasn't previously caught, but considered bad practice, to be
turned into a hard error, so the code would no longer compile.
This warning, while a good idea to invest some time to correct on
the development side had zero adverse effect on the code people
were running in their production environments.
Anyway I published a fast way to get back running, a SED script
that found the hardcoded (yes they hardcoded the new switch in)
-Wall switches in Google's home grown build system. This fixed the
problem and people were back in business while the Google
developer who did this, dug-in and fiercely defended how correct
he was to do this.?
The fact that people needed their systems to continue to work now,
did not seem to be relevant to him.
Also most of the users were "Data Scientist" with some systems
skills, so this fix was more actionable and simple than more hard
core experimenting with mixing and matching compilers and code
releases, for them.?
Tom, wb6b
--
Jack, W8TEE
|
Re: Bonehead mistake, hard to detect
The C compiler my company marketed had a Picky Flag that could be set from 0 to 10. Level 10 was infuriating. Indeed, Level 7 said that any printf() call had to be of the form:
??? successfulConversionsMade = printf("whatever...");
Most felt this was a tad too fussy, so most people ran at level 4 until production was ready. Several customers tried to shoot us...
Jack, W8TEE
On Tuesday, May 18, 2021, 9:29:13 PM EDT, Gerald Sherman <ve4gks@...> wrote:
Just as an aside - I used to do CNC programming in the RS-274
G-Code language.? We had a graphic analyser that ran on a PC, but
there were a few discrepancies between how the analyser ran and
how the machine ran.? I could tell a few stories.
Gerry
Sent by the Thunderbird
On 2021-05-18 7:48 p.m., Tom, wb6b
wrote:
On Sun, May 16, 2021 at 01:40 PM, jerry@... wrote:
Absolutely. I always ran gcc in "pedantic". Any bug
that the warnings find - is a freebee.
This is a very good idea for the development phase, but be careful
in the production phase.
I was contributing to a Google open source project. One of the
Google developers, for software religious reasons decided that the
-Wall complier needed to be set. But, the developers were one
compiler revision behind from what people setting up a fresh
development environment were using.?
The next push to Github and dozens or more of company projects
that incorporated this Google project crashed to the ground. This
release did have some other important enhancements and bug fixes
that users were waiting for.?
The -Wall switch turned a new compiler warning about something
that wasn't previously caught, but considered bad practice, to be
turned into a hard error, so the code would no longer compile.
This warning, while a good idea to invest some time to correct on
the development side had zero adverse effect on the code people
were running in their production environments.
Anyway I published a fast way to get back running, a SED script
that found the hardcoded (yes they hardcoded the new switch in)
-Wall switches in Google's home grown build system. This fixed the
problem and people were back in business while the Google
developer who did this, dug-in and fiercely defended how correct
he was to do this.?
The fact that people needed their systems to continue to work now,
did not seem to be relevant to him.
Also most of the users were "Data Scientist" with some systems
skills, so this fix was more actionable and simple than more hard
core experimenting with mixing and matching compilers and code
releases, for them.?
Tom, wb6b
-- Jack, W8TEE
|
Re: Bonehead mistake, hard to detect
Just as an aside - I used to do CNC programming in the RS-274
G-Code language.? We had a graphic analyser that ran on a PC, but
there were a few discrepancies between how the analyser ran and
how the machine ran.? I could tell a few stories.
Gerry
Sent by the Thunderbird
On 2021-05-18 7:48 p.m., Tom, wb6b
wrote:
toggle quoted message
Show quoted text
On Sun, May 16, 2021 at 01:40 PM, jerry@... wrote:
Absolutely. I always ran gcc in "pedantic". Any bug
that the warnings find - is a freebee.
This is a very good idea for the development phase, but be careful
in the production phase.
I was contributing to a Google open source project. One of the
Google developers, for software religious reasons decided that the
-Wall complier needed to be set. But, the developers were one
compiler revision behind from what people setting up a fresh
development environment were using.?
The next push to Github and dozens or more of company projects
that incorporated this Google project crashed to the ground. This
release did have some other important enhancements and bug fixes
that users were waiting for.?
The -Wall switch turned a new compiler warning about something
that wasn't previously caught, but considered bad practice, to be
turned into a hard error, so the code would no longer compile.
This warning, while a good idea to invest some time to correct on
the development side had zero adverse effect on the code people
were running in their production environments.
Anyway I published a fast way to get back running, a SED script
that found the hardcoded (yes they hardcoded the new switch in)
-Wall switches in Google's home grown build system. This fixed the
problem and people were back in business while the Google
developer who did this, dug-in and fiercely defended how correct
he was to do this.?
The fact that people needed their systems to continue to work now,
did not seem to be relevant to him.
Also most of the users were "Data Scientist" with some systems
skills, so this fix was more actionable and simple than more hard
core experimenting with mixing and matching compilers and code
releases, for them.?
Tom, wb6b
|
Re: Bonehead mistake, hard to detect
On Sun, May 16, 2021 at 06:56 PM, Jack, W8TEE wrote:
The warning was near the top of a project with 22 source code files.
I hate to think of the many time this has happened to me. Then there is warning overload, where you take a quick look, but warnings that may actually be important get lost in the noise. I wonder what programs/utilities may have been developed in recent time (last couple of hundred years) that can intelligently sort through compiler warnings to prioritize and highlight what may be best to look into first. Of course static code checkers help too. Like your check levels on your C compiler helped in this regard. Tom, wb6b
|
Re: Bonehead mistake, hard to detect
On Sun, May 16, 2021 at 01:40 PM, jerry@... wrote:
Absolutely. I always ran gcc in "pedantic". Any bug that the warnings find - is a freebee.
This is a very good idea for the development phase, but be careful in the production phase. I was contributing to a Google open source project. One of the Google developers, for software religious reasons decided that the -Wall complier needed to be set. But, the developers were one compiler revision behind from what people setting up a fresh development environment were using.? The next push to Github and dozens or more of company projects that incorporated this Google project crashed to the ground. This release did have some other important enhancements and bug fixes that users were waiting for.? The -Wall switch turned a new compiler warning about something that wasn't previously caught, but considered bad practice, to be turned into a hard error, so the code would no longer compile. This warning, while a good idea to invest some time to correct on the development side had zero adverse effect on the code people were running in their production environments. Anyway I published a fast way to get back running, a SED script that found the hardcoded (yes they hardcoded the new switch in) -Wall switches in Google's home grown build system. This fixed the problem and people were back in business while the Google developer who did this, dug-in and fiercely defended how correct he was to do this.? The fact that people needed their systems to continue to work now, did not seem to be relevant to him. Also most of the users were "Data Scientist" with some systems skills, so this fix was more actionable and simple than more hard core experimenting with mixing and matching compilers and code releases, for them.? Tom, wb6b
|
I don't have instruments just LCR frequency meter- Tip RF- only basic wattmeter was more from experience in assemblies that I adjusted and it was very good at 40m voce pode? de add no Whatzapp? ?+5564999629242 para ver se eu te ajudo mais ok?
yea all voltage measurements seem fine as per the chart.
Do you have a CRO and can you help with
1)Waveforms of BFO and VFO individually
2)Can you change VFO and see whether BFO changes and vice a versa?
Thanks and Good Luck
--
--
Atenciosamente.
Carlos Fraga
|
yea all voltage measurements seem fine as per the chart.
Do you have a CRO and can you help with
1)Waveforms of BFO and VFO individually
2)Can you change VFO and see whether BFO changes and vice a versa?
Thanks and Good Luck
--
|
Hello everyone, I already configured the 3 E-bitx all working very well. They were assembled strictly in accordance with the manual and prior to the placement of the BPF and the toroidal inductors were all measured to certify the quality of the radio. Turn on the radio and press the encoder button for 1 second and you will be in the IF configuration mode. you can put it there to try 9,999,960 and press again for 1 second to enter VFO mode, so you must listen to a station at a certain frequency you are editing. the VFO works accordingly, you must calibrate according to the library what you can do after solving this. If your BPFis poorly calibrated, it will interfere with the result of your receipt. I want to understand that you made all the measurements of the transistors and must have done the test by the C50 directly with the antenna for RX. Any questions you can talk to me in private to not fill in the topic and then we summarize the results to let people know greetings Carlos -Brazil- PT9EB
--
Atenciosamente.
Carlos Fraga
|
Michael DK1MI/N1BSD
Sunil Lakhani