Date   

Re: QCX - Adding a small speaker & amplifier - spare power point on PCB?

K4LXY
 

I should have added that for use with the QCX, I added a 6v zener diode and resistor so that I could feed the zero beat indicator directly with 12/13.8v.
Howard


Re: QCX - Adding a small speaker & amplifier - spare power point on PCB?

K4LXY
 

Steve
It's the last page in the photo gallery
https://groups.io/g/QRPLabs/album?id=42540

I seem to be pitch-challenged so have zero-beat indicators on all my rigs. I've tried quite a variety.  The smallest one, that would fit nicely with the QCX, is the K6XX one (comes up with Google) that I have in my Elecraft KX1 and K2.  I recently tried a small self-contained one from QRP Guys, but it seemed too wide.  I've sent it back and they are testing it.

Overall, I've had the best luck with a design I published in QRP Quarterly in 2014. I can dig up the schematic if you want.  I believe that's the design in the two included in the photos. 

Howard K4LXY


Re: SI5351 VFO/sig gen for up conversion receiver

Ron Carr
 

About the noise during encoder action:   Many SI5351 libraries reset the SI5351 every time a new frequency is loaded.  Hans has written some notes about this issue, and the resets are not needed when the new frequency is not very different from the previous frequency.   Flickering on loud signals could be the same issue if you had RIT active and the radio firmware was loading new frequencies.

Ron K1URC


Re: NEED YOUR OPINIONS #qcx

Harv - K2PI
 

I did the same, and buying and replacing the AT Mega chip fixed it.   Reprogramming did not work.  It was completely fried.   

What does the display show?
--
Harv
K2PI
Warrenton, VA


Re: Hans, a request to consider please?

Adrian Scripcă
 

Hi Ken,

You are right, the key format is the help instruction is wrong. Thanks for catching that. I fixed the problem and re-packaged the last release to contain the fix. 

73! Adrian, YO6SSW

On Sat, Apr 7, 2018 at 3:23 PM, KEN G4APB via Groups.Io <lfoofui.nbz42@...> wrote:
Hi Adrian,
Version: v1-12-g18e1199 built at 1523099129

In that case your help instructions when the programme is run is missing the plural 's' on 'transmission', and the full stop before 'enabled':-

show [input-file] [key] 
 
        Loads the .eep file pointed at by the [input-file] parameter and
        shows the setting at the provided key.
        Example:
                u3s-eeprom-tool show bob.eep transmission[0]enabled

73 Ken G4APB



Re: Hans, a request to consider please?

KEN G4APB
 

Hi Adrian,
Version: v1-12-g18e1199 built at 1523099129

In that case your help instructions when the programme is run is missing the plural 's' on 'transmission', and the full stop before 'enabled':-

show [input-file] [key] 
 
        Loads the .eep file pointed at by the [input-file] parameter and
        shows the setting at the provided key.
        Example:
                u3s-eeprom-tool show bob.eep transmission[0]enabled

73 Ken G4APB


Re: Hans, a request to consider please?

Adrian Scripcă
 

Hi Ken,

The proper key to be used is transmissions[0].enabled please mind the punctuation and the plural for transmissions. It's basically a quick way to address that particular setting. The index between the brackets is the index of the transmission slot and should be between 0 and 15.

73! Adrian, YO6SSW

On Sat, Apr 7, 2018 at 2:58 PM, KEN G4APB via Groups.Io <lfoofui.nbz42@...> wrote:
Hi Adrian,
ran into this problem...I type in.....

C:\Users\Downloads\u3s-eeprom-tool-win64>u3s-eeprom-tool show v3.12a.eep transmission[0]enabl
ed

and I get result....

ERROR: Failed to show key transmission[0]enabled. Cause: [json.exception.out_of_range.403] key 'tran
smission' not found

What happens if a slot is disabled? I tried various slots and configurations but get the same result.(Win64 version).

73 Ken G4APB



Re: Hans, a request to consider please?

KEN G4APB
 

Hi Adrian,
ran into this problem...I type in.....

C:\Users\Downloads\u3s-eeprom-tool-win64>u3s-eeprom-tool show v3.12a.eep transmission[0]enabl
ed

and I get result....

ERROR: Failed to show key transmission[0]enabled. Cause: [json.exception.out_of_range.403] key 'tran
smission' not found

What happens if a slot is disabled? I tried various slots and configurations but get the same result.(Win64 version).

73 Ken G4APB


Re: Hans, a request to consider please?

Adrian Scripcă
 

Hi all,

Since Romania is an Orthodox country, it means the Easter is due this Sunday. This in turn means that the Easter bunny was hard at work and it's time to bring some presents. Here's a new release with some features that I was working on for the last days, namely edit and show.

The edit feature allows one to quickly edit an .eep file in-place by issuing one command, without having to first convert to JSON, edit the file with a text editor and then convert back to .eep.
The show feature allows one to quickly view value of a variable currently configured in an existing .eep without having to convert it to JSON first.

Usage examples:

Enabling the first transmission slot:
    u3s-eeprom-tool edit mike.eep transmissions[0].enabled true

Updating the eeprom message with one that contains three submessages (note the use of pipe character as message delimiter)
    u3s-eeprom-tool edit bob.eep message "CQ DE ZL1RS|C# M#|HELLO WORLD"

Checking the mode of the second transmission
    u3s-eeprom-tool show chris.eep transmissions[1].mode

Checking the whole second transmission
    u3s-eeprom-tool show chris.eep transmissions[1]


The error reporting has also been improved in order to be more meaningful and the help system was also improved with extra details and usage examples.

You can find the version containing the new features here: http://hq.scene.ro/u3s-eeprom-tool/v1-12-g18e1199/

Some words about the command-line rationale and future developments. 
There were a couple of reasons in going for a command line tool for editing the eeproms, namely:
  • it needs to be fast, small and able to run by itself without forcing the user to install any other dependencies
  • it needs to be able to run offline, without requiring the use of a connection (think of when you're somewhere remote with a laptop and you want to reprogram your U3S)
  • it needs to be able to be ran on all major used OS-es
  • it needs to be command line based so that it will be possible to make it part of an automated tool chain for whatever reasons. Besides the visual feedback displayed to the user, whenever a command is being ran the program returns an exit code to the OS whether the command was successful or not. This makes it able to include it in automation scripts
However, some people might be more comfortable with a GUI at different times. I have pondered long on the available options and I decided to develop a web based GUI frontend for the tool which will allow anyone to drag and drop an eep file onto a page, edit the desired settings and then download the new .eep file given there is enough interest for this, of course. Writing a desktop GUI is not practical due to platform/OS fragmentation and the toll that will be placed upon users in order to be able to install/run the graphical tool.

So please let me know your thoughts.

73! Adrian, YO6SSW



On Sat, Apr 7, 2018 at 12:51 PM, Chris Wilson <chris@...> wrote:
Hello Adrian,

Thanks for the info and apologies for doubting what I saw! ;)
I'll have a play with the new version later, much appreciated!

 Saturday, April 7, 2018

> Hi Chris, Sverre, Bob,


> I'm sorry for the confusion but those were the information from the
> document Hans provided. In order to eliminate any further confusion,
> I added the ability to query existing modes in the tool. New version
> released at https://hq.scene.ro/u3s-eeprom-tool/v1-11-g3a5b023/


> This will allow you to perform a call like u3s-eeprom-tool modes
> and have the list of known modes printed on the screen, like in the sample below:


> Available modes:
>         - RX (Receive only)
>         - FSKCW (FSK CW (slow))
>         - QRSS (Plain QRSS (slow))
>         - DFCW (DF CW (slow))
>         - SHELL (MFSK Hellschreiber (slow))
>         - HELL (Hellschreiber (standard speed))
>         - DXHELL (Hellschreiber (standard speed, DX=double))
>         - CW (CW (standard speed))
>         - CWID (CW ID (Callsign sent at 12wpm))
>         - FSK (FSK (standard CW-speed))
>         - WSPR (Standard 2-minute WSPR)
>         - WSPR15 (15-minute, 1/8th shift WSPR)
>         - TX_CW (Manually keyed transmitter mode: CW)
>         - TX_FSK (Manually keyed transmitter mode: FSK)
>         - OPERA05 (Opera 05)
>         - OPERA1 (Opera 1)
>         - OPERA2 (Opera 2)
>         - OPERA4 (Opera 4)
>         - OPERA8 (Opera 8)
>         - OPERA32 (Opera 32)
>         - OPERA65 (Opera 65)
>         - OPERA2H (Opera 2H)
>         - PI4 (PI4)
>         - JT91 (JT9-1)
>         - JT92 (JT9-2)
>         - JT95 (JT9-5)
>         - JT910 (JT9-10)
>         - JT930 (JT9-30)
>         - ISCATA (ISCAT-A)
>         - ISCATB (ISCAT-B)
>         - JT65A (JT65A)
>         - JT65B (JT65B)
>         - JT65C (JT65C)


> The feature I am currently working on is the ability to edit a
> certain part of the whole eep right from command line, for instance:



> u3s-eeprom-tool edit bob.eep message "#CS VMTX|#A0 #A1 #A3|"



> This will allow for quick .eep edits, without the need to first
> convert to json, edit things by hand and then convert back to .eep.
> It seemed to me that this feature will be convenient for U3S users.


> 73! Adrian, YO6SSW






--

 2E0ILY
Best regards,
 Chris                            mailto:chris@...



--
Best regards, Chris Wilson (2E0ILY)





Re: Will a U3S run with a USBAsp connected?

Chris Wilson
 

Hello Bob,

Thanks for that, I will have a play later, appreciate the reply and
warning, cheers.

Saturday, April 7, 2018

Hi Chris,
It does on mine, but my U3S is not standard so YMMV ... but be
aware that the U3S will reset after each new .eep file is loaded
(at least mine does), so you probably don't want to do that in
the middle of a 'live' transmission. 
73, Bob  ZL1RS




--

2E0ILY
Best regards,
Chris mailto:chris@...
--
Best regards, Chris Wilson (2E0ILY)


Re: Hans, a request to consider please?

Chris Wilson
 

Hello Adrian,

Thanks for the info and apologies for doubting what I saw! ;)
I'll have a play with the new version later, much appreciated!

Saturday, April 7, 2018

Hi Chris, Sverre, Bob,

I'm sorry for the confusion but those were the information from the
document Hans provided. In order to eliminate any further confusion,
I added the ability to query existing modes in the tool. New version
released at https://hq.scene.ro/u3s-eeprom-tool/v1-11-g3a5b023/

This will allow you to perform a call like u3s-eeprom-tool modes
and have the list of known modes printed on the screen, like in the sample below:

Available modes:
- RX (Receive only)
- FSKCW (FSK CW (slow))
- QRSS (Plain QRSS (slow))
- DFCW (DF CW (slow))
- SHELL (MFSK Hellschreiber (slow))
- HELL (Hellschreiber (standard speed))
- DXHELL (Hellschreiber (standard speed, DX=double))
- CW (CW (standard speed))
- CWID (CW ID (Callsign sent at 12wpm))
- FSK (FSK (standard CW-speed))
- WSPR (Standard 2-minute WSPR)
- WSPR15 (15-minute, 1/8th shift WSPR)
- TX_CW (Manually keyed transmitter mode: CW)
- TX_FSK (Manually keyed transmitter mode: FSK)
- OPERA05 (Opera 05)
- OPERA1 (Opera 1)
- OPERA2 (Opera 2)
- OPERA4 (Opera 4)
- OPERA8 (Opera 8)
- OPERA32 (Opera 32)
- OPERA65 (Opera 65)
- OPERA2H (Opera 2H)
- PI4 (PI4)
- JT91 (JT9-1)
- JT92 (JT9-2)
- JT95 (JT9-5)
- JT910 (JT9-10)
- JT930 (JT9-30)
- ISCATA (ISCAT-A)
- ISCATB (ISCAT-B)
- JT65A (JT65A)
- JT65B (JT65B)
- JT65C (JT65C)

The feature I am currently working on is the ability to edit a
certain part of the whole eep right from command line, for instance:


u3s-eeprom-tool edit bob.eep message "#CS VMTX|#A0 #A1 #A3|"


This will allow for quick .eep edits, without the need to first
convert to json, edit things by hand and then convert back to .eep.
It seemed to me that this feature will be convenient for U3S users.

73! Adrian, YO6SSW





--

2E0ILY
Best regards,
Chris mailto:chris@...
--
Best regards, Chris Wilson (2E0ILY)


Re: Hans, a request to consider please?

Chris Wilson
 

Hello Bob,

Thanks for that confirmation, it was the lack of the dash that caused
me to wonder. I uploaded to the U3S and of course it worked fine!

Saturday, April 7, 2018

Hi Chris,
That caught me too, but there are several variants of JT9
transmission mode available in the U3S.  According to the 3.12 operation pdf:
"The available modes are: None, FSKCW, QRSS, DFCW, Slow Hell, Hell,
DX Hell, CW, CW ID, WSPR, WSPR-15, TX CW, TX FSK, Opera05, Opera1,
Opera2, Opera4, Opera8, Opera32, Opera65, Opera2H, PI4, JT9-1,
JT9-2, JT9-5, JT9-10, JT9-30, ISCAT-A, ISCAT-B, JT65A, JT65B and JT65C."
... so JT91 in the .json encodes into the .eep file and makes the
U3S transmit in JT9-1.  (at least, it does here).
Note that your setting    "powerOrMessageIndex": 23     in JT9 will
be trying to send the 23rd sub-message in the messages parameter. 
That sub-message is probably unlikely to exist, so the JT9 will
send the 0th sub-message (e.g. the first one).
73, Bob  ZL1RS


On 7/04/2018 9:55 AM, Chris Wilson wrote:


Hello Adrian,
When I convert a working .eep file to a human readable .json file i am
seeing the JT9 mode shown as JT91
Is this expected please? Thanks, not sure how a copy / paste from the
.json file will format on the group but here goes:
"transmissions": [
{
"aux": 0,
"band": 1,
"enabled": true,
"frequency": 137548,
"mode": "WSPR",
"powerOrMessageIndex": 27
},
{
"aux": 0,
"band": 0,
"enabled": true,
"frequency": 137350,
"mode": "JT91",
"powerOrMessageIndex": 23
},




--

2E0ILY
Best regards,
Chris mailto:chris@...
--
Best regards, Chris Wilson (2E0ILY)


EEP editor

Gray Remlin
 

A GUI EEP editor written in Python3 is available at

https://github.com/gryrmln/EEPeditor

This is Alpha software - testing stage.
This software is primarily targeted at the Raspberry Pi but as it is written in Python...

Installation on Debian based systems is trivial. Should you choose to try out this software on Windows or MacOS, please help each other out with installs, I will revisit this Group and collate
all the posts to rework the installation instructions.

When editing any field do not forget to hit the 'Enter' key before leaving it to register your input.
This is currently a safety feature that may be removed in the future.

If you launch the software in a console you will be able to see certain actions and any errors.

The current version does not fully support v3.09 eep files as the mapping is not complete,
 so do not attempt to flash the resulting output, v3.12a should work.

Gray


Re: Hans, a request to consider please?

KEN G4APB
 

Hi Paul and Adrian,
many thanks both of you. You both gave me the same correct reply and it all worked for me. I was so far off the mark!
I managed to create an .eep file entirely from an Excel spreadsheet and sucessfully decoded it back in Adrians' programme. I am now getting a really good understanding of the workings of the .eep file.

Just a small point Adrian;
You have in CONFIG:-

 "config": {
        "Iv": false,
        "Tn": false,
        "TxS": 15,
        "XW": false,
        "x2": false
In fact, the 'false' fields are shown as '0' on the actual U3S display, and the TxS number (15) would show as set.
 
A note to Hans here:- this is a small anomaly here The 'modes/ 'slots' are labelled 0-F I would expect the TxS field to be similar, not 0-15. Also you can incorrectly set the TxS number higher than 15.

73 Ken G4APB


Re: Hans, a request to consider please?

Adrian Scripcă
 

Hi Chris, Sverre, Bob,

I'm sorry for the confusion but those were the information from the document Hans provided. In order to eliminate any further confusion, I added the ability to query existing modes in the tool. New version released at https://hq.scene.ro/u3s-eeprom-tool/v1-11-g3a5b023/

This will allow you to perform a call like u3s-eeprom-tool modes and have the list of known modes printed on the screen, like in the sample below:

Available modes:
- RX (Receive only)
- FSKCW (FSK CW (slow))
- QRSS (Plain QRSS (slow))
- DFCW (DF CW (slow))
- SHELL (MFSK Hellschreiber (slow))
- HELL (Hellschreiber (standard speed))
- DXHELL (Hellschreiber (standard speed, DX=double))
- CW (CW (standard speed))
- CWID (CW ID (Callsign sent at 12wpm))
- FSK (FSK (standard CW-speed))
- WSPR (Standard 2-minute WSPR)
- WSPR15 (15-minute, 1/8th shift WSPR)
- TX_CW (Manually keyed transmitter mode: CW)
- TX_FSK (Manually keyed transmitter mode: FSK)
- OPERA05 (Opera 05)
- OPERA1 (Opera 1)
- OPERA2 (Opera 2)
- OPERA4 (Opera 4)
- OPERA8 (Opera 8)
- OPERA32 (Opera 32)
- OPERA65 (Opera 65)
- OPERA2H (Opera 2H)
- PI4 (PI4)
- JT91 (JT9-1)
- JT92 (JT9-2)
- JT95 (JT9-5)
- JT910 (JT9-10)
- JT930 (JT9-30)
- ISCATA (ISCAT-A)
- ISCATB (ISCAT-B)
- JT65A (JT65A)
- JT65B (JT65B)
- JT65C (JT65C)

The feature I am currently working on is the ability to edit a certain part of the whole eep right from command line, for instance:

u3s-eeprom-tool edit bob.eep message "#CS VMTX|#A0 #A1 #A3|"

This will allow for quick .eep edits, without the need to first convert to json, edit things by hand and then convert back to .eep. It seemed to me that this feature will be convenient for U3S users.

73! Adrian, YO6SSW


On Sat, Apr 7, 2018 at 2:38 AM, Bob Sutton via Groups.Io <zl1rs@...> wrote:
Hi Chris,

That caught me too, but there are several variants of JT9 transmission mode available in the U3S.  According to the 3.12 operation pdf:

"The available modes are: None, FSKCW, QRSS, DFCW, Slow Hell, Hell, DX Hell, CW, CW ID, WSPR, WSPR-15, TX CW, TX FSK, Opera05, Opera1, Opera2, Opera4, Opera8, Opera32, Opera65, Opera2H, PI4, JT9-1, JT9-2, JT9-5, JT9-10, JT9-30, ISCAT-A, ISCAT-B, JT65A, JT65B and JT65C."

... so JT91 in the .json encodes into the .eep file and makes the U3S transmit in JT9-1.  (at least, it does here).

Note that your setting    "powerOrMessageIndex": 23     in JT9 will be trying to send the 23rd sub-message in the messages parameter.  That sub-message is probably unlikely to exist, so the JT9 will send the 0th sub-message (e.g. the first one).

73, Bob  ZL1RS


On 7/04/2018 9:55 AM, Chris Wilson wrote:
Hello Adrian,

When I convert a working .eep file to a human readable .json file i am
seeing the JT9 mode shown as JT91

Is  this expected please? Thanks, not sure how a copy / paste from the
.json file will format on the group but here goes:

"transmissions": [
        {
            "aux": 0,
            "band": 1,
            "enabled": true,
            "frequency": 137548,
            "mode": "WSPR",
            "powerOrMessageIndex": 27
        },
        {
            "aux": 0,
            "band": 0,
            "enabled": true,
            "frequency": 137350,
            "mode": "JT91",
            "powerOrMessageIndex": 23
        },
        {







Re: SI5351 VFO/sig gen for up conversion receiver

ik0vaq@...
 

No Ken, I'm using the VFO in a homebrew up conversion receiver....
73
Alex


Re: QRX-20 - I Shorted Something

Alan G4ZFQ
 

Could someone point me in a direction for trouble shooting?
I checked the voltages from the circuit diagram and most seem ok.
George,

It would most probably help if you told us what voltages were not OK. And what they are.

73 Alan G4ZFQ


Re: No Dits; Only Dahs

Ed Vignati
 

Did you install an external jack? I put my radio in an aluminum project box and installed a stereo jack.

I had the same problem you are speaking about, I put a wire on the wrong terminal.

It's in the wiring, gotta be.

Eddie kj4fgi 

On Fri, Apr 6, 2018 at 11:19 PM, Bill Watkins <kf7yxs@...> wrote:
Hi,

I've read and searched, and I cannot find a similar problem.  I have hooked an external paddle to the qcx.  I get dashes, but no dots when the paddles are pressed.  What am I doing wrong?  I have gone to the keyer menu and changed to either iambic and to ultimatic in order to see the results. 

In straight key, I get tone as long as one paddle is held.  In iambic and ultimatic, I  get a series of dashes; no dots

Appreciate any ideas.

Bill
K0WHW



Re: No Dits; Only Dahs

William Martin
 

Bill,

Check the stereo jack to see if the DIT side is functional.  Some of those parts are pretty fragile.

Bill N7EU


No Dits; Only Dahs

Bill Watkins
 

Hi,

I've read and searched, and I cannot find a similar problem.  I have hooked an external paddle to the qcx.  I get dashes, but no dots when the paddles are pressed.  What am I doing wrong?  I have gone to the keyer menu and changed to either iambic and to ultimatic in order to see the results. 

In straight key, I get tone as long as one paddle is held.  In iambic and ultimatic, I  get a series of dashes; no dots

Appreciate any ideas.

Bill
K0WHW