Hi,
sorry but somewhere down the line I must have missed something. ?What is an i2c? ?More specifically, what is an i2c periferal?
regards
Norm vk5gi
McLaren Vale
South Australia

I desoldered all wires from the encoder.
The push putton funktions works from open circuit to 0 ohm when I push it.
Connecting the yellow and red wire doesn't change a thing on the display.

I disconnected all wires from the encoder and measured the following:

?

The following measures to common ground on chassis:

Yellow -0.03v

Brown + 4.73v

Red + 0.01v

Black + 4.73v

?

?

Measurements between controller wires:

Yellow > Red + 0.04v

Yellow > Brown + 4.73v

Yellow > Black +4.73v

?

Brown > Red 0.00V

Brown > Black 0.00v

Attached is a schematic of the variable IF circuit. ?The RX and TX voltages are about 12V, so I used a resistor network to keep the applied voltage to about 1 to 9V because that is the usable range for these diodes.

The 4.7K resistors that feed the voltage to the VVC diodes could be 10 or 20 K, or what have you, as there is very little current needed.

Tom W1EAT

Allard,

I? checked the purple wire is indeed on the center wiper and I do have 0 to 5.0 volts as I move the shaft.?



Tom WD9GON

开云体育

Tim,

I am a little confused by your post titled Re: [BITX20] Should we adopt the KD8CEC firmware?
You mention a feature you may want to implement.

To me, whether the 'base load' is hfsignals firmware, or KD8CEC firmware, the problem
seems to be the same. You can add or delete features to/from either firmware.

I quote your email:

It's my opinion that we *need* a base load with a set of common
functionality that experimenters can build on. The current software
that Ashar provides seems to fit that bill.

If someone wants to load other software then it is up to them to
manage all the complexity. 

--end quote--


In your example, especially the second paragraph quoted above, it seems
to me that either 'base load' would suffice. Am I missing something?

Rod KM6SN

OK. Figured it out.?

Relays are fine.

The culprit: I have?a PCB trace,?with the node/net L1, C200, C80 running parallel to my RF output trace (from relay KT1, pin 5) causing feedback.

Doh. I should have realized this much sooner. Chased the rabbit down the hole, but I caught him!

-Mike

I finally got around to designing and printing ?BITX panels for the EF01 enclosure.? I switched out the LCD for a white on black one.? I ended up recessing it in the panel to avoid the need for a bezel.? It looks much better without the flash washing it out.? I also used a different volume pot so I had more knob options.? I had to angle the shot of the back to deal with the glare so you'll have to believe me the heat sinks line up with the openings.? The fins are just proud of the back with room around them for air flow.? The top 3.5mm jack is TRRS for mic and ptt.? I do not have a keyer jack.? Over the antenna connector is a mini USB connector.? On the back of the panels are recesses for the connectors that were too short to make it through otherwise.? The front and back are both glossy enough to show fingerprints.


--

Basic CW capability using the PTT switch on the mike is very lightweight
and?I'd tend to include it on any uBitx build.
? ??/g/BITX20/message/44349

What firmware gets shipped by hfsignals is up to Farhan,?
primary concern is that it be easy for new users to do basic stuff.

Those of us that want to hack can probably figure out a way to ifdef
a common codebase that suits most of us well enough.
We'll see, if I already knew exactly how this was going to turn out
it wouldn't be any fun.

Jerry, KE7ER
??

I get 3.0 mV to the connector with good continuity to the microphone.

if it was carefully and intentionally engineered with design documentation that will open the door for experimentation then I am all for it..if it was hacked on the fly with no or poor documentation then I would prefer to write my own like the project was intended..I sense too many folks bought this as an appliance to be a cheap rig, not the experimental development platform it was intended to be. Dont adopt anything, develop your own solution.
Brian K9wis
---- Konstantinos Konstas <constantine170@...> wrote:

=============
Ashhar,

I am fully in favor of Dr. Lee's software and developments.
When I first got uBitx and fired it up, I was fully disappointed with the poorness of its firmware.
Just to mention the stock Split operation. I am sure more fellow users will agree with me.
Frankly speaking, it is thanks to CEC software that I decided to keep uBITx and play with it.
Memory Manager is a very useful tool, especially if you come to things like the S-meter calibration or the recovery of factory calibration that has been added in version 1.075
I do share some of the concerns of the published responses about the size and perhaps the too many features, but I am convinced about Dr. Lee's ingenuity and I am sure he can come up with a good start up version that can be helpful to beginners and? feature upgradeable.
Also if I may suggest, please consider using an I2C LCD that leaves a certain number of ports free for further experimentation and use. The cost of a I2C adapter for the LCD is minimal and I am sure you can purchase the I2C ready LCD cheaper.? A 20 by 4? LCD would make uBITx more attractive marketing-wise.

Konstantinos, SV1ONW

Well, Ash.

It seems to me that there are too many opinions
to change things very much. It is probably best to leave things
pretty much as is, and let each user determine what's the next best
thing to do...

john
AD5YE

Think of it this way.

I want to add a Tune item to the menu. The item will send a CW signal
and monitor an i2c peripheral for reverse power indication while the CW
key is held down.

Do I duplicate the CW transmit functionality in my code in case someone
wants to use my code to add the Tune functionality to their program? If
I don't do that then it won't work for someone who doesn't operate CW
and has deleted the CW function from the software. And the code gets
bloated from two different menu items duplicating the same
functionality for those that do operate CW.

Or do I wind up having to maintain two versions, one for software that
has CW functionality and one for software that doesn't?

It's my opinion that we *need* a base load with a set of common
functionality that experimenters can build on. The current software
that Ashar provides seems to fit that bill.

If someone wants to load other software then it is up to them to
manage all the complexity.

tim ab0wr



On Mon, 14 May 2018 16:38:39 +0000 (UTC)
"Jack Purdum via Groups.Io" <jjpurdum@...> wrote:

I think it could be done without too much confusion by using
preprocessor directives. That way, you don't actually mess with the
code; you only change the symbolic constants you wish to affect. For
example, if you don't use CW or CAT, then

#define CWINTERFACE ? ??????? false??????? // Set this to true if you
want to use CW #define CATINTERFACE????????? false??????? // Set this
to true if you wish to use a CAT interface

and so on. The burden of getting everything right then falls on the
programmer, not the user. The user would, however, be responsible for
their own code additions/deletions.

As to how much space this saves will depend upon the programs
kept/deleted and what you mean by "very much program space". For some
users, 50 bytes might be enough to add something they want at the
cost of deleting some existing feature. The answer to that's really a
try-it-and-see answer.

Jack, W8TEE

Have you measured the voltage at the electret element itself?

tim ab0wr

On Mon, 14 May 2018 13:06:46 -0700
t.h.mills@... wrote:

So, I just got my uBitx and have it all wired up.? It receives fine.
But, there is no transmit audio.? Here's some interesting
information.? I live about 1 Km from an AM radio station putting out
25KW.? During receive, the ubitx was experiencing some intermod and I
could clearly hear the local AM radio station.? When I keyed up and
attempted to transmit, I could hear the ubitx key up on my TS-2000.
There was no mic audio at all.? I could see about 2 S-meter increase
in noise on my TS-2000.? But, no mic audio from the ubitx.
Interestingly, the speaker audio from the local AM radio station was
being transmitted by the ubitx!? It was perfectly received audio by
my TS-2000.

So, I double checked all my wiring and everything on the ubitx is
correct.? Orange wire from digital connector to center / ring on mic
jack.? Blue from audio connector to ground.? And the purple wire from
audio connector was to the tip of the mic jack.? I tried the home
brew electret mic that came with the kit and also a Comet electret
mic.? Still no mic audio output during transmit.

I checked everywhere I could think to check to ensure continuity.
Both the digital connector and the audio connector are wire
properly.? There is a purple wire on the digital connector not used.
And, there is a red wire from the audio connector not used.

Any thoughts?

Tom - NU9R

I disagree that the original software is a good starting point for building on as its tuning and keying section need work.

I think the uBitx should be shipped with a software that best promotes it's capabilities. That way the user can enjoy it fully without having to go through an upgrade process that he may not be willing to go through.

Making room for later software changes is easy if, as said above, the software is segmented and shows the "memory cost" of each option.

As an example below is the start of the my ubitx_20.ino file, based on Ian's 1.061 version.

It is easy to make room by commenting out options to insert one's own code if desired, or simply enable "extra features".
etc......

73, John (VK2ETA)

Tom,
measure the voltage on the slider of the tuning pot with a DVM.
It should range from zero to +5V depending on the pot position.

Also make sure that the tuning pot is wired correctly. The purple wire
should be connected to the slider.

73 Allard PE1NWL

开云体育

Lead length at this frequency is mostly irrelevant. ?Stray Capacitance could be an issue in side circuit coupling or if the circuit is oddly designed at an extremely low capacitance level. ?Stray RF and coupling is the worst problem in this radio and that can easily be minimized through careful shielding. ?