On Fri, Jun 30, 2017 at 09:58 am, Allard PE1NWL wrote:

Well, I didn't need much time to find and fix this stupid bug.

Thanks! Glad to be of help!
?
--
John - WA2FZW

开云体育

I bought 2 nice displays on eBay. 3.2"

2-3 days Fun Invested.? Very complicated and confusing.? Parts of Demos worked others did not.

I could not even understand people trying to help me on the arduino forum.

Buy what Jack says "MCUFriend" Library compatible, that is what he is using.? Make sure you get pin arrangement he is using.

I DIDN'T! Sad........

Mike, WA6ISP

Steve ,

There are few in the works.
W8TEE , Jack is working on some code.
He has the display done. So many are waiting for his code.? A very talented coder.

There are some Russian and other hams from Japan with some . Both are on youtube

PD8W also has developed some code.
Nice display. Unfortunately he has not finished the code and cant seem to contact him.
I played with it and the display on the tft was very nice and the code for display works fine with my tft's and atmega2560.
Unfortunately the buttons to control other options need work.

Joe
VE1BWV

On Fri, Jun 30, 2017, 3:09 PM Steve Greer <km4ous@...> wrote:

Has anyone written code to use TFT display i keep searching but not finding anything.? If someone could point me in the correct direction that would be great thx.

-- 
Mike Hagen, WA6ISP
10917 Bryant Street
Yucaipa, Ca. 92399
(909) 918-0058
PayPal ID  "MotDog@..."
Mike@...

--

开云体育

Paypal or check is fine.? I get get gigged about $2 by paypal, so please add it if mPaypal.

I will? be frantically working the 4th of July to catch up when parts arrive from Mouser Monday!

Option is if you want Nano.? I have 5 new ones coming next week too.

Thanks Mike

?

--

Steve ,

There are few in the works.
W8TEE , Jack is working on some code.
He has the display done. So many are waiting for his code.? A very talented coder.

There are some Russian and other hams from Japan with some . Both are on youtube

PD8W also has developed some code.
Nice display. Unfortunately he has not finished the code and cant seem to contact him.
I played with it and the display on the tft was very nice and the code for display works fine with my tft's and atmega2560.
Unfortunately the buttons to control other options need work.

Joe
VE1BWV

What an interesting board - thanks, Mike. Sign me up for one, when you have a link to purchase. If not PP, how do you like to get paid?

Has anyone written code to use TFT display i keep searching but not finding anything. ?If someone could point me in the correct direction that would be great thx.

Yes, that is confusing. ?Can probably ignore it.

My guess the intent is that the speaker/headphones should be wired up directly to the speaker/headphone connector on the Bitx40, and that the ground wire from Bitx40 to speaker should not go anywhere else. ?If, for example, you ran the ground return black wire from the speaker over to the ground on the incoming power connector, fluctuations in supply current causing a voltage drop between that power connector and the Bitx40 ground plane would show up in the headphones. ?Though I doubt that would be much of a problem. ?If you wired up the microphone that way it could indeed be a problem, as peak voltage there is only 100mv or so and we are now sensitive to power supply currents during transmit..
Jerry, KE7ER

There was a small bug in v1.17 which caused the radio to return to an incorrect frequency when switching VFO's, RIT, SPLIT, FINE TUNE, etc.
I have fixed this and released a corrected version v1.17.1 via

73 Allard PE1NWL

Hello I don't really understand what does this mean. The black speaker thing

Note:
Don't solder the ground (black) wire of the speaker to the ground. It should only connect to the speaker or the earphone jack.
You may optionaly route the audio through the supplied stereo earphone jack to the speaker such that if you plug in the earphones/headset the speaker will disconnect. This is left as an exercise to you.


http://www.hfsigs.com/bitx40v3_wireup.html

On Fri, June 30, 2017 18:17, Allard PE1NWL wrote:

John, thanks for notifying!
I just tried it myself, there's indeed something wrong - probaby just a
small bug - I'll check it tonight.

Well, I didn't need much time to find and fix this stupid bug.
Found a typo in the shiftBase() routine and corrected it immediately.
Just released a corrected version Raduino v1.17.1 on


73, Allard PE1NWL

Changing the value of C124, originally 47 uF to a 4.7 uF will reduce the duration of the PTT TX burst from about 60 ms down to about 20 ms. ?This is shorter than the dot length of 30 WPM CW, so the remaining burst is covered up by the first dot or dash that is sent. ?Originally it was so long that it made a dot sound like a dash at higher speeds.

I agree that powering that stage on/off is not optimal and is absolutely the source of the problem. ?A preamp stage would probably be good anyway, and that could be switched on/off.

73, Bob, WB4SON

On Fri, June 30, 2017 16:57, John P wrote:

But I find that after using the "Fine Tune" function, the next time I move
the tuning dial (back in "Normal" mode), the frequency jumps to some
seemingly random value.

John, thanks for notifying!
I just tried it myself, there's indeed something wrong - probaby just a
small bug - I'll check it tonight.

73 Allard PE1NWL

Hans,?

I inserted a 10ms delay between individual i2c register writes.
Varied frequency between 6999950 and 7000050 in 1hz steps.

Nice clean tone on the receiver, no glitches on scope.

When dumping the registers, noticed that the values don't jump much on integer transitions of "a".
The register value calculations operating on a,b,c smooth that over.

Jerry, KE7ER

On Fri, Jun 30, 2017 at 07:57 am, John P wrote:

I just added the Spot/Fine Tune button this morning and loaded V1.17 into the rig.

Oops! I forgot to mention that I skipped over V1.16, so the same issue might also be in that version.
?
--
John - WA2FZW

I just added the Spot/Fine Tune button this morning and loaded V1.17 into the rig.

It works (almost)?great! As I had posted in the release notification thread, I thought that 1 Hz tuning in this mode might be too fine, but it's ok (IMHO).

But I find that after using the "Fine Tune" function, the next time I move the tuning dial (back in "Normal" mode), the frequency jumps to some seemingly random value. I would suspect that as soon as I move it, the software is reading the voltage and moving the frequency based on the difference in voltage between?the last known setting of the main tuning and where it is after moving the dial to perform the "Fine Tuning" function, as opposed to remembering the frequency I had set with the fine tuning. and associating that frequency with the voltage from the tuning pot.

--
John - WA2FZW

Yup, delays on those i2c writes could be revealing. ?Occurred to me but I haven't gotten around to it. ? ?But I did put a scope on it, looked at the 7mhz waveform with 5ms of delayed sweep after triggering on an edge. ?Seemed clean. ?The important thing for me is it sounds clean on the SW receiver, even when going through a transition between one integer and the next.

On p20 of the Si5338 datasheet ? ?
they quickly mention how they clean up those edges. ?I'd guess the mechanism is the same as the phase adjustment they make available to us, which is not infinitely accurate.?
> ? ?To eliminate phase error generated by this process, the MultiSynth block calculates
> ? ?the relative phase difference between the clock produced by the fractional-N divider
> ? ?and the desired output clock and dynamically adjusts the phase to match the ideal clock waveform.
In the next paragraph they mention how it's good for any frequency up to vco/8.0, and then integer divides of 6 and 4. ?Just like the Si5351. ?At $10, the Si5338 was apparently able to afford a tech writer. ?So the Si5338 docs might be a good way to fill in holes left by the Si5351 docs.

Jerry, KE7ER