From: [email protected] [mailto:[email protected]] On Behalf Of bellrossjr@...
Sent: Thursday, June 15, 2017 5:50 PM
To: [email protected]
Subject: [BITX20] W8TEE TFT/VFO DDS adapter

?

Hi All:
I received my VFO PCb's today they look great, In the process of gathering the for the build, I found the type II dds is pricey compared to the type I dds,. I recent post from W8TEE stated that he found a source for a type II to type I adapter, but cannot find the post on where he got the adapter. IS there an INO file for the VFO could find any reference for it. Looking forward to getting the VFO up and running.
73 Ross Bell K7RSB

I'm in the process of writing one myself and don't like some of the
things I'm discovering about Jason's so I'm about to try yours. At this
point I only need 2, so 2 of 3 works for me.

Vince.


On 06/15/2017 06:15 PM, Pavel Milanes Costa wrote:

Yes, but...

I'm waiting to see how they solve the output math relation in the shared
PLL.

The etherkit Si5351arduino lib from Jason claims it can put two freqs
sharing the same PLL if below certain point, my tests show that that's
true ONLY if you don't move them...

Once you start to move one of the two in the shared PLL (VFO,
correction, sideband change) the other will start jumping... BTDT... (in
my case the jumps was from a few 100th of Hz to a few KHz)

My lib always use integer math to minimize jitter and phase noise (bad
things on RF), but that has the side effect of no PLL sharing, then the
2 of 3...

But you know, there is no silver bullet... at least for free or very
cheap... ;-)

I'm waiting to see how they solve that...

73.

El 15/06/17 a las 17:53, Vince Vielhaber escribió:

2 of 3 may be a problem for the uBitX. It uses all three clocks.

Vince.


On 06/15/2017 04:46 PM, Pavel Milanes Costa wrote:

Hi group, I'm back.

Do you rememeber the pull request to switch from the etherkit Si5351
lib
(from NT7S) to my new Si5351mcu?

After a tough revision of the code I found that the error that make the
code a no-go was related two main factors:

* I2C initialization.
* Human error.

I develop mainly on the house desktop PC but use the laptop to connect
and upload the code to the internet; this resulted in wrong
(incomplete)
code uploaded to the github repository. (shame on me.)

A bug on the correction procedure was found & fixed, the init
procedures
are now mandatory and a general update to the documentation on the code
coments and Readme.md was made.

A new version (0.3) of the Si5351mcu library for arduino and flavours
was pushed to the github repository a minute ago
() you can just click the green
download button or go to the releases tab and grab it from there.

I have the bitx40 code now working back in home with a real Raduino +
Bitx40v3 SMD, but it's working against Allards code version 1.13, I
will
update it tonight against lastest 1.14.1 and fill a push request
tomorrow.

Firmware & sram reduction waranted.

73 de Pavel CO7WT.

Yes, but...

I'm waiting to see how they solve the output math relation in the shared
PLL.

The etherkit Si5351arduino lib from Jason claims it can put two freqs
sharing the same PLL if below certain point, my tests show that that's
true ONLY if you don't move them...

Once you start to move one of the two in the shared PLL (VFO,
correction, sideband change) the other will start jumping... BTDT... (in
my case the jumps was from a few 100th of Hz to a few KHz)

My lib always use integer math to minimize jitter and phase noise (bad
things on RF), but that has the side effect of no PLL sharing, then the
2 of 3...

But you know, there is no silver bullet... at least for free or very
cheap... ;-)

I'm waiting to see how they solve that...

73.

El 15/06/17 a las 17:53, Vince Vielhaber escribió:

2 of 3 may be a problem for the uBitX. It uses all three clocks.

Vince.


On 06/15/2017 04:46 PM, Pavel Milanes Costa wrote:

Hi group, I'm back.

Do you rememeber the pull request to switch from the etherkit Si5351 lib
(from NT7S) to my new Si5351mcu?

After a tough revision of the code I found that the error that make the
code a no-go was related two main factors:

* I2C initialization.
* Human error.

I develop mainly on the house desktop PC but use the laptop to connect
and upload the code to the internet; this resulted in wrong (incomplete)
code uploaded to the github repository. (shame on me.)

A bug on the correction procedure was found & fixed, the init procedures
are now mandatory and a general update to the documentation on the code
coments and Readme.md was made.

A new version (0.3) of the Si5351mcu library for arduino and flavours
was pushed to the github repository a minute ago
() you can just click the green
download button or go to the releases tab and grab it from there.

I have the bitx40 code now working back in home with a real Raduino +
Bitx40v3 SMD, but it's working against Allards code version 1.13, I will
update it tonight against lastest 1.14.1 and fill a push request
tomorrow.

Firmware & sram reduction waranted.

73 de Pavel CO7WT.

Not wanting to re-invent the wheel ... ?has anyone come up with a template for drilling holes in an enclosure for a 2 to 3 inch speaker ?
I was hoping to find something that I could print out and tape to the outside of the enclosure to use as a guide for drilling sound
holes in a regular pattern for a 3 inch speaker.?

If not, I will see what I can come up with and I will post to the group.?

Cheers

Michael VE3WMB?

2 of 3 may be a problem for the uBitX. It uses all three clocks.

Vince.


On 06/15/2017 04:46 PM, Pavel Milanes Costa wrote:

Hi group, I'm back.

Do you rememeber the pull request to switch from the etherkit Si5351 lib
(from NT7S) to my new Si5351mcu?

After a tough revision of the code I found that the error that make the
code a no-go was related two main factors:

* I2C initialization.
* Human error.

I develop mainly on the house desktop PC but use the laptop to connect
and upload the code to the internet; this resulted in wrong (incomplete)
code uploaded to the github repository. (shame on me.)

A bug on the correction procedure was found & fixed, the init procedures
are now mandatory and a general update to the documentation on the code
coments and Readme.md was made.

A new version (0.3) of the Si5351mcu library for arduino and flavours
was pushed to the github repository a minute ago
() you can just click the green
download button or go to the releases tab and grab it from there.

I have the bitx40 code now working back in home with a real Raduino +
Bitx40v3 SMD, but it's working against Allards code version 1.13, I will
update it tonight against lastest 1.14.1 and fill a push request tomorrow.

Firmware & sram reduction waranted.

73 de Pavel CO7WT.

Hi group, I'm back.

Do you rememeber the pull request to switch from the etherkit Si5351 lib
(from NT7S) to my new Si5351mcu?

After a tough revision of the code I found that the error that make the
code a no-go was related two main factors:

* I2C initialization.
* Human error.

I develop mainly on the house desktop PC but use the laptop to connect
and upload the code to the internet; this resulted in wrong (incomplete)
code uploaded to the github repository. (shame on me.)

A bug on the correction procedure was found & fixed, the init procedures
are now mandatory and a general update to the documentation on the code
coments and Readme.md was made.

A new version (0.3) of the Si5351mcu library for arduino and flavours
was pushed to the github repository a minute ago
() you can just click the green
download button or go to the releases tab and grab it from there.

I have the bitx40 code now working back in home with a real Raduino +
Bitx40v3 SMD, but it's working against Allards code version 1.13, I will
update it tonight against lastest 1.14.1 and fill a push request tomorrow.

Firmware & sram reduction waranted.

73 de Pavel CO7WT.

To protect an input you can put a series resistor to limit current, then a diode on the input to +V and another to ground.

Allard ... this is excellent ... exactly what I was hoping for. ?Thanks for the quick response !?

My thoughts on ?ESD protection for the key line were that it would be easier to do something
like to add ?Zener diode than to have to replace the soldered-in Arduino Nano on the Raduino board?
(i.e. a situation where an ounce of prevention is worth a pound of cure).

Cheers

Michael VE3WMB?

I have this one. Enough room and the nice tilting bar feature. You will have to drill holes for the speaker. You may use different panels as the fron and rear are detachable. They are only with a sliding panel.
I suggest you shield it with this tape or something like that?

I didn't follow this:

?

? ???but then wouldn't the US would have high customs charges for stuff originating here too?