How To Upload The Ubitx Manager

Ashhar Farhan VU2ESE has indicated that there is a bug in the v6 lawmaking that prevents piece of cake band switching to the 17m (xviii MHz) band.

This is in ubitx_ui.cpp in line 746. Information technology should read "17", instead information technology reads "eighteen" in the code as shipped with the offset v6 µBITx off the line. This makes the button for 17 meters (xviii Mhz) unusable, yous have to use fast tune or straight frequency entry to get to 18 MHz.

Ashhar has patched the source code on https://github.com/afarhan/ubitxv6

He reminds those wanting to amend their code for uploading that the v6 source code compiles only when saved inside the sketches binder of the Arduino. This is an Arduino idiosyncrasy.

Reference

Just as the BITx40 goes out of production, Allard PE1NW has released a new version of his acclaimed firmware for the BITx40.

This is known every bit the Raduino v1.29 version, and can be downloaded from here: https://github.com/amunters/bitx40

New in this release:

Added Roger Beep (NASA mode "Quindar Tone" as used in Apollo missions).

Note that the PTT sense, RX/TX and CW Carrier mods must be installed for this feature to piece of work.

Press Function Button 7 times to toggle this function on/off. It's OFF by default as some find it annoying. Others find it helpful in pile-upwardly situations though.

Allard says "Utilise responsibly!"

Allison KB1GMX commented that the "Roger Beep" was not a mutual thing until the CB mess broke down in the early 80s and it was often accompanied with other electronic dissonance makers and profanity. Then that mess started moved into the lower (CW) sections of the 10M band and they got tired of freebanding.

Well-nigh of usa back when that used CB found it annoying and unneeded peculiarly for SSB. The general feeling is it was those that were disruptive or trying to experience like they were running something important doing information technology initially. It was especially noxious when it appeared in the 80s. Then it became a feature on CB radios (a signal that those that were modified for non CB allocated frequencies) and later Chinese made HTs.

For the Infinite activities (Mercury and later) it was needed as the communications were actually full duplex on the data links and you lot had to have some way of knowing when the other guy was done equally in really did release the button and it was also to confirm the push didn't stick as in heard in the astronauts headphone when he released the button (or VOX). Until CB adopted it if you heard a over beep is was probable a repeater (usually ham) or space based radio (space program).

To date I know of the use of "over beep" actualization is standard communications systems, those beingness Infinite plan, Repeaters, armed forces systems that use satellite links, and CB.

It does however correspond what one tin can do with a MPU of reasonable power and some programming skills!

Reference

Ian KD8CEC has released his latest firmware. This requires a minor configuration flag to be ready to your µBITx version (3, 4 or 5) in the sketch before compiling and uploading the code to your µBITx.

Earlier µBITx versions do not require upgrading as no new features take been added to the firmware other than compatibility with the new v5 board.

Ian KD8CEC has announced a beta version of his firmware (Version 1.12) for the uBITX V5 board. He has written an commodity well-nigh it hither.

All existing firmware functions for V3 and V4 are available on the V5 beta.

The same version of uBITX Managing director will work with the v5 Lath.

Merely the LPF control and the frequency control part are changed in the V5 code. Ian has released firmware V1.121 for V5.

Reference

Nick VK4PP notes that custom filter section in uBITx Manager software for CEC firmware allows for configuring LPF daughter boards and is very easy to setup.

Reference

Ian KD8CEC has released version 1.i of his CEC firmware. This the offset major release since Beta version 1.097. He has also released new versions of uBITx Director (for Windows) and Nextion screen firmware.

Version 1.i includes all additions or improvements from the last not-Beta release version 1.08. This includes features and issues fixes addressed in Beta versions i.09, i.093, ane.095, and 1.097. No further changes take been fabricated to the Version one.097 Beta version.

You lot do not need to upgrade if yous are using Version one.097. This is the version with only the version number changed.

Major Changes since the final official release

The firmware supports additional features for the Nextion and TJC LCDs
Read & Backup uBITX, ADC Monitoring, ATT, IF-Shift and more on Nextion LCD (TJC LCD)
Factory Reset (Both Character LCD and Nextion LCD are applicative)
Betoken Meter using ADC (A7 Port)
I2C Signal Meter
Spectrum display
Ring Scan
Memory Command on Nextion LCD (TJC LCD)
Speed Change CW-Pick on Nextion LCD
Fixed Band Change Bug (Both Character LCD and Nextion LCD are applicable)
uBITX Managing director removed the Encode and Decode buttons. The procedure has go a bit easier.
I2C Device Scan on uBITX Managing director ( Both Grapheme LCD and Nextion LCD are applicable)
Si5351 I2C Accost can exist inverse
Recovery using QR-Code Data from Server
Nextion LCD and TJC LCD can brandish Spectrum and CW Decode (using Stand alone S-Meter)
Fixes for other Minor Bugs

Please refer to the link below for details.
http://www.hamskey.com/2018/09/ubitx-firmware-cec-version-11-release.html

Please download the related files from the link below.
https://github.com/phdlee/ubitx/releases/tag/1.one

Nextion LCD or TJC LCD's GUI have not changes since the 1.097 (Beta) distribution. If you are using a different GUI that is customized by other helpful developers, you should not need to upgrade the firmware. Some screen sizes are nevertheless not supported in ver i.097 (and therefore in version one.one).

For farther details run across Ian's web log at www.hamskey.com

There are several alternative firmware versions available for use with the µBITx transceiver. So why has the KD8CEC firmware been so successful with uBITx owners?

Some key reasons put forward by uBITx.net:

KD8CEC firmware is fully compatible with the standard event kit. No hardware changes are required to brand it piece of work. This is a disquisitional point of departure with all of the other variants, and probably the most of import gene associated with the success of CEC firmware.
No custom wiring changes are required when using the firmware. This is a further significant cistron in widespread adoption.
The firmware fixes problems that come with the factory firmware – although some argue that CW modes are still non fully addressed in the CEC firmware.
Using CEC firmware means no loss of features from the default factory firmware. Other alternatives offer fewer or different features from the mill firmware.
Users are familiar with the user interface, as it reflects the default firmware's "look and feel" with the standard display supplied with the kit.
Information technology is easy to upload a hex file to the Raduino. Constructors without a working noesis of the Arduino IDE can upload files easily.
All full releases of CEC Firmware are available equally open source firmware. This follows the aforementioned structure as the original code, although most of the lawmaking has been replaced. Open source is not released for beta versions (and for adept reason).
No additional processor is required, unlike other firmware variants. A mechanism for adding boosted processors has been added in ver 1.097 (Beta). This promises a hereafter where multiple processor support will be bachelor. You won't be locked into a single processor blazon.
Addition of a Nextion display or additional processor is relatively straightforward.
The firmware on the Nextion brandish can be edited by others to provide a different "look and feel" or to add or subtract features. This is independent of the firmware for the transceiver.

Remi F1MQJ has m odified the manufacturer'due south v4.3 original firmware (published on may 23 2018) to include communication with KD8CEC memory manager.

This could be very useful for those wanting to stick with the HF Signals latest firmware, while making information technology easier to view or update initialisation settings, such as calibration of frequency or setting the BFO injection bespeak, in the original firmware.

Modifications are the same every bit those described by Ian KD8CEC here merely are adjusted to the HF Signals V4.3 original firmware.

The file removes all text after .ino in your firmware directory replacing the original ubitx_cat.ino file.

You tin can admission this file at the following URL:
https://groups.io/g/BITX20/files/ubitx_cat.ino_modified_KD8CEC_F1MQJ.txt

Ian KD8CEC has been busy once more in conjuring up new features in his CEC firmware. He is tempting united states of america with descriptions of two new features:

Nextion display update that makes it like shooting fish in a barrel to suit keying speed and to select the keyer type (Iambic A, Iambic B or Straight Central) even while in TX
Adding an additional arduino, continued to the Raduino via i2c, to provide an S-meter function.

The first feature is well explained by the photo to a higher place. The second feature is a bit more difficult to depict. Past adding a US$3 additional arduino the µBITx at present has double the number of analogue and digital ports and another 32K of program space. This could be a fun ride! The first part is a bones ane, but an important one. A much more sensitive S-meter. Only wait in that location's more, as still to be fully described. If you already have a Nextion screen, it looks similar you may be in line for a half decent signal analyser function.

Connecting up the arduino

The excursion is pretty straight forward, and involves just a couple of resistors and a capacitor, along with wiring to +5v and ground, and the two i2c lines.

W0EB and W2CTX have just completed and released a powerful new gear up of firmware for their BITeensio card.

Details about the BITeensio and links to the firmware can exist found on the website at www.w0eb.com.

Release Proclamation

"As of this morning, July 8, we take released a powerful new version of the firmware for our BITeensio card, V6.00R, that utilizes the Teensy 3.6's capability to utilize USB "Host" manner and connect a standard USB ASCII keyboard (many wireless ones work likewise). PJRC (the people that make the Teensy www.pjrc.com ) offer a standard USB cable thatcan plug into the Teensy. (You do have to add a 5 pivot header to the Teensy iii.half dozen board) on the same side, and just to the right of the USB "Micro B" connector into which you volition be able to plug the standard USB 2.0 cable. The red wire (+5V) must be plugged into the pin indicated by a white square in the outline on the Teensy iii.vi.In this version, we have implemented a comprehensive command list that allows many of the standard "menu" commands, including the operating frequency, to be entered using the keyboard.

"Also included is a brand new Keyboard CW keyer that uses most of the K1EL keyboard keyer'southward character/cardinal mapping. The V6.00R firmware is released as pre-compiled "HEX" files and placed in the appropriate directory of the "Files" link on the www.w0eb.com website. We are non denying anyone that wants information technology the source code, but you will take to enquire for it with the agreement that if yous cannot compile it or if you modify information technology, you lot are on your own every bit we simply don't take time to troubleshoot it for yous."