Ok. Here is how I solved this.
i have completlyvredone the wiring keeping the negative sidew all togheter and positive ones all togheter.
not mixing grounds from other places!
|
Re: Bitx TFT display code
I came across your site and was looking all over to find some sample code but no joy. ?I'm very interested I will keep checking back.
|
Re: Si5351A: facts and myths
Hello Jerry
Your findings re the Si5351A slow register programming are fascinating to me. They kind of imply the Si5351A DOES double-buffer the registers! Amazing. I want to do lots more experiments myself, now. I love the way the understanding of this wonderful little $1 chip keeps being pushed forward - despite chronic lack of hard facts in the documentation.?
> Your older comment about floating point taking less flash than? > 64bit integer math was interesting.? I'd guess that if you have a > lot of computations, 64bit integer loses due to all of those 64 bit? > args getting bussed around, where standard floating point is? > just 32 bit per arg.? For just a couple computations the integer? > math might win, as the floating point multiply and divide? > subroutines are relatively large. ??
My experiences with this were based on a single line of code involving one floating point multiplication and one floating point division.?It actually was only a couple of computations, as you said - but the floating point STILL won.??
This was my original Si5351A code in the Ultimate3S QRSS/WSPR/etc transmitter kit an also later used in the other kits.?As the code evolved and code space ran out, I kept having to find places to compact the code and eventually came to the tricky one, getting rid of the floating point arithmetic. The easy thing to do was to replace it with 64-bit integers and that was when to my horror, I saw that the flash code space was even BIGGER! Just to be clear again: the entire rest of my code uses unsigned 8, 16 or 32-bit variables. This single line of code was the only place I used a float (or uint64_t).?
In the end I spent many hours headscratching with pen and paper, and Excel simulations, and finally the C code... and eventually managed to figure out some neat tricks to accomplish the arithmetic I needed, using only 32-bit, without losing any precision! When I'd done that and floating point libraries were gone from my code I reclaimed 5 or 6% of the Flash space if I recall (even after adding all my integer tricks).?
73 Hans G0UPL
|
Re: Bitx TFT display code
Do you have a hardware list for your project.. I did not see a listing on your site I want of make sure I have the correct type of tft or I need to order one..
Joe VE1BWV
On Fri, Jun 30, 2017 at 10:44 PM, SP Bhatnagar <vu2spf@...> wrote: Please have a look at my blog for TFT touch screen based vfo and bfo. The first version of code should be there soon. Blog is at
73 Vu2spf Bhatnagar
|
Re: Bitx TFT display code
Wow!, The features look great.... cant wait to try it out. Your website on the Colour TFT display and si5351 looks very interesting.
I like the idea of using the si5351
Thanks for the info Joe VE1BWV
On Fri, Jun 30, 2017 at 10:44 PM, SP Bhatnagar <vu2spf@...> wrote: Please have a look at my blog for TFT touch screen based vfo and bfo. The first version of code should be there soon. Blog is at
73 Vu2spf Bhatnagar
|
Re: Si5351A: facts and myths
Yes it is using the same SDA and SCL lines as the Si5351 just a different address. The display is a 5v one. I didn't know there was a choice. I separated the Nano and display so I could mount the Nano with the USB port at the rear of the case and use a 20x4 display. I wanted to add an S meter and maybe a output/swr meter so I wanted the additional lines. It made more sense to run only 4 wires to the front panel and it was pretty easy to change the sketch to accommodate the new display, only three or four lines to change.
Your other post about birdies I have not done a side by side comparison but I use the Bitx a lot for digital so I have tuned around on USB and it sure seems to have less birdies and what is there seem to be at a much lower level. ?
|
Fw: [BITX20] Bitx TFT display code
I forgot to mention that I bought the wrong Mega from AliExpress.
Jack, W8TEE
----- Forwarded Message -----
From: Jack Purdum <econjack@...> To: " [email protected]" < [email protected]> Sent: Friday, June 30, 2017 10:26 PM Subject: Re: [BITX20] Bitx TFT display code All:
I bought a Mega 2560 Pro Mini from RobotDyn and it does NOT fit my PCB.
?
This is too bad, as it sell for about half the price of the one that does fit.
Jack, W8TEE
From: Joe <joeman2116@...> To: [email protected] Sent: Friday, June 30, 2017 5:51 PM Subject: Re: [BITX20] Bitx TFT display code In searching for tft displays, i noticed there were serial and parallel. The ones with connectors on the top and bottom are generally pin compatible with uno and atmega2560.? I have several of these and the 3.5" just plugged and Jacks display worked great.. These were mci friends type marked on the board. My other tft's were 2.8 inch.
One i had to change some text size for the display to look correct. The other 2.8 from elegoo was also mcufriend, but Jacks display code worked with no changes.
His code is able to identify several tft drivers and select the correct one.. Very cool.
The serial type tft usually have single set of pins - 8-10 pins. The usually say spi or serial in the description.
I see that some Japanese and Russian hams use these type.
Looking forward to Jack"s next code run...
Joe
VE1BWV
On Fri, Jun 30, 2017, 4:57 PM Jack Purdum via Groups.Io <econjack= [email protected]> wrote: My PCB uses the Mega 2560 Pro Mini because of its smaller footprint. I buy from Wideenm991 on eBay. The DDS module is a type II, as shown here:
but are getting hard to find. I can't find the guy who made an adapter board for a Type I to a Type II board (K5ESS??). He sells the adapter for about $2. My board looks like this:
You can see where the DDS and Mega boards go. The advantage of the board is that most of the I/O pins are brought out at the bottom and top of the baord for additional hacking. With the schematic I posted earlier today you should be able to "fit" things on the board.
Jack, W8TEE
Sent: Friday, June 30, 2017 3:20 PM
Subject: Re: [BITX20] Bitx TFT display code
Jack
I bought TFTs with the double connector on the
Right Hand side, to fit Mega 2560.
But some use the single pin headers across the
top and botom (Horz) of the Mega 2560?
I got confused over Mega 2560 compatibility?
Mike, WA6ISP
On 6/30/2017 11:59 AM, Jack Purdum via
Groups.Io wrote:
I've
had some setbacks at home, but am still trying to get things
going. I don't really use "buttons" on my display, as I am
not using a touch screen at this time. The mcufriend
displays should plug right into a standard Mega 2560 or my
TFT PCB. I should have the VFO working this weekend. The
schematic for my PCB is attached. You'll need the same
pinouts for my code to work with the display.
Jack,
W8TEE
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
On 6/30/2017
11:24 AM, Joe wrote:
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@...
--
Mike Hagen, WA6ISP
10917 Bryant Street
Yucaipa, Ca. 92399
(909) 918-0058
PayPal ID "MotDog@..."
Mike@...
|
Re: Bitx TFT display code
All:
I bought a Mega 2560 Pro Mini from RobotDyn and it does NOT fit my PCB.
?
This is too bad, as it sell for about half the price of the one that does fit.
Jack, W8TEE
From: Joe <joeman2116@...>
To: [email protected]
Sent: Friday, June 30, 2017 5:51 PM
Subject: Re: [BITX20] Bitx TFT display code
In searching for tft displays, i noticed there were serial and parallel. The ones with connectors on the top and bottom are generally pin compatible with uno and atmega2560.? I have several of these and the 3.5" just plugged and Jacks display worked great.. These were mci friends type marked on the board. My other tft's were 2.8 inch.
One i had to change some text size for the display to look correct. The other 2.8 from elegoo was also mcufriend, but Jacks display code worked with no changes.
His code is able to identify several tft drivers and select the correct one.. Very cool.
The serial type tft usually have single set of pins - 8-10 pins. The usually say spi or serial in the description.
I see that some Japanese and Russian hams use these type.
Looking forward to Jack"s next code run...
Joe
VE1BWV
On Fri, Jun 30, 2017, 4:57 PM Jack Purdum via Groups.Io <econjack= [email protected]> wrote: My PCB uses the Mega 2560 Pro Mini because of its smaller footprint. I buy from Wideenm991 on eBay. The DDS module is a type II, as shown here:
but are getting hard to find. I can't find the guy who made an adapter board for a Type I to a Type II board (K5ESS??). He sells the adapter for about $2. My board looks like this:
You can see where the DDS and Mega boards go. The advantage of the board is that most of the I/O pins are brought out at the bottom and top of the baord for additional hacking. With the schematic I posted earlier today you should be able to "fit" things on the board.
Jack, W8TEE
Sent: Friday, June 30, 2017 3:20 PM
Subject: Re: [BITX20] Bitx TFT display code
Jack
I bought TFTs with the double connector on the
Right Hand side, to fit Mega 2560.
But some use the single pin headers across the
top and botom (Horz) of the Mega 2560?
I got confused over Mega 2560 compatibility?
Mike, WA6ISP
On 6/30/2017 11:59 AM, Jack Purdum via
Groups.Io wrote:
I've
had some setbacks at home, but am still trying to get things
going. I don't really use "buttons" on my display, as I am
not using a touch screen at this time. The mcufriend
displays should plug right into a standard Mega 2560 or my
TFT PCB. I should have the VFO working this weekend. The
schematic for my PCB is attached. You'll need the same
pinouts for my code to work with the display.
Jack,
W8TEE
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
On 6/30/2017
11:24 AM, Joe wrote:
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@...
--
Mike Hagen, WA6ISP
10917 Bryant Street
Yucaipa, Ca. 92399
(909) 918-0058
PayPal ID "MotDog@..."
Mike@...
|
Re: Bitx TFT display code
Please have a look at my blog for TFT touch screen based vfo and bfo. The first version of code should be there soon. Blog is at
73 Vu2spf Bhatnagar
|
Re: Si5351A: facts and myths
Would be interesting to know if any birds are still around when operating the VFO at 19mhz.
This can be done with Allard's sketch by going to USB.
Jerry
toggle quoted message
Show quoted text
On Fri, Jun 30, 2017 at 05:07 pm, Michael Babineau wrote:
All that I have left are a few birdies, which I suspect can only be eliminated by better filtering on the DDS input to the main board.
|
Re: Si5351A: facts and myths
Hans,
Actually, there is a significant change when "a" increments.
Going up from 7.0 mhz, MS0_P2 transitions from 0x00000 to 0xd51f8.
If they didn't somehow buffer those register writes, I should have heard it given the 10ms delays..
And from what I see on the scope, they make a very clean transition to the new frequency
without so much as a runt cycle. ?Not bad for $1.
Jerry
toggle quoted message
Show quoted text
On Fri, Jun 30, 2017 at 08:29 am, Jerry Gaffke wrote:
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.
|
Re: Si5351A: facts and myths
Allard et al :
What I did that really got rid of noise from the Raduino was to use either multi conductor shielded cable or RG-174 for every connection?
coming out of the Raduino and making sure to ground the shield at both ends. ?Also I avoided running any wires under the Raduino or the
main board. All that I have left are a few birdies, which I suspect can only be eliminated by better filtering on the DDS input to the main board.
Reducing the Raduino output to 2mA from the default 4mA, significantly reduced birdies without a big impact to the performance of the
rig.?
Cheers
Michael VE3WMB
|
Re: Now that's a Speaker Dude!
Nice Speaker from All Electronics! $2
3D printed Mount, there are no mounting holes on this guy?
Mike, WA6ISP
|
Re: Si5351A: facts and myths
I have a SI5351 Signal Generator running an I2C 4 line LCD, I
just had to jumper a non stock address on the I2C adapter.
You can run the I2C address scanner to find out where things are?
Mike, WA6ISP
On 6/30/2017 3:43 PM, Jerry Gaffke via
Groups.Io wrote:
So it's an i2c display, using the same SDA and SCL
lines as the Si5351?
That seems ideal if there aren't any issues, as we're about out of
pins on the Nano.
That's relevant.
Displays with the little i2c adapter board added on are quite
cheap.
If not specified they are likely operating at 5v as that's what
most of the Arduino world wants.
I'd choose a 3.3v display and not 5v though. ?If it had pullups to
5v on board there would be
some current getting dumped into the Si5351 die's SDA and SCL
protection diodes.
If the Si5351 were on the main board, it would be easy to wire up
the an i2c display and tuning pot
to the processor board of our choosing. ?No need for a Raduino
board.
(I know, broken record here.)
Jerry, KE7ER
On Fri, Jun 30, 2017 at 03:08 pm, Jeff wrote:
I am not sure it is relevant but I changed to a serial
display and all the tuning clicks disappeared with the new
display. Nice discussion by the way I am getting my education!
--
Mike Hagen, WA6ISP
10917 Bryant Street
Yucaipa, Ca. 92399
(909) 918-0058
PayPal ID "MotDog@..."
Mike@...
|
Re: Si5351A: facts and myths
So it's an i2c display, using the same SDA and SCL lines as the Si5351?
That seems ideal if there aren't any issues, as we're about out of pins on the Nano.
That's relevant.
Displays with the little i2c adapter board added on are quite cheap.
If not specified they are likely operating at 5v as that's what most of the Arduino world wants.
I'd choose a 3.3v display and not 5v though. ?If it had pullups to 5v on board there would be
some current getting dumped into the Si5351 die's SDA and SCL protection diodes.
If the Si5351 were on the main board, it would be easy to wire up the an i2c display and tuning pot
to the processor board of our choosing. ?No need for a Raduino board.
(I know, broken record here.)
Jerry, KE7ER
toggle quoted message
Show quoted text
On Fri, Jun 30, 2017 at 03:08 pm, Jeff wrote:
I am not sure it is relevant but I changed to a serial display and all the tuning clicks disappeared with the new display. Nice discussion by the way I am getting my education!
|
Re: Si5351A: facts and myths
I am not sure it is relevant but I changed to a serial display and all the tuning clicks disappeared with the new display. Nice discussion by the way I am getting my education!
Jeff
N9ARZ
|
Re: Bitx TFT display code
In searching for tft displays, i noticed there were serial and parallel. The ones with connectors on the top and bottom are generally pin compatible with uno and atmega2560.? I have several of these and the 3.5" just plugged and Jacks display worked great.. These were mci friends type marked on the board. My other tft's were 2.8 inch.
One i had to change some text size for the display to look correct. The other 2.8 from elegoo was also mcufriend, but Jacks display code worked with no changes.
His code is able to identify several tft drivers and select the correct one.. Very cool.
The serial type tft usually have single set of pins - 8-10 pins. The usually say spi or serial in the description.
I see that some Japanese and Russian hams use these type.
Looking forward to Jack"s next code run...
Joe
VE1BWV
On Fri, Jun 30, 2017, 4:57 PM Jack Purdum via Groups.Io <econjack= [email protected]> wrote: My PCB uses the Mega 2560 Pro Mini because of its smaller footprint. I buy from Wideenm991 on eBay. The DDS module is a type II, as shown here:
but are getting hard to find. I can't find the guy who made an adapter board for a Type I to a Type II board (K5ESS??). He sells the adapter for about $2. My board looks like this:
You can see where the DDS and Mega boards go. The advantage of the board is that most of the I/O pins are brought out at the bottom and top of the baord for additional hacking. With the schematic I posted earlier today you should be able to "fit" things on the board.
Jack, W8TEE
Sent: Friday, June 30, 2017 3:20 PM
Subject: Re: [BITX20] Bitx TFT display code
Jack
I bought TFTs with the double connector on the
Right Hand side, to fit Mega 2560.
But some use the single pin headers across the
top and botom (Horz) of the Mega 2560?
I got confused over Mega 2560 compatibility?
Mike, WA6ISP
On 6/30/2017 11:59 AM, Jack Purdum via
Groups.Io wrote:
I've
had some setbacks at home, but am still trying to get things
going. I don't really use "buttons" on my display, as I am
not using a touch screen at this time. The mcufriend
displays should plug right into a standard Mega 2560 or my
TFT PCB. I should have the VFO working this weekend. The
schematic for my PCB is attached. You'll need the same
pinouts for my code to work with the display.
Jack,
W8TEE
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
On 6/30/2017
11:24 AM, Joe wrote:
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@...
--
Mike Hagen, WA6ISP
10917 Bryant Street
Yucaipa, Ca. 92399
(909) 918-0058
PayPal ID "MotDog@..."
Mike@...
|
Re: Si5351A: facts and myths
On Fri, June 30, 2017 22:16, Hans Summers wrote: In my opinion (reinforced by this result) the tuning "pops" which people
mention are nothing to do with the Si5351A in 99% of cases. They are the
burst of digital activity which happens when the processor talks to the
LCD, which finds its way into the sensitive RF stages either via radiation
(lack of shielding) or conduction via the power supply lines (lack of
supply line filtering). Yes you're absolutely right! There is a lot of confusion about the origin of the tuning clicks. The SI5351 library v2.02, 2.03 and 2.04 had the PLL reset issue which indeed gave clicks because the PLL was unneccessarily reset each time. Those clicks were extra strong when you tuned near to a strong signal. But that has all been fixed recently in v2.05. Any clicks that still remain are coming from the LCD display which can be fixed by better shielding, extra caps, etc. 73 Allard PE1NWL
|
Re: Si5351A: facts and myths
We had some pops in there due to extra PLL resets in the Etherkit library, but should not be an issue going forward ?Some have found that just a filter cap across the incoming 12v at the Raduino solved their tuning tick issues. ?So filter the 12v in well, and would be best to have a good 3.3v regulator for the Si5351. ?We may have RF from the i2c lines into the Si5351 also. ?If I were scratch buillding for maximum performance, I'd put the Si5351 on the main board under a 1/2" copper plumbing endcap for shieldng, and make sure those i2c lines were in coax and well filtered for RF. ?And use multiple Si5351s and multiple endcaps if needing multiple clocks.
Haven't tried it yet, but I think you could cut off a 1/4" piece of 1/2" copper pipe and solder it to the board, testpoints coming up through the board inside the pipe to center it and give something to solder to. Then the endcap would be a friction fit over the top. ?And keep some 3/4" and 1" endcaps on hand too for larger bits of circuit that need shielding. ?Signals from one endcap to the next are routed as short traces through the bottomside groundplane, perhaps covered with kapton tape and then copper tape soldered to the groundplane. ?Should take out most of them birdies.
Your older comment about floating point taking less flash than 64bit integer math was interesting. ?I'd guess that if you have a lot of computations, 64bit integer loses due to all of those 64 bit args getting bussed around, where standard floating point is just 32 bit per arg. ?For just a couple computations the integer math might win, as the floating point multiply and divide subroutines are relatively large. ??
As I said previously, those computations on a,b,c to generate the register values do muddy things up a bit. I'll someday find those frequencies at which an entire register flips from 0xFF to 0x00 and scan through that looking for ticks. ?But I doubt they are there, and if those ticks are there they are infrequently encountered.?
Jerry
?
toggle quoted message
Show quoted text
On Fri, Jun 30, 2017 at 01:16 pm, Hans Summers wrote:
In my opinion (reinforced by this result) the tuning "pops" which people mention are nothing to do with the Si5351A in 99% of cases. They are the burst of digital activity which happens when the processor talks to the LCD, which finds its way into the sensitive RF stages either via radiation (lack of shielding) or conduction via the power supply lines (lack of supply line filtering). I think if people try commenting out the Si5351A update in the code, after the first write, so that the Si5351A is not tuned at all; but leaving the display updating the frequency, you will find the "pops" still present... time to add more power line filtering etc!
?
|
Re: Do not solder ground. Instructions mess
Well, you're about to find out anyway: ?No consequences.
Check the back of your board, the SPK1 connector ties into the same big happy ground plane as TUNING1
Some of the ground symbols got labeled "GNDREF" and some did not, but that's all one big ground net.
toggle quoted message
Show quoted text
On Fri, Jun 30, 2017 at 11:29 am, Andrew Krause wrote:
If you look on the schematic, there art two grounds. The audio circuit is on GNDREF. The RF circuit is on GND.?
I don't know what the consequences would be if you mixed the two up. But I don't want to find out.?
|
Jeff
SP Bhatnagar
Allard PE1NWL