|
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
The explanation is absolutely correct. ?
To all programmers of CW for the uBITX. ?You do NOT offset the transmitter by the sidetone frequency! ?When you press the key, the uBITX must transmit exactly on the display frequency and the RECEIVER must be offset from that frequency by the value of the sidetone. ?Watch the video that W2CTX posted the link to and it explains how it should work.
Jim Sheldon, W0EB CW operator for over 50 years.
toggle quoted message
Show quoted text
On Sep 2, 2018, at 9:01 PM, W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
Yeah but the point is it’s the receiver that should offset. Not the transmitter
On Sep 2, 2018, at 22:31, Jim Tibbits < ab7vf1@...> wrote:
toggle quoted message
Show quoted text
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
You can do it the other way around, with the transmitter upset, but then you have to be absolutely certain that the user knows that their transmissions are offset from the dial number.
That’s not terrible, that’s exactly what happens when you’re doing upper or lower sideband, and certainly when you’re doing pseudo CW by injecting an pure audio sinewave signal into a single side band system. ?FLDIGI will do that, and you can even rig
it so your computer shows your correct transmitting frequency
On Sep 2, 2018, at 22:31, Jim Tibbits < ab7vf1@...> wrote:
toggle quoted message
Show quoted text
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
toggle quoted message
Show quoted text
On Sun, Sep 2, 2018 at 7:33 PM Gordon Gibby < ggibby@...> wrote:
Yeah but the point is it’s the receiver that should offset. Not the transmitter
On Sep 2, 2018, at 22:31, Jim Tibbits < ab7vf1@...> wrote:
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
Did you watch the video?
rOn
On September 3, 2018 at 6:36 AM Jim Tibbits <ab7vf1@...> wrote:
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote: Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
?
?
|
Yes and it was reasonably well done but oversimplified a bit.
toggle quoted message
Show quoted text
On Sep 2, 2018, at 9:36 PM, W2CTX < w2ctx@...> wrote:
Did you watch the video?
rOn
On September 3, 2018 at 6:36 AM Jim Tibbits <ab7vf1@...> wrote:
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote: Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
?
?
|
I don't like to be overly critical, but I've been hinting for months now. ?I am now openly stating that KD8CEC's software has it wrong and it's been wrong from the beginning. ?I call on Ian Lee to clean up his code and get it right before he adds any more junk to his programs.
Jim, W0EB
toggle quoted message
Show quoted text
On Sep 2, 2018, at 9:33 PM, Gordon Gibby < ggibby@...> wrote:
Yeah but the point is it’s the receiver that should offset. Not the transmitter
On Sep 2, 2018, at 22:31, Jim Tibbits < ab7vf1@...> wrote:
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
Ian's software is the most popular update available for the uBitx.
He has added a lot of functionality to the rig and that is to be applauded.
It's taken months of free time for him to bring it to this level.
Could well be that Ian doesn't use CW much, and CW is not a priority for him.
Getting an iambic keyer to feel right is best done by a serious CW operator.
I'd think Jim Sheldon would be an excellent candidate.
Jerry, KE7ER
toggle quoted message
Show quoted text
On Sun, Sep 2, 2018 at 08:00 PM, Jim Sheldon wrote:
I don't like to be overly critical, but I've been hinting for months now. ?I am now openly stating that KD8CEC's software has it wrong and it's been wrong from the beginning. ?I call on Ian Lee to clean up his code and get it right before he adds any more junk to his programs.
?
Jim, W0EB
|
This issue come up over and over. The factory software has (or at least originally had) the same issue. A comprise would be for the display to switch to the TX frequency when you key the transmitter with the CW key. At least people would get some feedback to know that is happening. I think Ian responded in a previous thread on this issue with a setting in his uBITX memory manager that would at least do the display the frequency on transmit. It may be in the CEC documentation, but I don't remember what it was.
If you try to set your receive CW tone to the same as the sidetone when you send CW, that will get you close. Better would be for the functionality to be included for everything to work how the video explains it. Adding a true zero beat function might involve a hardware change, or injecting the sidetone audio at a lower volume, during receive, with an added ?button.
Tom, wb6b
|
Thank Jerry, but in all of the software put out by the Triumviratw Skonk Works from our first public release for the original NANO and ever since, CW has not only worked properly but the Keyer has too. ?We figured out early on that using the voltage divider was NOT and still is NOT the way to go. ?Using 2 inputs and learning how to use the available (timer not pin) interrupts properly works just fine. ?Our software (written mostly by Ron, W2CTX) addressed the CW problem early on.
There is no need for me to use Ian's sodftware as it is so full of work-arounds, not fixes to all the problems that have cropped up that I refuse to use it. ?His source code is so convoluted that even the most experienced programmers on this group have given up trying to fix it for him.
The Nextion display is getting so cluttered up with extra buttons & menus that you almost can't read the frequency on it any more. ?It started out being a pretty nice addition and now is so cluttered as to be almost unusable. ?It's also a "Single Source" display with a GUI editor that most people can't even figure out how to use. ?Where's the utility in that?
What are all of those who spent and are spending LOTS of money just for the Nextion display alone, trying to make their uBITX $119 or $129 kit radio look like a $2000 or higher big name radio going to do when that Chinese company decides to charge hundreds of dollars for the use of their editor (since it seems to have gotten popular) and raises their prices astronomically for the Nextion because they are selling to the hams at such a rate or quits production because the market dries up?
Frankly, the original LCD was quite adequate for a rig of this caliber and all of the problems involved in using it should have been addressed before even thinking of trying something else.?
By the Way, the TSW DID that. ?We went to using the (easily accessible on the original Raduino) I2C bus to drive the display (added minimal extra cost and freed up a bunch of digital lines to use for the CW Keyer and other controls.
Also, now that Ian HAS implemented the 4 wire (power ground, TX & RX) Nextion interface that leaves 8 digital I/O pins freee on the old display connector. ?Why has he not solved the major CW problem by dropping the voltage divider altogether and using digital inputs for the paddles dot and dash inputs? ?Switch the hand key portion of the keyer over to use the Push To Talk (PTT) line, wire the hand key to use the mike jack if you don't want to add another dedicated jack. ?This allows auto select of hand key or paddles just by hitting the hand key or pressing the paddles. ?Ask Ron, it took minimal code to do this. ?You don't need PTT in CW operation and you don't normally need the hand key in SSB operation so the PTT wire is easily co-opted for this. ?
By the way, this is not meant to be a rant though it may be turning into one. ?I've seen many people complaining lately that the keyer doesn't work properly but nobody has proposed or made a proper fix to the CEC software. ?TSW has had the solution almost from the beginning but everyone has drunk the "Nextion" kool-aid and the programmer for that has chosen NOT to fix the CW issue. ?TSW has also tried to provide readable and understandable PDF files explaining how our programs work and any (usually minor) hardware changes necessary to make it work. ?
Jim Sheldon, W0EB for TSW (Triumvirate Skonk Works) website: www.w0eb.com
------ Original Message ------
Sent: 9/2/2018 11:19:23 PM
Subject: Re: [BITX20] CW OPERATION
Ian's software is the most popular update available for the uBitx.
He has added a lot of functionality to the rig and that is to be applauded.
It's taken months of free time for him to bring it to this level.
Could well be that Ian doesn't use CW much, and CW is not a priority for him.
Getting an iambic keyer to feel right is best done by a serious CW operator.
I'd think Jim Sheldon would be an excellent candidate.
Jerry, KE7ER
On Sun, Sep 2, 2018 at 08:00 PM, Jim Sheldon wrote:
I don't like to be overly critical, but I've been hinting for months now. ?I am now openly stating that KD8CEC's software has it wrong and it's been wrong from the beginning. ?I call on Ian Lee to clean up his code and get it right before he adds any more junk to his programs.
?
Jim, W0EB
|
Perfectly correct. On receive it is the BFO which must be offset and NOT the transmit frequency. When we had separate Tx and RX and the RX had a variable BFO (CR100/B28, CR300, Atalanta and their siblings, AR88 etc and all the old? ex-service Boat Anchors). the BFO was set at the centre of the IF, zero beat the incoming signal and then shift the BFO up or down the IF passband for your favourite (or xtal filter) tone. You could also peak the signal if you had an S meter and shift the BFO accordingly.
Same used to be done when listening to SSB where you had to choose the correct injection frequency for USB or LSB.
Some of the old boat anchors had the local oscillator on the high side of the received signal on lower frequencies and on the lower side on higher frequencies than the signal so that when you adjusted the BFO to receive LSB on lower frequencies you would receive the USB on higher frequencies and vice versa as this caused sideband inversion.
This was done for better tracking on lower frequencies and better (how much) stability on the higher frequencies as the local oscillator was lower in frequency than if it was on the high side of the received signal.?
On the TX side, usually the TX was switched on "net" which powered the VFO buffers etc but not the pa so that you will hear the TX signal in your receiver, zero beat with the incoming signal you wanted to answer and you will be tuned to his / her frequency.
Memories and regards from an old timer
On Mon, Sep 3, 2018 at 4:28 AM Jim Sheldon < w0eb@...> wrote: The explanation is absolutely correct. ?
To all programmers of CW for the uBITX.? You do NOT offset the transmitter by the sidetone frequency!? When you press the key, the uBITX must transmit exactly on the display frequency and the RECEIVER must be offset from that frequency by the value of the sidetone.? Watch the video that W2CTX posted the link to and it explains how it should work.
Jim Sheldon, W0EB CW operator for over 50 years. On Sep 2, 2018, at 9:01 PM, W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
If you are near the band edge you risk out of band transmissions
On Mon, Sep 3, 2018 at 4:35 AM Gordon Gibby < ggibby@...> wrote:
You can do it the other way around, with the transmitter upset, but then you have to be absolutely certain that the user knows that their transmissions are offset from the dial number.
That’s not terrible, that’s exactly what happens when you’re doing upper or lower sideband, and certainly when you’re doing pseudo CW by injecting an pure audio sinewave signal into a single side band system.? FLDIGI will do that, and you can even rig
it so your computer shows your correct transmitting frequency
On Sep 2, 2018, at 22:31, Jim Tibbits < ab7vf1@...> wrote:
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
Jim… I think you may have missed many of the positive features of the Nextion display… and in particular BECAUSE of that editor, anyone can move those, how did you call it… clutter?, things around… add and subtract easily to fit their needs without understanding and writing hundreds of lines of code like others implementations?.? That is a real BIG plus.? And… if the popularity of the Nextion keeps up, it will be no time before, feeling left out of the game, the “competition” follows suit with their own clone-ish display.? Now Ian’s code isn’t perfect, but it has brought us a lot of positive things… decent CAT control, usable “S” meter circuitry, IF shift for attenuation… etc.? And the memory manager.? Yeah at some point it makes sense for some real programmers to do a rewrite… ? Dumping on Ian isn’t a good sales tactic given his base… -- …_. _._
|
On Mon, 03 Sep 2018 12:23:57 +0000 "Jim Sheldon" <w0eb@...> wrote: Hi, I just want to be sure I understand. The PTT line can be used for straight CW keying? It seems reasonable, but I have to ask. Would this be true for any of the sketches? Thanks, Joe KN4OND Thank Jerry, but in all of the software put out by the Triumviratw Skonk
Works from our first public release for the original NANO and ever
since, CW has not only worked properly but the Keyer has too. We
figured out early on that using the voltage divider was NOT and still is
NOT the way to go. Using 2 inputs and learning how to use the available
(timer not pin) interrupts properly works just fine. Our software
(written mostly by Ron, W2CTX) addressed the CW problem early on.
There is no need for me to use Ian's sodftware as it is so full of
work-arounds, not fixes to all the problems that have cropped up that I
refuse to use it. His source code is so convoluted that even the most
experienced programmers on this group have given up trying to fix it for
him.
The Nextion display is getting so cluttered up with extra buttons &
menus that you almost can't read the frequency on it any more. It
started out being a pretty nice addition and now is so cluttered as to
be almost unusable. It's also a "Single Source" display with a GUI
editor that most people can't even figure out how to use. Where's the
utility in that?
What are all of those who spent and are spending LOTS of money just for
the Nextion display alone, trying to make their uBITX $119 or $129 kit
radio look like a $2000 or higher big name radio going to do when that
Chinese company decides to charge hundreds of dollars for the use of
their editor (since it seems to have gotten popular) and raises their
prices astronomically for the Nextion because they are selling to the
hams at such a rate or quits production because the market dries up?
Frankly, the original LCD was quite adequate for a rig of this caliber
and all of the problems involved in using it should have been addressed
before even thinking of trying something else.
By the Way, the TSW DID that. We went to using the (easily accessible
on the original Raduino) I2C bus to drive the display (added minimal
extra cost and freed up a bunch of digital lines to use for the CW Keyer
and other controls.
Also, now that Ian HAS implemented the 4 wire (power ground, TX & RX)
Nextion interface that leaves 8 digital I/O pins freee on the old
display connector. Why has he not solved the major CW problem by
dropping the voltage divider altogether and using digital inputs for the
paddles dot and dash inputs? Switch the hand key portion of the keyer
over to use the Push To Talk (PTT) line, wire the hand key to use the
mike jack if you don't want to add another dedicated jack. This allows
auto select of hand key or paddles just by hitting the hand key or
pressing the paddles. Ask Ron, it took minimal code to do this. You
don't need PTT in CW operation and you don't normally need the hand key
in SSB operation so the PTT wire is easily co-opted for this.
By the way, this is not meant to be a rant though it may be turning into
one. I've seen many people complaining lately that the keyer doesn't
work properly but nobody has proposed or made a proper fix to the CEC
software. TSW has had the solution almost from the beginning but
everyone has drunk the "Nextion" kool-aid and the programmer for that
has chosen NOT to fix the CW issue. TSW has also tried to provide
readable and understandable PDF files explaining how our programs work
and any (usually minor) hardware changes necessary to make it work.
Jim Sheldon, W0EB
for TSW (Triumvirate Skonk Works)
website: www.w0eb.com
------ Original Message ------
From: "Jerry Gaffke via Groups.Io" <jgaffke@...>
To: [email protected]
Sent: 9/2/2018 11:19:23 PM
Subject: Re: [BITX20] CW OPERATION
Ian's software is the most popular update available for the uBitx.
He has added a lot of functionality to the rig and that is to be
applauded.
It's taken months of free time for him to bring it to this level.
Could well be that Ian doesn't use CW much, and CW is not a priority
for him.
Getting an iambic keyer to feel right is best done by a serious CW
operator.
I'd think Jim Sheldon would be an excellent candidate.
Jerry, KE7ER
On Sun, Sep 2, 2018 at 08:00 PM, Jim Sheldon wrote:
I don't like to be overly critical, but I've been hinting for months
now. I am now openly stating that KD8CEC's software has it wrong and
it's been wrong from the beginning. I call on Ian Lee to clean up his
code and get it right before he adds any more junk to his programs.
Jim, W0EB
|
9h1avlaw?
of course you risk outof band transmissions if you aren't at least able to recognize which WAY your sideband is going, and how close to the band edge you are.....exactly the same is true of upper side band and lower sideband voice opeeration.? ?
We expect people with the General class or higher license class to understand those sideband type pesky issues...in fact, it is a question or two in the exam packet!? ? and if you were to use FM...or AM....then you have sidebands on BOTH sides.....so if
you're going to be a RADIO amateur you need to understand just a bit about MODULATION.....
Cheers, my friend!
gordon
toggle quoted message
Show quoted text
If you are near the band edge you risk out of band transmissions
On Mon, Sep 3, 2018 at 4:35 AM Gordon Gibby < ggibby@...> wrote:
You can do it the other way around, with the transmitter upset, but then you have to be absolutely certain that the user knows that their transmissions are offset from the dial number.
That’s not terrible, that’s exactly what happens when you’re doing upper or lower sideband, and certainly when you’re doing pseudo CW by injecting an pure audio sinewave signal into a single side band system.? FLDIGI will do that, and you can even rig
it so your computer shows your correct transmitting frequency
On Sep 2, 2018, at 22:31, Jim Tibbits < ab7vf1@...> wrote:
Gotta offset,? can't hear em on the carrier
On Sun, Sep 2, 2018 at 7:01 PM W2CTX < w2ctx@...> wrote:
Found this video explaining CW Zero-beating.? So based on this explanation the following is illustrated
for 7.040.000:??? Dial displays 07.040.000, you transmit on 07.040.000, and the receive is offset by the
sidetone value.
Of course this is based on the video being correct.
rOb
|
Well maybe no one is paying attention but our software has CAT control, S-meter display, Pass Band Tuning, and
we build "memory manager" into the software so, you do not need a pc to change things. We also have a
companion Remote Control Program that allows control of the uBITX from a PC.? We also include keyboard control and
keyboard CW sending.
We are not in competition with Ian, we are just a few guys trying to make the best uBITX possible.? We make our
efforts available if people want to try them.
rOn
On September 3, 2018 at 9:00 AM MadRadioModder <madradiomodder@...> wrote:
Jim… I think you may have missed many of the positive features of the Nextion display… and in particular BECAUSE of that editor, anyone can move those, how did you call it… clutter?, things around… add and subtract easily to fit their needs without understanding and writing hundreds of lines of code like others implementations?.? That is a real BIG plus.? And… if the popularity of the Nextion keeps up, it will be no time before, feeling left out of the game, the “competition” follows suit with their own clone-ish display.? Now Ian’s code isn’t perfect, but it has brought us a lot of positive things… decent CAT control, usable “S” meter circuitry, IF shift for attenuation… etc.? And the memory manager.? Yeah at some point it makes sense for some real programmers to do a rewrite… ? Dumping on Ian isn’t a good sales tactic given his base… ?
--
…_. _._
?
|
It has to be programmed to work that way, but we do it in all of our recent sketches. There is no reason why it can't be programmed in the other sketches if the programmer choses to do so.
Jim
toggle quoted message
Show quoted text
------ Original Message ------ From: "Joe Milosch" <zzmiloschxx@...> To: [email protected]Sent: 9/3/2018 8:05:15 AM Subject: Re: [BITX20] CW OPERATION On Mon, 03 Sep 2018 12:23:57 +0000
"Jim Sheldon" <w0eb@...> wrote:
Hi, I just want to be sure I understand. The PTT line can
be used for straight CW keying? It seems reasonable,
but I have to ask. Would this be true for any of the sketches?
Thanks,
Joe KN4OND
Thank Jerry, but in all of the software put out by the Triumviratw Skonk
Works from our first public release for the original NANO and ever
since, CW has not only worked properly but the Keyer has too. We
figured out early on that using the voltage divider was NOT and still is
NOT the way to go. Using 2 inputs and learning how to use the available
(timer not pin) interrupts properly works just fine. Our software
(written mostly by Ron, W2CTX) addressed the CW problem early on.
There is no need for me to use Ian's sodftware as it is so full of
work-arounds, not fixes to all the problems that have cropped up that I
refuse to use it. His source code is so convoluted that even the most
experienced programmers on this group have given up trying to fix it for
him.
The Nextion display is getting so cluttered up with extra buttons &
menus that you almost can't read the frequency on it any more. It
started out being a pretty nice addition and now is so cluttered as to
be almost unusable. It's also a "Single Source" display with a GUI
editor that most people can't even figure out how to use. Where's the
utility in that?
What are all of those who spent and are spending LOTS of money just for
the Nextion display alone, trying to make their uBITX $119 or $129 kit
radio look like a $2000 or higher big name radio going to do when that
Chinese company decides to charge hundreds of dollars for the use of
their editor (since it seems to have gotten popular) and raises their
prices astronomically for the Nextion because they are selling to the
hams at such a rate or quits production because the market dries up?
Frankly, the original LCD was quite adequate for a rig of this caliber
and all of the problems involved in using it should have been addressed
before even thinking of trying something else.
By the Way, the TSW DID that. We went to using the (easily accessible
on the original Raduino) I2C bus to drive the display (added minimal
extra cost and freed up a bunch of digital lines to use for the CW Keyer
and other controls.
Also, now that Ian HAS implemented the 4 wire (power ground, TX & RX)
Nextion interface that leaves 8 digital I/O pins freee on the old
display connector. Why has he not solved the major CW problem by
dropping the voltage divider altogether and using digital inputs for the
paddles dot and dash inputs? Switch the hand key portion of the keyer
over to use the Push To Talk (PTT) line, wire the hand key to use the
mike jack if you don't want to add another dedicated jack. This allows
auto select of hand key or paddles just by hitting the hand key or
pressing the paddles. Ask Ron, it took minimal code to do this. You
don't need PTT in CW operation and you don't normally need the hand key
in SSB operation so the PTT wire is easily co-opted for this.
By the way, this is not meant to be a rant though it may be turning into
one. I've seen many people complaining lately that the keyer doesn't
work properly but nobody has proposed or made a proper fix to the CEC
software. TSW has had the solution almost from the beginning but
everyone has drunk the "Nextion" kool-aid and the programmer for that
has chosen NOT to fix the CW issue. TSW has also tried to provide
readable and understandable PDF files explaining how our programs work
and any (usually minor) hardware changes necessary to make it work.
Jim Sheldon, W0EB
for TSW (Triumvirate Skonk Works)
website: www.w0eb.com
------ Original Message ------
From: "Jerry Gaffke via Groups.Io" <jgaffke@...>
To: [email protected]
Sent: 9/2/2018 11:19:23 PM
Subject: Re: [BITX20] CW OPERATION
Ian's software is the most popular update available for the uBitx.
He has added a lot of functionality to the rig and that is to be
applauded.
It's taken months of free time for him to bring it to this level.
Could well be that Ian doesn't use CW much, and CW is not a priority
for him.
Getting an iambic keyer to feel right is best done by a serious CW
operator.
I'd think Jim Sheldon would be an excellent candidate.
Jerry, KE7ER
On Sun, Sep 2, 2018 at 08:00 PM, Jim Sheldon wrote:
I don't like to be overly critical, but I've been hinting for months
now. I am now openly stating that KD8CEC's software has it wrong and
it's been wrong from the beginning. I call on Ian Lee to clean up his
code and get it right before he adds any more junk to his programs.
Jim, W0EB
|
I'm not "dumping" on Ian, merely trying to get him to WAKE UP and fix the problems he's kept missing in his software. ?It could be really good for ALL modes if he'd just listen to what a few of us have told him and fix his code. ?It's about time somebody got a bit forceful and tried to wake him up. That's all I'm doing here and we HAVE offered our help to him several times but he chose to ignore it. ?
He claims "open source" but I can't seem to find any reasonably readable code to even help fix these days.
Sorry, but I will continue to remind him until he fixes the problems.
As to the Nextion, ?Take a look at the picture on ?and see what a fully functional, UNCLUTTERED display looks like (it ain't a Nextion) and it's a heck of a lot cheaper.
I rest my case.
Jim - W0EB
------ Original Message ------
Sent: 9/3/2018 8:00:04 AM
Subject: Re: [BITX20] CW OPERATION
Jim… I think you may have missed many of the positive features of the Nextion display… and in particular BECAUSE of that editor, anyone can move those, how did you call it… clutter?, things around… add and subtract easily to fit their needs without understanding and writing hundreds of lines of code like others implementations?.? That is a real BIG plus.? And… if the popularity of the Nextion keeps up, it will be no time before, feeling left out of the game, the “competition” follows suit with their own clone-ish display.? Now Ian’s code isn’t perfect, but it has brought us a lot of positive things… decent CAT control, usable “S” meter circuitry, IF shift for attenuation… etc.? And the memory manager.? Yeah at some point it makes sense for some real programmers to do a rewrite… ? Dumping on Ian isn’t a good sales tactic given his base… -- …_. _._
|
Jim Sheldon
MadRadioModder