For the life of me I do not understand why the diode is before the fuse.

The fuse should always be first as it needs to operate for all faults even reverse polarity.

Hi,

I've managed to get the CEC uBITX Memory Manager running and the uBITX_CEC firmware uploaded to my uBITX from my Mac.

uBITX Manager:

I have Microsoft Visual Studio Community (a free version) already install on my Mac, so Mono was already installed. When I first tried to run?uBITX_Manager it crashed with the warning "The Carbon driver has not been ported to 64bits, and very few parts of Windows.Forms will work properly, or at all".

After a little Googling I found the solution was to run mono in the 32 bit mode with the following command:
mono --arch=32 uBITX_Manager.exe

The uBITX Manager UI runs painfully slow on the Mac. Scrolling is next to impossible. But, with patients it is useful. The buttons will be covered over often, but just hover the mouse over them to bring them back.

The manager crashed when connecting to the USB serial chip unless the "Linux" mode check box was checked.

Also, I already had the USB serial driver installed because I'd purchased a temperature logger from this company "Elitech" and the driver was included with their software. However, the Mac "Homebrew" installer now has an updated signed driver for the CH340 chip. I found this on Github:??

uBITX CEC Firmware Upload:

I decided the best way to upload the firmware was through the Arduino sketch IDE. I downloaded the firmware source code and compiled it. The only issue I had with comping the code was I named the base directory with the version number of the code as part of the name. The source code wants to be in a directory named ubitx_20. I installed this directory under the "~/Documents/Arduino/" directory where all my other sketches are located. I have a fair number of libraries already installed, so it is possible you may need to add a library here or there if the CEC uBITX firmware needs any other libraries.

Running the Firmware:

The firmware seems to be running just fine. I used the uBITX Manager to copy the memory values from my Radiuno and save them to a file. I'm particularly interested in using the CAT interface to control my uBITX from a Raspberry Pi.

This software and the fact that it exposes all the memory settings, may have already started to point to some of the mysteries involving my radio. I have noticed my receiver is about 100hz low on sideband signals. That is no big deal. However, it looks like my transmitter frequency is about 1khz low on CW. I can't quite wrap my head around the standard factory setup calibration method and if it could result in an unwanted difference in the transmit and receive frequency calibrations (or fix it).?

I wanted to try the IF shift to get a handle of where my radio may be operating in the 12Mhz crystal filter bandpass. Interestingly, tuning the IF shift up a kHz makes the received SSB signals much clearer. So, maybe my uBITX is out of calibration.?

There truly are a lot of numbers and such to digest in the uBITX Manager, but I'll read the posts (and the synthesizer chip's app notes) on how the calculations are done and then I'll know for sure when my radio is calibrated. At least now, rather than not quite knowing what the assumptions are in the factory calibration, I can directly experiment with the values to understand them and see what works.?

Tom, wb6b

peeps, jack, ian, allard, arv

i have created a next version of the base software after thinking hard about it. you can download it from?. I invite you all to test it. if you are not familiar with C code or Arduino programming, I suggest you wait for a few days until we get all the bugs sorted out. This is only for the Arduino regulars.

Sending bugs:

Send me the bug reports directly to my email farhanbox@.... In the subject line use the word "#ubitx40". I will try to answer all emails but I can't promise responses to all.?

Before you start reviewing the code, let me give you a heads up of what to expect. Going by the general mood, I have taken the call to substantially borrow from Ian, KD8CEC's code and back port it to the original ubitx code. I guess that the new code has about 10% more lines but it is substantially more robust and useful.? The main features that I cherry picked from Ian's code are:

1. Keyer. You have to choose which keyer to use, but the keying is much better and robust now. This code is a total copy/paste of Ian's keyer. The auto-keyer (that sends out preset phrases in cw) is left out. The Iamabic A, Iambic B and the handkey sending works very well.

2. CAT control. Given the popularity of FT8, I rewrote the cat by following Ian's code but rewrote it to follow the ubitx coding conventions. It is a miminal set.

3. Split operations: My own interest of working with satellites have prompted me to add split operation.?

4. Rationalized menus: The menu system is now more consistent.

5. Tuning mechanism. The accelerated tuning works, though it doesn't jump randomly like before nor does it work at that speed. For very long band changes, it is recommended to do that through the menu option to change the band.

Among the things left out was support for different other types of displays, wspr beacon and many other goodies. The eeprom memory map is kept consistent with the KD8CEC's plan. You can switch between both the codes easily.

I have kept usage of english words at a minimum.??

- f

Why not remote it some from the mainboard and put a box around the back of it
with the wires sneaking out of? it.? The front of the box is the front panel and the
Raduino is tinned up.? Take care with the signal leads (use SHORT twisted pairs).
Used those tricks for old style counter circuits that radiated digital noise like mad.

In my case the height of the board when mounted is a problem.? Solution is change
the board connector into a right angle and then relocate the display with wires.
That lowers the profile.? ?Both boards can easily then have a cover over them
made of soldered up PCB, hobby brass, or copper screening.? Control pins will
exit though the screen box via 1000pf feedthroughs.? I try to keep noise in
the box so to speak.

Allison

RIght now I'm using 2n2222A with acceptable results.

The KSP10 might be ok too, I like the price.? ? MPSH10s are on the way already but will not
have time to use them?till next week.

Right now rather than device suggestions I'll take all your free time.? ;)

Allison

On May 22, 2018, at 2:47 AM, Jerry Gaffke via Groups.Io <jgaffke@...> wrote:

or

Tell that to varidur.? Reverse protection diodes are cheap insurance.