Keyboard Shortcuts
Likes
- BITX20
- Messages
Search
Re: Snap Crackle Pop
Heatsink shorted to ground sounds right. ?The flash of light was likely one of the traces blowing between PA 12v and the IRF510 blowing. ? Make sure the heatsink is not shorted, then gingerly apply power (perhaps through a fuse of ?2 Amps) into PA 12v. ?Check to see if 12v is getting to the top of the IRF510 (the IRF510 mounting tab and heatsink are connected to the drain, which is connected by traces to L8). ?You should see 12v on the drain even when in receive mode. ?If not, you have a trace to patch. ?Or possibly the wire around L8. ?Either should be easy to repair. ? On Sun, Apr 9, 2017 at 10:35 am, Jonathan Peakall wrote:
When I got mine the heat sink had an intermittent short to ground. Luckily it wasn't dead shorted and I was running it on a current limiting supply. I removed it, filed enough off the bottom to be able to place double layer of tape and then put it back. I'd check to see if you have a short on the heat sink. ? |
Re: VFO/BFO selecting outputs
Ah, here's that bug I was warning you about. That last line of the three lines of code should end with _CLK0, ?not _CLK2. On Sun, Apr 9, 2017 at 09:40 am, Jerry Gaffke wrote:
si5351.set_freq(11998500L*100ULL , SI5351_PLL_FIXED, SI5351_CLK2); ? |
Re: Snap Crackle Pop
Ouch!
toggle quoted message
Show quoted text
When I got mine the heat sink had an intermittent short to ground. Luckily it wasn't dead shorted and I was running it on a current limiting supply. I removed it, filed enough off the bottom to be able to place double layer of tape and then put it back. I'd check to see if you have a short on the heat sink. Jonathan On 4/9/2017 9:58 AM, Josh Walton via Groups.Io wrote:
That¡¯s the sound I heard when I first powered up my beautiful BITX40. I immediately cut the power, traced all my connections, everything looked great. Cautiously I applied power and turned on the radio, it tuned in perfectly. After some playing around I tried to transmit¡ nothing. No power out. Well I guess it was the transmit circuits that made the pop sound when I powered it up. |
Re: VFO/BFO selecting outputs
¿ªÔÆÌåÓýJerry,
>>The VFO_A and VFO_B defines are just an integer used to remember what frequency we are currently operating on Duh. I should have figured that out. Gee, ya mean like every radio with a VFOA and VFOB? As for the rest, thanks. Detailed and cogent. That gives me enough information to get into trouble! :-) >> But haven't compiled and tried it, might be sending you off with a bug or two. How dare you. When I demand help I expect it to be perfect. Next time be prepared to make a house call, bring a thumb drive with the sketch and beer. ;-) Jonathan On 4/9/2017 9:40 AM, Jerry Gaffke via Groups.Io wrote:
|
Snap Crackle Pop
That¡¯s the sound I heard when I first powered up my beautiful BITX40. I immediately cut the power, traced all my connections, everything looked great. Cautiously I applied power and turned on the radio, it tuned in perfectly. After some playing around I tried to transmit¡ nothing. No power out. Well I guess it was the transmit circuits that made the pop sound when I powered it up.
I believe the source of the snap pop (a minor flash too) was close to the PA-PWR input, close to the larger black torrid and the heat-sinked transistor. There is no visual damage on the components or board. Any ideas on how to trouble shoot? Oh, just a note, the power supply was a powerwerx switching power supply, so nice and clean. Any help would be great! Thanks! Josh KK4LGZ |
Re: VFO/BFO selecting outputs
OK, I'll take a stab at this. ?But haven't compiled and tried it, might be sending you off with a bug or two. The VFO_A and VFO_B defines are just an integer used to remember what frequency we are currently operating on. ?This is not fully implemented. ?If it were, you could push a button and flip from talking to your friend at 7.175 with VFO_A and see what the traffic net is doing at 7.270, for example. ?Then push the button again and get back to your friend at 7.175. ?Twiddling the tuning knob changes the frequency of whatever VFO you have currently selected. ?There is of course only one VFO, and it always comes out of channel 2 of the Si5351. ?The Nano sketch is remembering those two VFO frequencies, and toggling the Si5351 frequency out of channel 2 when you press the button. ? In summary, your on the wrong track. Let's assume we leave the VFO at Si5351 channel 2 and put the BFO at Si5351 channel 0. ?Channel 1 is left unused, and is turned off. ?You can probably figure out how to add a piece of coax to channel 0, perhaps just solder it directly into the back of the Raduino board. Add this code to the bottom of the setup() function in the sketch: //si5351.drive_strength(SI5351_CLK0, SI5351_DRIVE_2MA); si5351.output_enable(SI5351_CLK0, 1); si5351.set_freq(11998500L*100ULL , SI5351_PLL_FIXED, SI5351_CLK2); Then wire up your coax as Pete suggested here, and see if it works: ?/g/BITX20/topic/4703461 The BFO frequency is set to 11.9985 MHz. ?You probably want to adjust that somehow until you get the best audio when receiving a station. ?The value is given in Hz with a final L to tell the compiler that this is a long integer of 32 bits, not just 16 bits. ?I'm following Farhan's lead and multiplying that by 100ULL, which is a really big integer of 64 bits (an unsigned long long) but only has a value of 100. ?The extra factor of 100 is needed because the Si5351 library takes frequencies in hundredth's of one Hz just in case you care about being that precise. ?An unsigned 32 bit integer can deal with numbers up to a max of 2**32 - 1 = 4294967295, so big enough to tell the Si5351 about a frequency of up to 42.9 MHz. ?So that code could also be written as 11998500UL * 100, or as 1199850000UL. ?But then I haven't tried it. ?The "U" tells the compiler that this is an unsigned (positive) number so the bit normally used to store the sign (the + or -) can be used instead to deal with numbers twice as large. The drive_strength line above has been commented out with the two leading slashes. ?If you remove the slashes then the Si5351 will drive your channel 0 coax with a 2 ma output buffer. ?You could also try 4ma and 8ma. ? Not terribly obvious what that value should be. ?Too little drive into the demodulator and there may be intermodulation distortion. ?I doubt there's any consequences for driving at the max of 8ma, those diodes should have no trouble handling 8ma. ?But I could be wrong. ? Ideally, the 11.9985 value could be changed during the calibration sequence by pressing a button and turning the tuning knob, the BFO frequency displayed in the LCD. ?When the button is released the BFO frequency gets stored to EEPROM, where it can be read by setup() the next time the rig is powered up. ?That's left an exercise for the reader. Jerry, KE7ER On Sat, Apr 8, 2017 at 12:35 pm, Jonathan Peakall wrote:? Getting ready to convert over to using the si5351 for the BFO. I'd like to use rg-174 for both the VFO and BFO lines. The Si5351 has three outputs. The first is already routed on the PCB to the SIP header making it inconvienent to solder coax to it. Is there any reason that I can't use the two other Si5351 outputs that aren't used? That would be easy to solder to. And if so do I change the sketch like: ? |
Bitx-40 S meter
Hi all I have been looking to add a s meter to my bitx 40. Looking on Goggle for a simple s meter circuit and came across one that can connect to the raduino A2 pin https://1.bp.blogspot.com/-r1nfdAF5utY/WHuP9-bzXAI/AAAAAAAAbfs/be-Xrbvh7Fgx2PLSAB-aQ8M3egPGJfdcACLcB/s1600/Nd6t%2Bs%2Bmeter.jpg Now I am not that clever with the codes for the raduino and find it very difficult to add this or that and not knowing where in the program to put said new snip of code. Sorry if this has been covered before but I am struggling with this. |
Re: VFO/BFO selecting outputs
¿ªÔÆÌåÓýThanks for the coax info. The 174 I
have is small enough for the job, although I'll get some of the
178. However, my real question was about how to change the code to
change which Si5351 output I use.
Also, looking for how to enable the raduino BFO. Thanks! On 4/8/2017 3:32 PM, Jerry Gaffke via Groups.Io wrote:
|
Re: Transmit audio
Should read: ? This method is preferred, as it could let you adjust the BFO using the tuning pot just like you currently adjust the VFO. On Sun, Apr 9, 2017 at 06:55 am, Jerry Gaffke wrote:
This method is preferred, as it could let you adjust the BFO using the tuning pot just like you currently adjust the BFO. ? |
Re: Transmit audio
No procedure has been described for adjusting the carrier (same as the bfo) frequency. One way is to add a 100pf variable cap at C103 (currently not stuffed) and adjust that cap for best performance. ?Could remove C102 if you need to go the other direction in frequency (alternately add an approximately 4uH coil at L5).? The other way is Pete's method of using CLK0 from the Si5351 to replace the analog BFO: ?/g/BITX20/topic/4703461? ? ?This method is preferred, as it could let you adjust the BFO using the tuning pot just like you currently adjust the BFO. ?But not yet fully supported, as I don't think anyone has posted a known good sketch for it yet, and the best way to wire CLK0 into the Bitx40 has not yet been resolved. ?(I suspect it should use the resistor network from the uBitx) On Sun, Apr 9, 2017 at 06:20 am, <pierre@...> wrote: I would check to carrier adjustment with respect to the filter passband. ?On Sun, Apr 9, 2017 at 05:51 am, Raj vu2zap wrote: Your BFO may be off, |
Re: Tuning with Si5351 and Rotary encoders
To figure out which Nano pins get used, look at the schematic here: ? and also the Wireup diagram at the top of this page: ? Only those Raduino connector pins with wires to them in the Wireup diagram are used in the standard firmware. The two I2C pins go to the Si5351 as shown in the schematic, the pin numbers get called out down inside the Si5351 library so you won't see them. There are several extra pins called out in the standard firmware, anything not shown in the Wireup diagram is not currently used. On Sun, Apr 9, 2017 at 02:53 am, Weddig, Henning-Christof wrote:
? |
Re: Transmit audio
Michael,
toggle quoted message
Show quoted text
Monitoring your transmit audio in station with a second receiver is notoriously difficult because of the proximity of the transmitter and monitoring receiver. Your transmitter is outputting watts and the monitoring receiver has sub-microvolt sensitivity resulting in the receiver being swamped by the transmitter output. What you are probably listening to are extraneous noises being picked up by the microphone which at close range (within your station) are strong enough to swamp your receiver. I have found that if you can have a nearby station monitor your transmissions, record them and then play them back to you this works a lot better, although it is a bit tedious. You make adjustments and listen to the result played back to you. Some of the more expensive transceivers have record facilities which make this a lot easier, but it works best if it is done at a distance. There could be a number of reasons for your poor transmit audio. I would check to carrier adjustment with respect to the filter passband. If that doesn't improve the transmit audio then have a look at the mic. Best of luck, Peter VK1XP On 09-04-2017 22:24, Michael Davis wrote:
Hi, while checking my transmit audio quality (getting muffled |
Re: Transmit audio
Your BFO may be off, that's why you are sounding muffled and that would also give you a carrier leak.
toggle quoted message
Show quoted text
Check the BFO frequency, mine is at 11.9985 MHz approx. At 09/04/2017, you wrote:
Hi, while checking my transmit audio quality (getting muffled reports), I disconnected my Icom's antenna, set both the Icom and Bitx (on a 40 meter dipole) to the same frequency and listened to transmissions on the Icom. What I noticed was an S7 or 8 when keyed but not talking? In ssb, shouldn't the S meter be close to or at zero unless modulated by my voice since there is no carrier. Could someone please check for me in case it's some kind of thing that happens in such close proximity to each radio. Thanks |
Transmit audio
Michael Davis
Hi, while checking my transmit audio quality (getting muffled reports), I disconnected my Icom's antenna, set both the Icom and Bitx (on a 40 meter dipole) to the same frequency and listened to transmissions on the Icom. What I noticed was an S7 or 8 when keyed but not talking? In ssb, shouldn't the S meter be close to or at zero unless modulated by my voice since there is no carrier. Could someone please check for me in case it's some kind of thing that happens in such close proximity to each radio. Thanks |
Re: Tuning with Si5351 and Rotary encoders
Weddig, Henning-Christof
One big question: if i use only an Arduino Nano to which Pins do i have to connect the LCD pushbutton and SI5351? In the Code some Pins are named, but I am missing the connection to the SI5351. I tried to find out using some Pictures I found on the net, but These are too controversy. BTW: the Code could be compiled. Henning Weddig DK5LV? From: "Jack Purdum via Groups.Io" <econjack@...> To: [email protected] Sent: Sunday, 9 April, 2017 05:59:43 Subject: Re: [BITX20] Tuning with Si5351 and Rotary encoders Eric: What happens if you change this: ? ? ? ? ? ? ? ? if (get_button())? ? ? ? ? ? ? ? ? { to this: ? ? ? ? ? ? ? ? if (!digitalRead(ENCODER_BTN)) ? ? ? ? ? ? ? ? { In fact, get rid of get_button(). Also, I don't like to call functions within an ISR. The reason is because it's possible for one of those functions to call something that itself has an interrupt, leading to a blocking condition. Instead, define a volatile int variable at the top: volatile int dir; Also, you don't need to pass dir into?set_frequency() since it's now a global int?and modify your ISR to: ISR(PCINT2_vect) { ? unsigned char result = r.process(); ? if (result == 0) { ? ?dir = 0; ? ?return; ? } ? if (result == DIR_CW) { ? ? dir = 1; ? } else { ? ? dir = -1; ? } } Then, at the top of loop(), write: void loop() { ? ?if (dir) { ? ? ? ? ? ? ? ? ? ? ? ? // Only call if encoder rotated ? ? ?set_frequency(dir); ? ? ?display_frequency(); ? ? } ? ?// rest of code, and uncomment the new button reading code You may need to comment out the set_frequency() and display_frequency() in the if (changed_f) block as it might cause flickering. I also added a debug symbolic constant. If you comment out the #define DEBUG at the top of the program and use the F() macros I've added, the code size goes from 16512 bytes of flash and 699 bytes of SRAM down to 15578 and 468. Not much, but it might make a difference down the road. The modified file is attached. I cannot test it because I don't have the Raduino hooked up to my BITX40. Let me know if it works and, if not, the errors you see. Jack, W8TEE From: Eric Torraca <eric.torraca@...> To: [email protected] Sent: Saturday, April 8, 2017 7:53 PM Subject: Re: [BITX20] Tuning with Si5351 and Rotary encoders Thanks Pete, but that code doesn't work for me. At least, not without some modifications. To be fair, what I have doesn't work without modifications too, but I think you must have some buttons that I don't. At any rate, I've made a minor discovery. If Jack or someone could check out what I'm seeing. If I comment out the if (get_button()) section at the end of the main loop, I get a live tune. The bad news is I can't change frequency increments. I'll attach the latest version. Anybody have any tips? Also, I'm finding that if I tune too fast the LCD blinks out and won't return until I power down and restart. Is there a software fix for that?? 73 de KB1VNA Eric |
shipping options, raduino, source code and website updates
comrades, i have a few updates to tell you guys 1. hfsigs will now ship through DHL. that means you will get your radio within a week with full tracking. this costs $10 extra. if you want to save, the old shipping option is available too. gives you both options. 2. raduino is now available to be bought separately at $25. i have a number of raduino based projects that will bring online soon. if you dabble with other arduino projects or use the Si53551 in any other radios, this might be an excellent idea : it allows you to write your own code to do whatever you want it to. 3. the mystery of the bullet 5 in the bitx40 alignment is solved. instead of closing the </li> i had typed <li>. i have fixed it. many thought that that's where he elusive RV136 was explained. that is now fixed too. the station 10-1/2 is now in plain sight. 4. i have synced the bitx40 source code to what is being shipped on github. - f |
Re: USB/LSB operation
You are welcome to take what I got in the User's Manual. What was said about Jerry is right. Trolling the archives today showed me a lot of things I didn't know about before. Ugly things. Like before me ugly things. And I saw complex bewildering smart things. Just recently with speech compression conversations, then Farhan dropping another tidbit to collectively ponder, and the USB/LSB mod and hack. Now a User's Manual to poor my rantings into like a busy work thing. I am feeling a little overwhelmed, and in way over my head. I'll go and get back to my dungeon to work some more on the Manual here in a bit. This is for any and all here to listen. Someone I respect once told me, The best way to kill a hobby is to take a class for it. Then another one just recently at our meeting and dinner told me I should see about some electronics courses. So, I am inviting you all, everyone, to tell me about some good ways or places to start with a good foundation edumacation so I can catch up quickly? I took some fast track Comptia classes like A+, Network+, Security+. And MCSA/MCSE back in 2003 & 04 too. ?? And finally. How is my Email address getting around? I have had 4 senders and 8 messages so far. I didn't know that was possible.? |
Re: Tuning with Si5351 and Rotary encoders
Jack Purdum
Eric: What happens if you change this: ? ? ? ? ? ? ? ? if (get_button())? ? ? ? ? ? ? ? ? { to this: ? ? ? ? ? ? ? ? if (!digitalRead(ENCODER_BTN)) ? ? ? ? ? ? ? ? { In fact, get rid of get_button(). Also, I don't like to call functions within an ISR. The reason is because it's possible for one of those functions to call something that itself has an interrupt, leading to a blocking condition. Instead, define a volatile int variable at the top: volatile int dir; Also, you don't need to pass dir into?set_frequency() since it's now a global int?and modify your ISR to: ISR(PCINT2_vect) { ? unsigned char result = r.process(); ? if (result == 0) { ? ?dir = 0; ? ?return; ? } ? if (result == DIR_CW) { ? ? dir = 1; ? } else { ? ? dir = -1; ? } } Then, at the top of loop(), write: void loop() { ? ?if (dir) { ? ? ? ? ? ? ? ? ? ? ? ? // Only call if encoder rotated ? ? ?set_frequency(dir); ? ? ?display_frequency(); ? ? } ? ?// rest of code, and uncomment the new button reading code You may need to comment out the set_frequency() and display_frequency() in the if (changed_f) block as it might cause flickering. I also added a debug symbolic constant. If you comment out the #define DEBUG at the top of the program and use the F() macros I've added, the code size goes from 16512 bytes of flash and 699 bytes of SRAM down to 15578 and 468. Not much, but it might make a difference down the road. The modified file is attached. I cannot test it because I don't have the Raduino hooked up to my BITX40. Let me know if it works and, if not, the errors you see. Jack, W8TEE From: Eric Torraca <eric.torraca@...> To: [email protected] Sent: Saturday, April 8, 2017 7:53 PM Subject: Re: [BITX20] Tuning with Si5351 and Rotary encoders Thanks Pete, but that code doesn't work for me. At least, not without some modifications. To be fair, what I have doesn't work without modifications too, but I think you must have some buttons that I don't. At any rate, I've made a minor discovery. If Jack or someone could check out what I'm seeing. If I comment out the if (get_button()) section at the end of the main loop, I get a live tune. The bad news is I can't change frequency increments. I'll attach the latest version. Anybody have any tips? Also, I'm finding that if I tune too fast the LCD blinks out and won't return until I power down and restart. Is there a software fix for that?? 73 de KB1VNA Eric
|
Re: The Users User Manual
You are exactly right Jerry. Calibration gets the display on the same page as you and the other guy. Thank you. Writing detailed instructions is hard work. Lots of care must be taken to avoid confusion with someone seeing this stuff for the first time. That's why #5 and the refusal to put it in, upsets me.? I've has this post open on my screen for several hours now. I can't find what I want to show about the jacks, so I am having to draw it, and scan it, and watch tv too. So get ready for that. I am gonna cut it way back for the people who just want to know about the wiring points right now, then figure out the rest as they are putting it together.? |