Date   
Re: Compiler warnings

Jack, W8TEE
 

Writing that in plain ansi C is just more error prone work than it needs to be.

What is your suggestion to fix that?

There are elements of C++ that I don't like and tend to be misused (e.g., multiple inheritance). However, one can practice the OOP concept of encapsulation even within the confines of ANSI C, and that's a very good thing. Perhaps the two biggest mistakes I see made by beginning programmers are 1) the reliance on globally-scoped variables and 2) trying to write functions that do too much (i.e., they are not "cohesive"). A globally defined variable means that every single statement in the program has the ability to change that variable. It's like placing a hooker at the top of the program and giving every statement in the program a $50 bill and, after something goes wrong, trying to find out who the father of the error is. Encapsulation at least lessens the scope of the error search.

If you can't tell someone what a function does in two sentences or less, it is not cohesive. Another tip off is a function that has a bunch of variables passed to it, especially variables that are little more than flag variables. Writing Swiss Army knife functions may seem like a good idea, but they are almost always too complex for the task at hand and, because they try to do too much, they are rarely reusable.

Just paying attention to those two things as you write code will make the code less error-prone. Personally, I've used a lot of different languages over the years and I still think C is the best. There must be some agreement, otherwise it wouldn't be the first language most companies resurrect on a new processor and it wouldn't have lasted over 40 years.

Jack, W8TEE

On Monday, July 2, 2018, 12:08:58 PM EDT, ajparent1/KB1GMX <kb1gmx@...> wrote:


As someone that cut their teeth is the '70s with K&R C the biggest thing I see is poor programming
not poor programming languages.  I also grew up in systems where resources are scarce and 
adding them was expensive.  So pardon me if I think 32K of code space, 1k of eeprom and 2K
of ram is a lot of space.  Sure beats 8749 with 2K of program Eprom, 128byts of ram and a timer.

OOP is not a bad word but it may be very stupid in a machine with maybe 2K of ram, code
accordingly.  The problem is coders (not programmers) that figure if it doesn't fit use a bigger
chip.  Then again if the objects are small it can be useful.  For example a Arduino Mega2650
running a two axis (elevation and azimuth) antenna control that serves out position and
tracking as a web page.  No it isn't full and it even gets the TLEs for the Sat to track via
the web page.  One of these days I need GPS and a electronic compass so it knows
where it is and what way is north so I can move it with out calibrating it afterwards.
Writing that in plain ansi C is just more error prone work than it needs to be.


Allison

Elmer in Atlanta GA with working BITx40 RFSignals Kit working

Hugo Boots
 

Howdy,

I am seeking someone close to Atlanta, GA that has a working Bitx-40
"Kit" the one that you just do the final wiring and put the "kit" in a enclosure.

My "kit" receives great but does not transmit.

Thanks in advance.

Hugo

Re: RFI from uBitx TX after AGC and other mods installed

Kees T
 

Forgot to ask. Did you connect the capacitor across the connector end to ground of C1 or the 2N3904 Base end of C1 to ground ?

73 Kees K5BCQ

Re: Easy, Inexpensive Cooling Fan, Excelway Case

Richard Sepin
 


Arvo KD9HLC via Groups.Io <arvopl=yahoo.com@groups.io> schrieb am Mo., 2. Juli 2018, 15:48:

On Sat, Jun 30, 2018 at 04:32 pm, n4eev wrote:
Arv, you are one smart dude! I love your idea.
Haha, well, there are always unforeseen complications.

On mine, when I open PTT the fan coasts down and I'm guessing acts like a little magnetic generator and puts quite the whir into the AF signal for a second or two.  I'm thinking the DC pulses produced by the freewheeling fan are of opposite polarity from the PS, so I could snub them with a diode, right?

Does sound kinda cool, though.  Maybe not as cool as a "Roger beep" and nobody else (I hope) can hear it.

That's what I get for testing the idea on WSPR with the volume all the way down.

Re: RFI from uBitx TX after AGC and other mods installed

Mark M
 

FWIW, I soldered the cap across the audio input pins on the underside of the board. I didn't have an SMD so it's just a plain old leaded part...I'm not even sure what technology it is (it's blue), it's what I had in my junque boxe. I listened around last night on 40M and it sounds OK, there's plenty of audio. Nothing weird on xmit, either, that I could hear.

As always, YMMV. :)

I have some 43 mix beads laying around so if have a chance I'll remove the cap and try them and see what happens.

Now I'm looking into the S meter connection but that's for another thread.

Mark AA7TA

On 7/2/18 11:59 AM, Kees T wrote:
Forgot to ask. Did you connect the capacitor across the connector end to ground of C1 or the 2N3904 Base end of C1 to ground ?
73 Kees K5BCQ

Re: TX frequency? of uBitx at CWL and CWU mode #ubitxcw

 

Ian : 

I did as you suggested within the uBITX Manager : 

 - Enabled Adjust CW Frequency
 - Shift Display Frequency on CWL, CWU Mode

I encoded and wrote to the uBITX and then reset and I see no difference in operation.

Note that I am using your v1.094 beta with the Nextion Display.

With my main radio set to 7.050 Mhz (CWU) the uBITX must still be tuned to 7.049.300 Mhz (700 Hz Sidetone/Offset selected) CWU
in order for each Radio to hear the other, so the Display Frequency on the uBITX is still the RX frequency, not the TX Frequency.

Both radios should display 7.050 Mhz or very close to it.

Cheers

Michael VE3WMB 

Re: RFI from uBitx TX after AGC and other mods installed

John KC9OJV
 

I did it exactly as Mark did and I'm using Kees' PCB.

John
KC9OJV

New file uploaded to BITX20@groups.io

BITX20@groups.io Notification <BITX20+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the BITX20@groups.io group.

File: ubitx_32B_F_0_2e.HMI

Uploaded By: Allen Merrell

Description:
32B is for basic and 32E is for enhanced

You can access this file at the URL:
https://groups.io/g/BITX20/files/3.2%20Nextion/ubitx_32B_F_0_2e.HMI

Cheers,
The Groups.io Team

New file uploaded to BITX20@groups.io

BITX20@groups.io Notification <BITX20+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the BITX20@groups.io group.

File: ubitx_32B_F_0_2e.tft

Uploaded By: Allen Merrell

Description:
32B is for basic and 32E is for enhanced

You can access this file at the URL:
https://groups.io/g/BITX20/files/3.2%20Nextion/ubitx_32B_F_0_2e.tft

Cheers,
The Groups.io Team

New file uploaded to BITX20@groups.io

BITX20@groups.io Notification <BITX20+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the BITX20@groups.io group.

File: ubitx_32E_F_0_2e.HMI

Uploaded By: Allen Merrell

Description:
32B is for basic and 32E is for enhanced

You can access this file at the URL:
https://groups.io/g/BITX20/files/3.2%20Nextion/ubitx_32E_F_0_2e.HMI

Cheers,
The Groups.io Team

New file uploaded to BITX20@groups.io

BITX20@groups.io Notification <BITX20+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the BITX20@groups.io group.

File: ubitx_32E_F_0_2e.tft

Uploaded By: Allen Merrell

Description:
32B is for basic and 32E is for enhanced

You can access this file at the URL:
https://groups.io/g/BITX20/files/3.2%20Nextion/ubitx_32E_F_0_2e.tft

Cheers,
The Groups.io Team

Nextion 3.2 Display

Allen Merrell
 

I just uploaded 4 files for the Nextion 3.2 display. They are for the basic and enhanced to work with Dr Ian Lee's CEC 1.094 firmware. I am starting to work on the 3.5 display next.
I would appreciate input on these files if you choose to use them. They are not an enlarged version of the 2.4 they are done on an actual 3.2 size scale.

kn4ud
--
Allen  Merrell

Re: experience with Sunil VU3SUA's enclosures #ubitx

Andy Wragg
 

I ordered mine towards the end of April, there was stock showing at the time of order but this soon changed. I had several email exchanges with Sunil, over the course of my wait, with a final notification of shipping about 3 weeks ago. I chose to use IndiaPost as DHL charge extra on delivery to the UK. Shipping took 10 days. I have found the case and supplied components to be great considering what you are getting for the money. No it's not a Yaesu or Icom but if that's what you want go and spend half a grand or more. This thing is $60 delivered anywhere in the world. The power switch is a little intermittent but I can live with that until it fails and needs replacing.
Considering the popularity of these cases (overwhelming Sunil I'm sure) I'm surprised I wasn't waiting longer, remember this is cottage industry in the North of India.    

Re: RFI problem at the encoder switch #ubitx-help

Leonard Steel
 

Len Steel,
Is your enclosure metal or plastic?
Just one more possible cause.

Re: RFI from uBitx TX after AGC and other mods installed

Sascha Bohnet | DL5SMB
 

I had the same problem  (kit board) - and the cap across the audio input (bevore C1) was the solution for me too.

Just to give some feedback and thank everybody for the investigation of this problem. I used a 10nF film capacitator .
AGC also seems to be working...

Sascha, DL5SMB

Re: Compiler warnings

Steven Read
 

Nice explanation Jack! People who write standards need to realize there are are many programs they break with changes like this. Myself, I go "tweak" the source when I get something like this but I am a bit obsessive about getting a clean compile. Inflicting things like this on the average Joe is a lousy way to run a railroad!

On Thu, Jun 28, 2018 at 10:53 PM, Jack Purdum via Groups.Io <jjpurdum@...> wrote:
All:

Several people have asked about compiler warnings they are getting, like:

        warning: ISO C++ forbids converting a string constant to 'char*'

A variation on this are the "deprecated" warnings issued by the compiler. Even more confusing is the fact that the warnings they now see were not there before. Usually, this is because of a compiler update. As a general rule, compiler warnings do not prevent the compile from finishing or performing an upload. However, warnings mean something is bending the rules. For anyone who might be interested, this was my answer to one of those people.
 
--
Steven Read - ab9ol - Dublin, Indiana (em79jt)

Re: Nextion 3.2 Display

Jeff Kendrick
 

Allen,

Nice work, looks great. I'll continue to experiment and let you know if I find anything out of the ordinary.

Jeff KC5UFS

Re: RFI from uBitx TX after AGC and other mods installed

Don, ND6T
 

I spent most of the last two days experimenting. My oscillation when using that bypass capacitor was due to attaching the ground return from the pot to the audio input of the AGC board. With the bypass capacitor in place (10 nF on my test, 470 pF on Kees' board) the resistance of that return wire afforded enough of a voltage drop to create a feedback path.
If I were to encounter RFI or audio feedback I would heartily recommend a 10 nF capacitor across the audio input of the AGC. If you encounter a squeal, then open the ground return from the volume control pot right near the board and do all that is possible to make a low resistance ground for the 5 volt power return (as well as the RF).
My sincere thanks for all of the work that you folks invested and please accept my apologies for failing to anticipate the problem. 73, Don

Re: Nextion 3.2 Display

Allen Merrell
 

thanks Jeff, appreciate  it.
Kn4ud  
--
Allen  Merrell

Re: Microscope - - new thread

 

Terry, i will try to boot up to Mint and try it, I'll  let you know.

Joel
N6ALT