ubitx raduino issue/AKA the radio doesn't receive
My receiver hasn't worked since I got the kit.???I've put a frequency counter (Fluke 115 multimeter) on the raduino/ubitx connector, and clk0, clk1, and clk2 all have no signal. Display is lit and counts. The raduino is in the right position on the header (per mapping the ground pins on both boards), and the radio does not receive. Regulator 12VDC in, 5VDC out. Can anyone make a suggestion to get this radio up and running?? I'm pretty savvy when it comes to computers and electronics, but...? arduino is not currently in my skill set.
Thanks!
|
Thanks for responding. If I really want more power, an external amplifier would be the way to go. Since that December post, FT8 has caught my attention, and more power would be overkill.
|
When I press the Raduino reset and the controller button the display briefly shows "Raduino 2.0" before returning back to VFO A: ?7.150:000
|
Re: Should we adopt the KD8CEC firmware?
The ATMega328P processor chip on our Nano processor (which in turn is mounted on the uBitx Raduino board)
talks to the Si5351 oscillator chip via a two wire i2c bus:
? ??
? ??
Some folks here are also saving 6 Nano pins by having the processor talk to a 2x16 display?
over the same two wire i2c bus
? ??
toggle quoted message
Show quoted text
On Mon, May 14, 2018 at 04:43 pm, marjannorm wrote:
sorry but somewhere down the line I must have missed something. ?What is an i2c? ?More specifically, what is an i2c periferal?
|
Re: ND6T AGC implementation for uBIT-X
I would also like to purchase one of the AGC kits. Thank you
73, Guy N7BIR?
|
Re: CONTEST!!!! New Board Naming Contest
#ubitx
BiTeensio bit TEEN see o
Vince.
toggle quoted message
Show quoted text
On 05/12/2018 08:20 PM, Jim Sheldon wrote: W0EB/W2CTX and N5IB are announcing the upcoming release of a complete
new board for the uBITX transceiver that utilized the PJRC Teensy 3.6 as
the micro-controller rather than the Arduino NANO.
We have been selling the older Raduino replacement I2C display board
that we lightheartedly named the "RadI2Cino" pronounced "rad eee too CEE
no" as it's part Raduino, uses the I2C bus to run the display and can
replace the Raduino. It has met with a fair bit of success both NANO
based and more recently with an N5IB designed adapter board that allows
a Teensy 3.6 to plug into the RadI2Cino in place of the original NANO.
The Teensy adapter allowed for a number of extra digital and analog I/O
pins that could be used for CW Keyer, S meter, Voltage Monitor and an
almost limitless number of features not yet implemented (many not even
thought of to date).
Now, our collective group, consisting of myself (W0EB), Ron - (W2CTX)
and our board designer/layout engineer Jim - (N5IB), has come up with a
newly designed board (still in the prototype stages) that will, when the
design is finalized, be offered in bare board or kit of all parts (less
the Teensy as a 3.5 or 3.6, preferrably 3.6 can be used) for a
reasonable, postage paid, price..
*Now here's the deal - I'm announcing a naming contest for this board
since these things seem to need a catchy name to identify them such as
the original Raduino, our RadI2Cino and several that are being offered
by others that I won't name here so as not to step on any toes. All of
these boards are fine in their own rights and all have merits so no
arguments or flames please.*
*The Naming contest for our new board starts NOW and runs through 23:59
UTC May 20, 2018.*
*The PRIZE awarded to the person who we (W0EB/W2CTX and N5IB) judge to
have come up with the best name for the new board will receive, free of
charge, a complete kit of parts for the new board postage paid to the
mailing address they specify. This is open to all on the
[email protected] reflector and will also be posted to the uBITX group on
Facebook. The announcement will be posted on the w0eb.com website too.*
Entries must be by direct email to the email address *jrg.qrv (at)
gmail (dot) com * only. NO entries posted to this group or the uBITX
Facebook group will be eligible. The winner will be announced sometime
after the contest closes at 23:59 UTC on May 20, 2018 and the winner
will receive an email indicating so as well as being posted on w0eb.com,
[email protected] and the uBITX group on Facebook.
Of course, myself, W2CTX and N5IB are not in the contest and cannot be
declared the winner - LOL.
Jim Sheldon, W0EB
--
Michigan VHF Corp.
|
Re: Should we adopt the KD8CEC firmware?
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
|
Re: CONTEST!!!! New Board Naming Contest
#ubitx
|
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
|
Re: Should we adopt the KD8CEC firmware?
Dennis? W7DRW
Perhaps I can provide a little information that may get you started.?
The .hex file is generated by the compiler.? In the Arduino IDE on Linux it is stored in a
temporary directory.? Windows and OS-X may be similar.?
As Jack has said, you need to click on File>Preferences and check the box for verbose
output during compiles.
When you do a compile the location of the .hex file, and other related files, is shown near
the end of the compile output at the bottom of the IDE window.?
If using the Arduino IDE you will see something like this:
/tmp/build4580944257211744891.tmp/BlinkWithoutDelay.cpp.o /tmp/build4580944257211744891.tmp/core.a -L/tmp/build4580944257211744891.tmp -lm
/usr/share/arduino/hardware/tools/avr/bin/avr-objcopy -O ihex -j .eeprom --set-section-flags=.eeprom=alloc,load --no-change-warnings --change-section-lma .eeprom=0 /tmp/build4580944257211744891.tmp/BlinkWithoutDelay.cpp.elf /tmp/build4580944257211744891.tmp/BlinkWithoutDelay.cpp.eep
/usr/share/arduino/hardware/tools/avr/bin/avr-objcopy -O ihex -R .eeprom /tmp/build4580944257211744891.tmp/BlinkWithoutDelay.cpp.elf /tmp/build4580944257211744891.tmp/BlinkWithoutDelay.cpp.hex
Binary sketch size: 1,038 bytes (of a 30,720 byte maximum)
I have highlighted the compiler output line that shows where to look for the .hex file.
You do not need to do anything with this file if you want to use the Arduino IDE to install
your new program on the Arduino.?
Connect your Arduino to the PC via a USB cable.
Go to Tools>Board and select the type of Arduino board that you are going to program.?
Next go to Tools>Serial Port and click the check-box for your serial USB port (/dev/tty/USB0
in Linux and probably something similar in Windows).?
Now go to File>Upload and your new .hex file will automatically be selected and installed in
the attached Arduino.?
There are many other things the IDE will do, such as installing a new bootloader, but new
programmers do not need to be concerned with all that.?
Arv? K7HKL
_-_
On Mon, May 14, 2018 at 2:00 PM, Dennis <dennis@...> wrote: Hi Jack,
I'm not a programmer any more and would certainly like to learn how to "find the hex file", "generate the hex file" and "learn a little bit about programming for a Nano in the Arduino IDE".
Perhaps you can recommend or provide a limited tutorial on these points. I would personally be grateful.
73, Dennis
W7DRW
On Mon, May 14, 2018 at 10:26 am, Jack Purdum wrote:
This approach still does not get around the problems "for people who do not know what we are talking about!" To me, if you can't be bothered to learn how to download, install, and recompile a program, then you probably shouldn't be messing around with the code. While your app might do away with that element of the problem, they will still have to use a hex loaders, connect to the Nano, and run the app. My guess is, 95% of the people don't know where that hex file is located. If your app, running under the multiple platforms of Windows, Linux, and MacOS, can run the custom install menu system, fork to the compiler, make the changes and generate the hex file, and then download that hex file to the Nano, that would be a great app to have! In the absence of that, users who wish to customize the software are probably going to have to learn a little bit about programming for a Nano in the Arduino IDE.
|
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
|
adding to base load software
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
|
Re: PA breaking into oscillation? (uBitx)
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.   --
|
Re: Should we adopt the KD8CEC firmware?
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/44349What 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 ??
On Mon, May 14, 2018 at 02:41 pm, Tim Gorman wrote:
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?
|
I get 3.0 mV to the connector with good continuity to the microphone.
|
Re: Should we adopt the KD8CEC firmware?
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
|
Re: Should we adopt the KD8CEC firmware?
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
|
Re: Should we adopt the KD8CEC firmware?
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
|
Craig Wadsworth
kj6etl
