Date   
Re: Different Tuning Steps #ubitx

Jack, W8TEE
 

A signed int on a Nano is a 2-byte number. Because the Most Significant Bit (MSB) is the sign bit, you only have 2^15 = 32,767 Anything after that sets the sign bit and appears as a negative number. I would guess that's what happened here, since it only happens on the largest value. Since you are working with frequencies, in Hertz, you should use the unsigned long data type. When you are assigning constant like below, it's good practice to use the data type specifier (in yellow below).

Jack, w8TEE

On Saturday, July 14, 2018, 4:48:17 PM EDT, Lee <mr.olson@...> wrote:


I want different tuning steps.   I wanted larger steps to, for example, to help moving from one WWV to another.   Below is what I changed.  When I try to set it to 100000 the display reads -31072 and when I accept it the display now shows 00000 ST  I under stand it will only display 5 digits but I could get by with just an S instead of the ST or take the M from the upper frequency display.   I am just a barely an Arduino hobbyist and I know there are some Arduino Pros here.   Does anybody have any ideas?   Thank you for the help.

  //Check Value Range and default Set for new users
  if (findedValidValueCount < 5)
  {
    //Default Setting
    arTuneStep[0] = 10UL;
    arTuneStep[1] = 100UL;
    arTuneStep[2] = 1000UL;
    arTuneStep[3] = 10000UL;
    arTuneStep[4] = 100000UL;
  }
--
Lee - N9LO  "I Void Warranties"

 

Windows Serial Port Problem

Albert Woodhull
 

A few days ago my Windows 10 installation got updated, without asking me, of course.  I stepped away from the computer for a while and when
I came back updates were being installed.

I think my USB port drivers were changed.  When I try to run the KD8CEC Memory Manager or to upload a newly compiled  ubitx_20 version
I do not see the COM4 port any more. The Windows Device Manger shows an "Unusable Parallel Port (LPT3) where I previously saw a COM4
Serial Port.

Does anyone know what happened or how to undo it?

- Al N1AW



Re: Windows Serial Port Problem

Thomas Martin <tem494@...>
 

I am not an expert but try unplugging the device then back in and also check device manager to see-if the device is active

Tom

Tom Martin


On Jul 14, 2018, at 4:09 PM, Albert Woodhull <n1aw@...> wrote:

A few days ago my Windows 10 installation got updated, without asking me, of course.  I stepped away from the computer for a while and when
I came back updates were being installed.

I think my USB port drivers were changed.  When I try to run the KD8CEC Memory Manager or to upload a newly compiled  ubitx_20 version
I do not see the COM4 port any more. The Windows Device Manger shows an "Unusable Parallel Port (LPT3) where I previously saw a COM4
Serial Port.

Does anyone know what happened or how to undo it?

- Al N1AW



Re: Nextion display cutout and mounting. #ubitx #ubitx-help

Dave Dixon
 

Hello Derek,
                     I firstly fitted the normal lcd display so the hole was cut for that the 2.4 screen just covers the hole I am mounting mine on the front panel with small standoffs.I am also running a version 3 with KD8CEC 1.07 and have today worked most of Europe on 40 mtrs with my dipole.regards dave g0ayd


On 14 July 2018 at 18:03, derek via Groups.Io <derek.g4vwi@...> wrote:
Hi Dave and others using the Nextion display.

Nice to know all is running well.

However, did you do anything about the 3mm inactive strip along the RHS or did you mount the screen with a slightly smaller cut-out to the screen size? Perhaps you have not bothered about this at all?
I take it you got everything up and running using the supplied display first. I have the 2.8 and 3.2 displays available here.
Any issues with transferring the firmware?
Any tips would be welcome.

Derek G4VWI.


Re: Windows Serial Port Problem

Ralph Mowery
 

Sometimes if you are not using a Profilic (probably spelled way wrong) original driver but a 3 rd party driver, you have to delete the driver and install the 3rd party driver.  This seems to happen to many almost  every time win 10 updates.

This may explain it.




On Sat, Jul 14, 2018 at 5:09 PM, Albert Woodhull <n1aw@...> wrote:
A few days ago my Windows 10 installation got updated, without asking me, of course.  I stepped away from the computer for a while and when
I came back updates were being installed.

I think my USB port drivers were changed.  When I try to run the KD8CEC Memory Manager or to upload a newly compiled  ubitx_20 version
I do not see the COM4 port any more. The Windows Device Manger shows an "Unusable Parallel Port (LPT3) where I previously saw a COM4
Serial Port.

Does anyone know what happened or how to undo it?

- Al N1AW




Re: Different Tuning Steps #ubitx

Lee
 

Is something missing?   
--
Lee - N9LO  "I Void Warranties"

 

Re: Different Tuning Steps #ubitx

Mike Woods
 

Lee

Are you editing KD8CEC sketch?  If so, this won't achieve what you want.  These values are only the initial values when the programme first runs.  They won't apply once values have been saved in EEPROM.

You can change the step values in UBitx Manager software in Windows (easiest method), or (I think) in the setup menu.

Mike ZL1AXG

On 15/07/18 11:29 AM, Lee wrote:
Is something missing?   
--
Lee - N9LO  "I Void Warranties"

 


--
Mike Woods
mhwoods@...

Re: Different Tuning Steps #ubitx

Lee
 

Yes, it is KC8CEC 1.08.   Changing those values does change my step size but the 100000 displays funny while setting it or using it.
--
Lee - N9LO  "I Void Warranties"

 

Re: Windows Serial Port Problem

Gordon Gibby <ggibby@...>
 

I think it’s FTDI that windows likes.




On Jul 14, 2018, at 17:57, Ralph Mowery <rmowery42@...> wrote:

Sometimes if you are not using a Profilic (probably spelled way wrong) original driver but a 3 rd party driver, you have to delete the driver and install the 3rd party driver.  This seems to happen to many almost  every time win 10 updates.

This may explain it.




On Sat, Jul 14, 2018 at 5:09 PM, Albert Woodhull <n1aw@...> wrote:
A few days ago my Windows 10 installation got updated, without asking me, of course.  I stepped away from the computer for a while and when
I came back updates were being installed.

I think my USB port drivers were changed.  When I try to run the KD8CEC Memory Manager or to upload a newly compiled  ubitx_20 version
I do not see the COM4 port any more. The Windows Device Manger shows an "Unusable Parallel Port (LPT3) where I previously saw a COM4
Serial Port.

Does anyone know what happened or how to undo it?

- Al N1AW




Re: Basic board test: 130ma @ 12.5 volts #ubitx

hirosmb <hirosmb@...>
 

Jerry,

Very much appreciated for your detailed explanations.

// hiro, JJ1FXF



2018/07/15 3:18、Jerry Gaffke via Groups.Io <jgaffke@...>のメール:

Not stupid.

It's not in the instructions.
Also, the photo clearly shows no Raduino plugged in.
    http://www.hfsignals.com/index.php/ubitx-wire-up/
Seems Farhan wrote that 7 months ago, and this has all since slipped his mind.

There's nothing that would be damaged if a uBitx main board were powered up
without a Raduino plugged in.  

Looking at the Raduino connector on the uBitx main board schematic near the bottom of this webpage:
    http://www.hfsignals.com/index.php/ubitx-circuit-description/
there are signals for  T/R, TXA,TXB,TXC, CLK0,CLK1,CLK2, CW-KEY, and CW-TONE.


The relay driver at Q15 for T/R won't have any current going into the base,
so that transistor won't be on.  The rig will not be trying to transmit.

Likewise for the LPF band-switching relays at TXA,TXB,TXC.
Though if some of them were on we don't really care.

Perfectly fine that the three clocks are dead, that won't hurt anything.

CW-KEY won't be unbalancing the first mixer because there's no current going in there.
Doesn't really matter anyways because T/R does not have us in transmit mode.

CW-TONE is fine if there's no current going in. 
And would be fine if 5v was applied there anyways.

You might think we could have damage if T/R was somehow injecting current
into Q15, which would power up the transmit amp with inappropriate LPF filters selected by the relays.
However, with all clocks dead, won't have any RF energy going out anyway.
And if there was RF, the IRF510's powered at 12v would be fine (at least for awhile) with the high SWR.

I'd recommend you follow the WireUp instructions as originally written up.
Follow the example in the photo, and do not plug in the Raduino.
I don't see anything wrong with that.
If it were a problem, then we would probably have lots of failures when
blowing new firmware with the rig powered on, no reports of such failures.

I'm much more concerned with the false sense of protection from reversed supply leads 
provided by the recommended reverse diode and no inline fuse, that's a recipe for disaster.
We have several threads on this, search for "reverse polarity" here:  https://groups.io/g/BITX20/messages

Jerry, KE7ER 



On Sat, Jul 14, 2018 at 08:51 AM, Don - KM4UDX wrote:
Hum.....the build instructions say NOTHING about plugging in the raduino BEFORE the current test.  So I didn't plug the board in -- and did the test per instruction. 

If if this is an important caution, why not just say..."plug in raduino then do test".  Why leave us to guess and be stupid? 

So so I was stupid. 

Re: Basic board test: 130ma @ 12.5 volts #ubitx

Don - KM4UDX
 

Jerry - as the original "not stupid" guy, thank you VERY much for the detailed analysis of a mainboard w/o raduino.  

This is kit has been so much fun to build. I've loved every minute of it. 

The receiver and audio are really fine. I'm using an efficient clossed-back 5" midrange, and the CEC software.  On a strong signal, the volume is "sweet" and ample. Nice to listen to.  Weak signals & inefficient speaker could easily be a problem. But not here. 

Amazingly the basic cat control (freq change) works great from WSJTX!!  I jumped out of my seat when I clicked on a freq within WSJTX and the uBitx changes to that freq.  How cool is that!!!  And for us liberal arts majors, that means we figured out how to load up the required apps, get the configurations and ports and a thousand other technical details right, and not screw it up. A slap on the back for a non-EE. Hahahah.

The transmit half is not working yet.  I built the mic in a pill bottle in honor of the Dr.  But, there is not enough audio modulation to make a signal.  So I'm using the keyer generated tone, but even that gives me next to no RF output.  So I have to keep working at that.  I'll double check my work and see if I can stumble on the problem and careen into a fix. That normally my problem solving methodology. 

More work to come, with crossed fingers.  I can't tell you all how much I want to make a contact with a transceiver I build. 

Thanks.

Re: Different Tuning Steps #ubitx

Peter Aiea
 

Or you could punt, and manually store the freqs for WWV in the memory channels available in the  KC8CEC 1.08 software ...
I did that - it's arguably easier than dial twiddling, hi. 
Sorry if this is no help - I know this doesn't address the coding issue and I haven't tried the step you're attempting.  
With arduinos though, I have had gnarly formatting issues displaying numbers on a tiny LCD display.  
You may have to mess with the LCD formatting code for the screens that are giving you display problems 
to get a readable display. assuming the long int used  for arTuneStep and associated variables remain sane. 
v/r
pete  kh6dk

On Sat, Jul 14, 2018 at 2:49 PM, Lee <mr.olson@...> wrote:
Yes, it is KC8CEC 1.08.   Changing those values does change my step size but the 100000 displays funny while setting it or using it.
--
Lee - N9LO  "I Void Warranties"

 


Re: Different Tuning Steps #ubitx

Mark M
 

I think Jack got it. The way Ian coded it you can't save that large of a value. It would probably be a good idea if there was some error checking in the uBitX Manager program where it wouldn't let you enter an invalid value. Or at least some warning about it.

Suggestion...to hop between WWV freqs, or any other freqs for that matter, put them in the channels...use the 'VFO to Channel' function in Ian's firmware. Then you can select which one you want using the 'Channel to VFO' function. I have the 5, 10, 15, & 20 MHz WWV freqs saved so I can check propagation. It's a lot faster than spinning the tuning knob.

Mark AA7TA

On 7/14/18 5:49 PM, Lee wrote:
Yes, it is KC8CEC 1.08.   Changing those values does change my step size but the 100000 displays funny while setting it or using it.
--

Re: Windows Serial Port Problem

George Baumann
 

I switched to using Parallax USB to Serial RS-232 adapters after having problems with ones from Prolific!

Started having problems with Prolific adapters when I switched to Windows 10.

Re: Different Tuning Steps #ubitx

Mike Woods
 

Try something under the maximum value 50000 should work and be almost as good as a fast way of getting around?

i presume you  know about Gen Coverage mode?  Go to band change and hold down the switch for a couple of secs.  It will then step up and down by a MHz on band change, which may also get you where you want to go?

Mike

On Sun, 15 Jul 2018 at 12:49 PM, Lee <mr.olson@...> wrote:
Yes, it is KC8CEC 1.08.   Changing those values does change my step size but the 100000 displays funny while setting it or using it.
--
Lee - N9LO  "I Void Warranties"

 

Re: Mike element

iz oos
 

I am now puzzled. Which gives more output? A mic with sensitivity - 24db or one at - 44db (as mine which still give some less output than the stock element)?


Il 13/lug/2018 23:05, "k1yw via Groups.Io" <k1yw=mail.ru@groups.io> ha scritto:
I have been playing with electret mics and using one that has has -24 dB output. This is :

https://www.mouser.com/datasheet/2/334/AOM-5024L-HD-R-1219369.pdf

Note that 0dB = 1V/Pa. If you look at some of the specs of other elements, they have typical sensitivities from ~ -40 to -30dB. There is a huge range....

https://www.mouser.com/Electromechanical/Audio-Devices/_/N-awp3d?Keyword=microphone&FS=True

Greg
K1YW

Re: Windows Serial Port Problem

Gordon Gibby <ggibby@...>
 

FTDI drivers were enforced by windows10, and had features designed to either refuse to use, or even adversely reprogram counterfeit versions of FTDI hardware..... and thus prolific stuff seems to have been ............




On Jul 15, 2018, at 03:20, George Baumann <georgehbaumann@...> wrote:

I switched to using Parallax USB to Serial RS-232 adapters after having problems with ones from Prolific!

Started having problems with Prolific adapters when I switched to Windows 10.

Re: Windows Serial Port Problem

Nigel G4ZAL
 

The uBitx uses a clone nano and the serial/USB chipset CH340.
In Windoze 10, open Device manager and right click the unusable/unwanted Parallel port LPT3 and delete it.
Download the CH340 USB serial driver and run it.
Plug in the ubitx and Windoze should install the correct driver.

If it still doesn't work, maybe try editing the Windoze registry and remove all com ports...
http://woshub.com/how-to-clean-up-and-reset-com-ports-in-windows-7/

A reboot may help (it's Windoze after all).

Nigel.

Question about Nextion display and firmware

f1apy - Jacques
 

Hello Group and developpers

 

I’m sorry for my bad English, but I have one question about firmware of raduino to use with a nextion display,

on site I have access to Hex file, it’s right, but I plan to use a megamini-pro,

where I can obtain sources files to compil on the good processor ? or the team of dev can compile an hex file with this proc please ?

many thanks to support me

73’s de Jacques – F1APY

Re: Question about Nextion display and firmware

Bo Barry <wn4ghv@...>
 

I don't think the source files for the latest CEC firmware have been released yet. I may still have an earlier version.
I think the chip you mentioned is a mega2560. If so I could send a hex file of the previous version compiled for the 2560.
If your English is bad, you should see my French . 😂 Buenos Dias. Bo W4GHV since '54