Date   
Re: WSPR, what am I doing wrong?

Brent DeWitt
 

That was it!  I was an idiot and didn't read the "rules" carefully enough.  Leading with a space only works if you have a _single_ character before a number, otherwise it needs to be at the end.  Thank you _very_ much!
--
Brent DeWitt, AB1LF
Milford, MA

Re: JS8mode heartbeat beacon...

Alan de G1FXB
 

U3 and QCX requires it to be added to the firmware
I think Hans already has already experimented with FT8, in addition a code module was written by one of our members.
The problem may be more of a time and space continuum in an existing well utilised 328.
We are going to need an upgraded U3 / QCXplus with an SD card slot to handle much more.......  :-)


QSX who knows for sure.
the features page suggests  it's digital ready
with a number of inbuilt modes.
While other features are added by an external USB device, PC, Laptop, mention is also made of an option of built in RPi Zero.......
In which case we can administrate those features ourselves, and not require support from Hans who can maintain his own closed QSX code base independently.

Alan

On 05/12/2019 18:48, Dean Smith wrote:
I see OZ2M has created Arduino code for sending JS8 heartbeat message beacon with rf zero project.
This mode is very simular to FT8. just expanded rather than signal and call exchanges, with chat modes, mailbox, comm speeds, beacon mode,APRIS . connecting via other stations. These are a few of it's features.
 Is there any way the humble U3/QCX,QSX would be able to make use any of this emerging weak signal mode??




-- 
Smell Czech corruptions are inevitable

Re: WSPR, what am I doing wrong?

Brent DeWitt
 

Well, no.  I added a space in front of the call as Hans did for his 5 character call in the manual.  I'll try it the other way around.
--
Brent DeWitt, AB1LF
Milford, MA

Re: We have 30 day until the QRSS New Year's Eve Celebration!

John Kirby
 

Thank you
John
N3AAZ

Re: U3S No output.

jim
 

Ok ...Not sure what you mean "one side of gate...other side of gate"...bias on bs170 determined by voltage on GATE ..Via R6 (4.7k) from R5 (variable)...measure GATE from GATE to GROUND ,,vary R5, GATE voltage should go from 0 to 5 volts ...(anything over about 2 volts on GATE turns the bs170 mosfet ON hard (Max current flow)
Max SMOKE ...to set bias I suggest looking at options on page 16 of assy manual ...the Voltage to DRAIN of bs170 is supplied (via T1) from PA terminal ...IF you have the option jumpers installed for 5 volt only operation, all you will see on bs170 DRAIN is 5 volts (not changing) ...

 Page 16 sez to set bias you should monitor current to module, then adjust R5 for "slight increase" in current to module ,,,As voltage to bs170 is supplied from PA pin via T1, I would suggest selecting the options on page 16 to "separate PA supply" , the feed SEPARATE 5 volts to PA pin...that way you can monitor current with a meter directly ...Adjust R5 for (maybe 10 Milliamps) ...Data sheet for bs170 sez 350 MA maximum (before SMOKE) at least at that point you'll be somewhere in the linear mode on the bs170 mosfet ...

IF you are getting an RF signal from CLK0, then you "should" be getting RF thru T1/C5 to the output Low-Pass Fiter ...

Jim

Re: LightAPRS-W (WSPR) Tracker

Mustafa Tan
 

Hi Tim,

I try to answer some of your questions below:

Has anyone successfully flown a LightAPRS-W around the world? 
Yes :)

Is a low pass filter needed for HF?  
You don't need a low pass filter for HF.

How do the two antennas interact? I envision the two antennas getting tangled or ripped off.
Antennas do not interfere with each other and getting tangled. VHF (APRS) antenna is very short (just 50 cm) comparing to HF antenna (5 m.)

Anyone know the LightAPRS-W current (i) specs?
Sleep mode:  3 mA, 
APRS TX : min 500 mA - max 800 mA

I see that the code will set APRS to the ISS frequency.  Has the ISS ever received this device? 
Not yet. It's very hard because of antenna polarisation. Pico balloons antennas are vertical, not suitable for satellite communication. 

Looking through the code it appears that only the standard WSPR packet is sent and not the added telemetry packet.  Is there code to add the telemetry packet? 
No. we didn't add it because it's really hard to manage it.

Since only 26 balloons can be in the air with the added telemetry packet, is there a systematic way to choose numbers?
Sort of. KD2EAT try to manage it : http://hojoham.blogspot.com/2016/10/known-flight-ids.html 

TA2MUN


On Thu, Dec 5, 2019 at 8:53 PM Tim Wiwel <tim.wiwel@...> wrote:
Has anyone used this tracker?   I see one drop of code was released to GIT back in Aug and only a little chatter here at that same time.    Looking through the code it appears that only the standard WSPR packet is sent and not the added telemetry packet.  Is there code to add the telemetry packet?  Since only 26 balloons can be in the air with the added telemetry packet, is there a systematic way to choose numbers?   In the code I see a clock offset variable.  Is setting that value as simple as connecting the output to my frequency counter?   I see other designs using low pass filters, at least one inductor and two caps.  Is a low pass filter needed for this design for HF.  From looking at the pictures it appears that there is a low pass filter on the VHF transmitter.   Maybe no one really cares about the 3rd harmonic of a 10mW  square wave. 

Several folks have asked if WSRP can be tracked on HABHUB and I see that it has been done many times.  Is there a pre-canned method to do this.   My son got an A in his python class and needs work...

Is this the correct forum to discuss such questions? 

Tim,  KM4EFW

On Mon, Dec 2, 2019 at 10:12 AM tim.wiwel via Groups.Io <tim.wiwel=gmail.com@groups.io> wrote:
Has anyone successfully flown a LightAPRS-W around the world?   Is a low pass filter needed for HF?  Any good ideas on antenna wire strain relief?  How do the two antennas interact?  It can get ruff at 35kft and I envision the two antennas getting tangled or ripped off. 

Anyone know the LightAPRS-W current (i) specs?The data sheet does not give clear average current consumption specs.  

I see that the code will set APRS to the ISS frequency.  Has the ISS ever received this device? 

Tim



Re: More paddles and keys ... Computer mouse innards

Eric KE6US
 

There is a very good reason why straight keys fell out of favor. Known as "glass fist" in the day, it is now recognized as carpel tunnel syndrome. A very painful malady then and now. A converted mouse essentially makes two side by side straight keys. And not very good ones. All the effort is in two fingers and associated tendons. At least in a traditional straight key, your fingers can relax and your much heavier duty wrist takes up the action.

Side to side keying eliminated glass fist for the most part. First with the cootie, then with the bug, then with the paddle. A hundred years of evolution proved the value of a side to side rocking motion of the hand which is held in a natural relaxed attitude. No stress on fingers if you're doing it properly. No stress on your wrist. Just your hand gently rocking on the edge of your palm.

There are lots of small paddles for portable operation. My favorite is still the Palm Paddle (no longer made, but available at Morse Express). It's 1x1x3". You can hold it in one hand and key with the other with both hands comfortably supported by your lap. You can't get any better than that for a trail friendly radio. I was using mine in that way sitting in a camp chair. A woman walked by with her young daughter, saw me, then briskly propelled her daughter past my campsite. I didn't realize what it must look like to see me sitting in a chair, fiddling with something in my lap staring off into the woods with a smile on my face. I turn the chair around now.

Eric KE6US

On 12/5/2019 9:52 AM, Paul WB6CXC wrote:
Has anyone converted a two-button mouse to a key? Not in software (but that's not a horrible idea), but just wiring the switches to an electronic keyer?  Left-clock for dot, right-click for dash?  It would be like a sideswiper, but with different finger motion.
--
Paul Elliott - WB6CXC

Re: More paddles and keys ... Computer mouse innards

Chris Wood
 

Paul
Years ago I used a keyer made by a friend which used two sets of relay contacts keyed by tapping the top leaf with the index and middle finger respectively.  Not quite the same as a mouse but same principle, and worked fine for input to the keyer.

Chris
G4CWS  G QRP 313


Re: WSPR, what am I doing wrong?

N3MNT
 

Did you add the space after your call when entering it?  The call must be XX#XXX even if your call is only 5 characters.

 

JS8mode heartbeat beacon...

Dean Smith
 

I see OZ2M has created Arduino code for sending JS8 heartbeat message beacon with rf zero project.
This mode is very simular to FT8. just expanded rather than signal and call exchanges, with chat modes, mailbox, comm speeds, beacon mode,APRIS . connecting via other stations. These are a few of it's features.
 Is there any way the humble U3/QCX,QSX would be able to make use any of this emerging weak signal mode??



WSPR, what am I doing wrong?

Brent DeWitt
 

I've been using my 40 mtr QCX for a few weeks now and have been constantly impressed by the quality and value.  Thank you Hans!

Yesterday I received and built the OLG1 GPS module and wired it up to the QCX.  Frequency calibration went smoothly and I appear to be within 1 Hz of zero-beating WWV at 10 MHz with the signal generator.  Then I tried to set up a WSPR beacon.

I believe I followed the setup instructions in the user manual and all the menus look "as advised".  I must be missing something though.  Returning from the menu the display reads "WSPR call" and none of the information shown in the manual.  As might be expected, it never transmits either.



Here's what I've checked and know:
- The QCX transmits fine, at about 4 Watts, with a straight key or iambic paddle, so those input lines are clear.  I can monitor the output power in a roughly calibrated manner.
- The OLG1 serial data is as-expected into a serial terminal (TeraTerm) on the PC and the 1 pps is apparently working from the success of the frequency calibration.
- The QCX is running T1.02b firmware and all other functions I've tried seem to work.

So, at this point, I'm pretty well convinced it's operator error.  Any thoughts/corrections would be welcome.

--
73,
Brent DeWitt, AB1LF
Milford, MA

Re: More paddles and keys ... Computer mouse innards

Lawrence GJ3RAX
 

On 5 Dec 2019, at 17:52, Paul WB6CXC <paul@...> wrote:

Has anyone converted a two-button mouse to a key? …
Try these web pages:

http://www.n1rwy.org/?p=433

https://www.slideshare.net/parveshtaneja9/connecting-morse-key-to-pc-using-an-optical-mouse

https://www.eham.net/article/5373

There are probably a lot more out there but this is a start to inspire you.

73, Lawrence GJ3RAX

Re: LightAPRS-W (WSPR) Tracker

Tim Wiwel
 

Has anyone used this tracker?   I see one drop of code was released to GIT back in Aug and only a little chatter here at that same time.    Looking through the code it appears that only the standard WSPR packet is sent and not the added telemetry packet.  Is there code to add the telemetry packet?  Since only 26 balloons can be in the air with the added telemetry packet, is there a systematic way to choose numbers?   In the code I see a clock offset variable.  Is setting that value as simple as connecting the output to my frequency counter?   I see other designs using low pass filters, at least one inductor and two caps.  Is a low pass filter needed for this design for HF.  From looking at the pictures it appears that there is a low pass filter on the VHF transmitter.   Maybe no one really cares about the 3rd harmonic of a 10mW  square wave. 

Several folks have asked if WSRP can be tracked on HABHUB and I see that it has been done many times.  Is there a pre-canned method to do this.   My son got an A in his python class and needs work...

Is this the correct forum to discuss such questions? 

Tim,  KM4EFW

On Mon, Dec 2, 2019 at 10:12 AM tim.wiwel via Groups.Io <tim.wiwel=gmail.com@groups.io> wrote:
Has anyone successfully flown a LightAPRS-W around the world?   Is a low pass filter needed for HF?  Any good ideas on antenna wire strain relief?  How do the two antennas interact?  It can get ruff at 35kft and I envision the two antennas getting tangled or ripped off. 

Anyone know the LightAPRS-W current (i) specs?The data sheet does not give clear average current consumption specs.  

I see that the code will set APRS to the ISS frequency.  Has the ISS ever received this device? 

Tim

Re: More paddles and keys ... Computer mouse innards

Paul WB6CXC
 

Has anyone converted a two-button mouse to a key? Not in software (but that's not a horrible idea), but just wiring the switches to an electronic keyer?  Left-clock for dot, right-click for dash?  It would be like a sideswiper, but with different finger motion.
--
Paul Elliott - WB6CXC

Re: QSX

Jim Manley
 

Gerry,

I’m about another 50% beyond you in experience (or at least longevity), but, I've spent about an equal amount of time in hardware engineering - not just electronics, but everything from power generation/conversion, structures, hydraulics, pneumatics, etc.  At the ~30-year point, you should know that implementation (which is more than just programming/coding) typically only occupies an average of about 15% of the total time consumed by a significant project.  The remainder of the time is consumed by:

- Careful identification of customer desires (and ferreting out what they really need)

- Generating developer requirements (desires and requirements are not anywhere close to being the same, at first, and need to be fully aligned, or disaster will occur)

- A high-level design identifying the components and how they fit together

- Low-level designs of each of the components, which usually have hierarchical dependencies

- A thorough test plan (including the actual procedures/scripts to be executed, plus any required realistic test data)

- A debugging strategy (identifying specific tools to be used)

- Configuration documentation (for IT type folks who may need to install, maintain, and upgrade the system)

- End-user documentation (at least built into the system, if not including stand-alone documents)

- A maintenance plan (for both resolving bugs through version upgrades, as well as providing new-feature additions).

Not understanding the above is why people are surprised when the time required to complete a project often requires around a whole number multiplier (usually much) larger than one that has to be applied to the planned time.  There are a bunch of reasons for this, and the most frequent is simply poor planning, if there's any real planning at all.  Complexity is another big reason, but, it's ... complex!  For small projects (and I mean small, as in weeks of effort total, with maybe a few hundred new and unique lines of code), you don't need to produce a Department of Defense contractor volume of paperwork.  However, if you haven't at least made very organized notes addressing everything in the above list that's appropriate for the scale of a project, it will ultimately fail.  That's not my opinion, it's a fact that numerous examples of failure litter the side of the road of systems development.

You might be surprised to hear that the average software developer can only produce about a dozen bug-free, feature-complete (at the atomic level of features), unique lines of code per day (integrating existing code is much more common).  If development isn't performed through self-discipline, that can include slinging hundreds of lines of initial stabs at code per day, much of which has to be heavily-modified/tossed because it doesn't achieve the goals of being bug-free and feature-complete.  If you really don't know exactly what the customer/end-user is thinking with respect to what the system is supposed to do, you will waste a huge amount of resources just finding out you really don't know, much less getting to that level before you can deliver anything useful.

You might also be surprised that the productivity ratio between an experienced, successful software developer, compared to the average one (not the least-experienced/successful, the _average_) is about 30:1 in terms of the resources (time, money, tools, etc.) needed to produce a bug-free and feature-complete system.  Even more unexpected is that this ratio is pretty much independent of other variables such as whether the entire system is being built from scratch (for proprietary reasons), or is being assembled to include a large fraction of open-source material.  It often takes more work to integrate components that weren't specifically designed to work together than to just start over, assuming you really understand what's actually needed in the first place.  Producing the wrong answer at a speed approaching that of light is not of much interest to customers.  If it's expressed in a language that the customer doesn't understand, they'll be even much, much, much less impressed.

The main factors affecting complexity start with how much of the functionality has been developed before (experience with specific algorithms and the customer operating environment).  Next, is a system being developed for the same:

- Platform (hardware things like specific processor or family, memory configuration, I/O devices , "glueware" that integrates hardware components, etc.)

- Software environment (OS, utilities, etc.)

- Software development tools (programming language(s), integrated development environment(s), compiler(s)/assemblers, code libraries, etc.)

- Open-source and/or proprietary libraries

Other critically-important factors are the experience level with all of the above by the developers, along with whether they've worked closely together before, and are they physically collocated, or strewn around the planet.  These lists are just the tip of the iceberg, but, any good book or on-line course in systems or software engineering (they're related, but, different disciplines) can provide a much more detailed enumeration.

I suspect that Hans is developing the OSX system that includes a lot of "I haven't done exactly that before", and in some cases, "I've never done any of that before" features.  The "haven't done exactly that before" things do benefit from the similar experience, but, they can also lead to unexpected difficulties, especially when dealing with real-world phenomena such as electromagnetic noise and signals that "aren't supposed to be like that".  That's why realistic testing data/signals/etc., are so critical in systems development.  Made-up test data/whatever is never good enough for more than toy projects - you have to collect lots of stuff from the real world and analyze it to make sure it covers as many corner cases as you can possibly foresee.

He's also working at the Olympic gold-medal level of having a day job (AIUI), and is supporting, and will continue to support, existing products that are requiring a few bug fixes as well as new features (that almost always bring with them their own bugs).  He may even be operating at the Olympic platinum-medal level and have people around him who depend on him maintaining his sanity while providing for them, despite people bugging him relentlessly with "When will it be ready?" questions.

Plus, customers/users will do things that developers just absolutely had no clue were possible, let alone likely (in the Navy, you learn early that there's no such thing as sailor-proof, which is a much larger superset of fool-proof).  The forum provides plenty of evidence of the "cleverness" of we users, and many of us here are probably assumed to be "sophisticated", which may not always be a good assumption!  Then again, we should all familiar with the constituent words/fragments that make up the word "assume".

Your mileage may vary, objects in mirror are closer and more dangerous than they appear, do not spindle, fold, or mutilate, and, of course, batteries are _not_ included!

All the Best,
Jim

"Murphy was an optimist."  -- An Engineer

"Problems worthy of attack, prove their worth by fighting back."  -- Piet Hein, Danish philosopher

"If at first you don't succeed, try, try, again.  Then quit.  There's no sense making a fool of yourself."  -- W.C. Fields




On Thu, Dec 5, 2019 at 1:59 AM Gerry Kavanagh via Groups.Io <gerrykav=yahoo.co.uk@groups.io> wrote:
Hi Larry...
there is a degree of defensiveness in your reply that I don't believe is warranted. I just said it would be nice to have the occasional update, not an in-depth feature burn-down. I have seen many projects 'go dark' with communication and soon after declare that the project was dead, so forgive me if I am a bit reactive over something I had been looking forward to.
Further, I have been a programmer for 30+ years, and have never had situation where some idea of the magnitude of the project vs. completion state wasn't known. I get that complexity is hard to manage, but I didn't think I was asking much - perhaps I was wrong.
I have plenty to occupy me, but occasionally the QSX will be mentioned after some time out of mind and it reminds me of how much I had been looking forward to this project.
/ Gerry

Re: U3S No output.

wes377@...
 

Don... all 3 rail of the transistors are connected as per schematic of the PA section 
But I’m still only using 5volts to be safe.
Im thinking I could take them out 1 by 1 to see if one is faulty.

Wes
--
wes377@...

Re: U3S No output.

wes377@...
 

Don.... on one side of the BS170 gate pin for example I get 2volts then on the other side I get 3volts = 5volts ((((depending where the trimmer is at))). Across from the two outside pins I get 5volts.  
--  Is that what you mean? I’m learning here. 
I have a dummy load. And the Unit is 6 inches away from the ts590sg. Should be booming in.
im getting 1.7volts from CLK0 so I assume that part is working... GPS works perfectly very impressed with that module :-).


Wes

Wes
wes377@...

Re: #qcx #firmware 1.03 release (CAT, real time clock) #qcx #firmware

Gregg Myers
 

Hi Hans,

Slightly correction to my earlier email. When I tried testing your sequence, I started on 8.11 and not 8.13. I guess if I started n 8.13, I would naturally have to change the encoder to get to 8.11 or 8.12 and it would have worked that way even better.

73,
Gregg


On Thu, Dec 5, 2019 at 6:04 AM Gregg Myers via Groups.Io <gregg.w7grm=gmail.com@groups.io> wrote:
Hi Hans,

Thanks for testing this. I had used a slightly different sequence.
1. Power is off
2. Plug in GPS
3. Power on
4. Go to Alignment 8.11
5. At this point, I start to see the weird behavior... For example, the QCX automatically seems to get out of the menu without me doing anything (showing VFO A and blank line underneath without me doing anything). But actually, I find it is still in the menu settings if I turn the rotary encoder back and forth 
6. If I go back to 8.11 then hit select, It doesn't seem to calibrate. But just now I was playing with it and turning the rotary encoder between 8.11 and 8.12, eventually it starts to calibrate correctly.

If I use your sequence I still saw my menu item appear to blank out when I hot plugged the GPS, but trurning the rotary encoder back and forth to 8.11 and 8.12 made it work.

So the behavior still seems different compared to T1.02b, where I never had the blank screen and I never had to turn rotary encoder back and forth. But anyway, I did get it to calibrate.

I had similar behavior on two different QCX. I didn't change fuse settings on either unit. Maybe I have noise eminaiting from my GPS connection? But I never saw this on earlier firmware.

Anyway, I can see how I can get it to work now. I like the new features you added in T1.03. keep up the good work!

73,
Gregg W7GRM



On Wed, Dec 4, 2019 at 10:55 PM Hans Summers <hans.summers@...> wrote:
Hello Gregg

I have just tried a fresh QCX-40 with a fresh 1.03 chip, and the frequency calibration worked fine. Steps:

1) Go to menu 8.13
2) Plug in GPS
3) Wait some seconds until I see satellite lock
4) Turn the rotary encoder one click anticlockwise to 8.12 and wait 6-7 seconds for the Sys Osc cal
5) Turn the rotary encoder one click anticlockwise to 8.11 and wait 6-7 seconds for the Ref Clk cal
6) Unplug GPS
7) Go to menu items 8.5 and 8.6 to check calibrations ran fine

If you have a different sequence of steps and it is failing please can you specify, so I can try that? 

Are you sure your fuse settings are correct (no divide-by-8 fuse etc)?

73 Hans G0UPL



On Thu, Dec 5, 2019 at 7:54 AM Gregg Myers <gregg.w7grm@...> wrote:
Has anyone else tried to calibrate their QCX crystal frequencies with GPS with firmware T1.03? It doesn't work for me. I get strange button responses, and the QCX never does update the crystal frequencies properly or at all. I reverted back to T1.02b and the GPS calibration works fine.

73,
Gregg W7GRM

On Wed, Dec 4, 2019 at 9:05 AM Tom N9GVP <tsnyder35@...> wrote:
Thanks, Hans, for the info on the time display when in split mode with CW decode ON.  It really is just a cosmetic issue.  Not a problem at all.
-Tom

Re: U3S No output.

Don--AE4DW
 

I would expect you to, definitely. Are you using the QLG-1 gps board with the U3S?

As I was building mine, modifying, and testing, with a single BS170 into a 50 ohm resistor as a quick and easy dummy load, and a a random length wire on my TS440 for receive-only purposes, the 440 heard the U3S from 5-10 feet away and decoded its transmission with no problems.

As has been mentioned earlier, the output section is a pretty simple circuit. I assume you've confirmed you have proper bias and supply voltages on the BS170s? And I'm sure you've been over parts placement a ton of times to ensure no wrong or missing parts?

 

 

 

Re: We have 30 day until the QRSS New Year's Eve Celebration!

Hans Summers
 

Hi John

Agreed with Alan

Additionally: selecting banks via the three bank input selection pins doesn't write anything to EEPROM so doesn't cause wear.

73 Hans G0UPL 

On Thu, Dec 5, 2019, 17:34 Alan G4ZFQ <alan4alan@...> wrote:
> ... which method causes * least stress * on eeprom?

John,

SAVING "wears out" the EEPROM. Method 1 or 2 saves. But you are not
going to wear out the EEPROM with occasional changes.
It is only relevant for serial programming when some one uses a
procedure that changes frequency maybe every second. Then v1.03 is
desirable. I've not checked but many modern EEPROMs specify a minimum of
100,000 writes.

73 Alan G4ZFQ

>
> ...method one...
>      Serial load;
>      05 = 7,000,000
>      08 = 7,000,002
>      11 = 7,000,004
>      etc thru
>      26 = 7,000,014
>
> ...method two...
>      DIP Switch load
>      same freqs into same locations
>
> ...then...
>      Band Select for Clock1 output via
>      B2, B1, B0