Date   

Re: Hans, a request to consider please?

Adrian Scripcă
 

I forgot to mention that at the above mentioned link you will find a folder named v1-3-g8c2c12b which is the current version of the tool. Enter that folder and you will find the archives for every platform.

73! Adrian, YO6SSW

On Wed, Apr 4, 2018 at 7:46 PM, Adrian Scripcă <benishor@...> wrote:
Hi guys,

I spent quite some time laying out the foundation for the program, extracting the domain model, writing the u3s v312 decoder, intel hex decoder, json export, cross-platform build for windows, linux, osx and I believe we're on a good track. Here's a first version for all of you to test since I do not own a U3S. 

Please go to https://hq.scene.ro/u3s-eeprom-tool/ pick the archive corresponding to your computer platform and give the binary a try. The basic syntax is:

u3s-eeprom-tool decode u3s-dump.eep u3s-dump.json

Basically that's asking the tool to load up u3s-dump.eep (or whatever your eeprom dump is called), decode it and dump it in a human readable file called u3s-dump.json

The next feature on the list is the encoding itself, which reverses the process described above, allowing you to change the json file by hand with all your desired changes and then have it encoded back to an eeprom file which you can burn directly to your U3S. 

I would appreciate some feedback on how the tool performs, since I did not get a chance to test it on *all* three platforms.

73! Adrian, YO6SSW


On Wed, Apr 4, 2018 at 6:26 PM, Christen Fihl <Christen@...> wrote:
Ken, try use the "Tiny Hexer" from www.mirkes.de
It knows everything about hex files. 

The extra byte is a checksum

Intel Hex Format (also in .epp) is like https://en.wikipedia.org/wiki/Intel_HEX

--
73 Christen Fihl, OZ1AAB




Re: Hans, a request to consider please?

Adrian Scripcă
 

Hi guys,

I spent quite some time laying out the foundation for the program, extracting the domain model, writing the u3s v312 decoder, intel hex decoder, json export, cross-platform build for windows, linux, osx and I believe we're on a good track. Here's a first version for all of you to test since I do not own a U3S. 

Please go to https://hq.scene.ro/u3s-eeprom-tool/ pick the archive corresponding to your computer platform and give the binary a try. The basic syntax is:

u3s-eeprom-tool decode u3s-dump.eep u3s-dump.json

Basically that's asking the tool to load up u3s-dump.eep (or whatever your eeprom dump is called), decode it and dump it in a human readable file called u3s-dump.json

The next feature on the list is the encoding itself, which reverses the process described above, allowing you to change the json file by hand with all your desired changes and then have it encoded back to an eeprom file which you can burn directly to your U3S. 

I would appreciate some feedback on how the tool performs, since I did not get a chance to test it on *all* three platforms.

73! Adrian, YO6SSW


On Wed, Apr 4, 2018 at 6:26 PM, Christen Fihl <Christen@...> wrote:
Ken, try use the "Tiny Hexer" from www.mirkes.de
It knows everything about hex files. 

The extra byte is a checksum

Intel Hex Format (also in .epp) is like https://en.wikipedia.org/wiki/Intel_HEX

--
73 Christen Fihl, OZ1AAB



Re: QCX and peaking BPF

Liam Kingsmill <lumetters1@...>
 

Robert, thank you for the info.  The board here is labeled "3".  The power application problem seems to fit, however.

Liam


On 04/04/2018 08:42 AM, rentwist@... wrote:
Liam,

You need to do the start-up mod if your board rev is 1 or 2 (number on lower right of board).  http://qrp-labs.com/qcx/qcxmods.html#pwrup

BTW, there are a number (4 at least that I recall) recommended mods for any PCB prior to rev 3.

Hope this helps (think it will).

73,

Robert, WA2T


Re: Hans, a request to consider please?

Christen Fihl
 

Ken, try use the "Tiny Hexer" from www.mirkes.de
It knows everything about hex files. 

The extra byte is a checksum

Intel Hex Format (also in .epp) is like https://en.wikipedia.org/wiki/Intel_HEX

--
73 Christen Fihl, OZ1AAB


The WA5DJJ SUPER GRABBER is now on 10M!

David R. Hassall WA5DJJ
 

Dear QRP Labs Members,

I just lit off the 10M grabber receiver last night.  It is operating at 28,125,680Hz to 28,125,920Hz.   I put it there so Technician Class Amateurs can operate QRSS in their Data band and it is just below the WSPR frequencies so the WSPR operators can reach it with a minor change in Frequency.   There might be some minor interruptions in service as I try to Tweak it up a bit now and then.   Hope you can get in there easily.  The grabber can be viewed at http://www.qsl.net/wa5djj/  It now has grabber operations on 160M, 80M, 60M (for UK and EU), 40M, 30M, 20M, 15M, and 10M.   12M is the next receiver block to build.  Hopefully in the next couple of weeks. I still need a lot of QRSS experimenters to try their luck at putting signals of any type on the grabbers.  I try to watch for them but I can’t sit here 24/7.  So you can copy your screenshot on your computer of cell phones.   I am saving all screenshots on a big hard drive for archive purposes.  If I miss seeing your signal, Please drop me an email telling me that you made it.   I am trying to get a handle on just how many are really getting in and on what bands. 

 

For those of you who are LOW FREQUENCY  operators.   Plans are for putting grabber receivers on 2200M (I need to know what frequency to use for QRSS) and 630M (at 477,700Hz to 477,900Hz is the expected frequency).   But those are my expansion plans at the moment. 

 

 

Take care and have fun

 

 

73 Dave Hassall WA5DJJ  Las Cruces, New Mexico

Website: http://www.zianet.com/dhassall/

QRSS SUPER GRABBER WEBSITE: http://www.qsl.net/wa5djj/

 


Re: Hans, a request to consider please?

Hans Summers
 

Hi Ken

No idea, sorry... this must be something specific to the .eep file format. The U3S doesn't involve any checksum. I suggest some Google'ing. Sorry I can't suggest anything else...

73 Hans G0UPL 

On Wed, Apr 4, 2018, 17:06 KEN G4APB via Groups.Io <lfoofui.nbz42=ntlworld.com@groups.io> wrote:
Hi Hans,
Using your .pdf information, I have managed to manually create a full 15 slots WSPR working.eep file without creating it by button pressing on a U3S. I had to manually enter every value on a one -by-one basis into my AVR Extreme burner. Uploading it to my U3S all works fine.

My next stage is to directly create the .eep file from my development programme. However the actual .eep file when viewed in say Notepad, has an extra two digits at the end of every line. I assume this is a checksum created when the file is saved.

Do you have any idea how this value is arrived at please?

73 Ken G4APB


Re: Hans, a request to consider please?

KEN G4APB
 

Hi Hans,
Using your .pdf information, I have managed to manually create a full 15 slots WSPR working.eep file without creating it by button pressing on a U3S. I had to manually enter every value on a one -by-one basis into my AVR Extreme burner. Uploading it to my U3S all works fine.

My next stage is to directly create the .eep file from my development programme. However the actual .eep file when viewed in say Notepad, has an extra two digits at the end of every line. I assume this is a checksum created when the file is saved.

Do you have any idea how this value is arrived at please?

73 Ken G4APB


Re: QCX and peaking BPF

Denis F6GKQ
 

Hi Daniel,

First, you don't tell us which band is your QCX... Please, confirm : 40, 20, other ?

Look at Alan message https://groups.io/g/QRPLabs/message/23136, he gave you valuable informations.

I had the missing peak problem on my QCX 40m. I solved it two ways :
1) putting a 50 ohms (my dummy load but you can take any 47, 51, 56 ohms resistor you have in your junk box) across the antenna input. At this stage, I started getting a peak that I couldn't get with the antenna plug leaved open.
2) I improved the level at the peak by removing 3 turns on my T1 longest winding. Now, the peak is at scale x7 and quite all segments lighted.

It is difficult to tell you where the problem is, you should try to follow the troubleshooting procedure that Hans wrote. Low signal when looking for the BPF peak can be with a problem on the LPF (double check turns number, solder joints, etc.) also on T1 and, then, more difficult to find... on any place else after T1.

Hope you will find...

--
73 from Denis, F6GKQ
QCX 40m nr 3082


Re: QCX and peaking BPF

rentwist@...
 

Liam,

You need to do the start-up mod if your board rev is 1 or 2 (number on lower right of board).  http://qrp-labs.com/qcx/qcxmods.html#pwrup

BTW, there are a number (4 at least that I recall) recommended mods for any PCB prior to rev 3.

Hope this helps (think it will).

73,

Robert, WA2T


Re: No Transmit QCX

Alan de G1FXB
 

And just the right time of year for an 'Easter Egg'
I wonder if Han's ever wrote any software for Atari?

Good luck !

Alan

On 04/04/2018 13:47, James Daldry W4JED wrote:
On Wed, 4 Apr 2018 11:37:35 +0100
"Alan de G1FXB via Groups.Io" <g1fxb@...> wrote:

James W4JED,

    if it's not too late, before you discover it the hard way...
The kit designer has implemented a gotcha to discourage unauthorised
copies of the QCX being built.
Burning a non genuine QRP-Labs supplied ATmega IC will not result in
a functioning QCX,
(I believe it's being reported elsewhere it displays something to the
effect 'none genuine'?)

https://groups.io/g/QRPLabs/message/17805

You should be OK to reflash the original IC.


You may wish to review the Mods / Trouble shooting pages, to see if
yours is a result of incomplete MCU boot / reset
Also separate comment specifically in the*Buttons / rotary encoder
don't work properly* section, highlighting need to check / modify if
necessary if yours is a Ver 1/2 PCB.

https://www.qrp-labs.com/qcx/qcxtrouble.html#digital

Looking over the past posts when used before a factory reset, it has
being reported to 'fix' some side tone / no alignment signal
'funnies' where the MCU saved data becomes corrupt,
Sometimes it goes beyond repair?
It may fix your keying signal working in one function and not
another, may be not?
It won't cost anything to check.

Alan

On 02/04/2018 14:41, James Daldry W4JED wrote:
On Sun, 01 Apr 2018 18:15:54 -0700
"Jim Carlson"<tshotshoto@...> wrote:

Hi Jack,

I'd be happy to look at your QCX with the commitment on your part
that no money changes hands!  I'm just happy to help.  I have built
one QCX but it worked the first time so I don't have experience
trouble shooting but I am a retired electronics engineer (from
Motorola) so I have a lot of experience.  I have the proper test
equipment for this task.  Let me know if you would like to send it
to me.  My contact information is correct on qrz.com.

73,
Jim W7EED
Hi, Jim

For about 10 years at my last job (1988 - 2010) I repaired VCR's and
camcorders almost exclusively - maybe 40 a week. Yes, most of these
were mechanical problems - belts, etc - but a fair number were logic
problems. Most of these, in turn, were things like bad pickup coils,
bad hall effect devices, bad optocouplers, etc, but a significant
fraction were microcontroller problems. VCR's have anywhere from no
micro's (Panasonic NV-8170, with 2 large boards full of CMOS), to 6
or 7, depending on how servo systems were designed. Some micro's had
blown cmos capacitors on input pins (circuit is loaded down by the
input pin, and can be made to work by adding a current amplifier),
weak output "totem poles", etc, but occasionally you would have bad
firmware like a whole family of Matsushita 1985 decks that would
burn the front load assembly motor because there was no timeout on
the basket motor drive. The replacement was MN15846VRG3, which
replaced one without the 3. We kept 2 of that one in stock.

In this case I have a key_out line that is not responding to the
NOT_dit signal, but does respond to the keyer code practice
function. So the output pin is good. When you disable the key_out
by pulling the pin out of the socket, the s-meter goes full-scale
on key presses. The dit pin is functioning. The only thing between
them is the micro and its program. So - I've downloaded the hex
file and will be firing up avrdude to burn it to one of my own
'328's. I have a current-limitted supply so I won't be letting the
magic smoke out. Thanks for volunteering, but I think I have this
handled.

73

Jim Daldry W4JED


Hi, Guys

The bogus chip message is "Use original IC!". Ask me how I know.
Anyway, since the original is burned to use a crystal oscillator it
won't work off-board, so I spent yesterday evening wiring up an
in-circuit programming cable, tracing the wires from the socket pins on
the usbasp to the pins on the socket. Sometime today I'll be trying it
out. Here's hoping!

Jim


Re: No Transmit QCX

James Daldry W4JED
 

On Wed, 4 Apr 2018 11:37:35 +0100
"Alan de G1FXB via Groups.Io" <g1fxb@...> wrote:

James W4JED,

    if it's not too late, before you discover it the hard way...
The kit designer has implemented a gotcha to discourage unauthorised
copies of the QCX being built.
Burning a non genuine QRP-Labs supplied ATmega IC will not result in
a functioning QCX,
(I believe it's being reported elsewhere it displays something to the
effect 'none genuine'?)

https://groups.io/g/QRPLabs/message/17805

You should be OK to reflash the original IC.


You may wish to review the Mods / Trouble shooting pages, to see if
yours is a result of incomplete MCU boot / reset
Also separate comment specifically in the*Buttons / rotary encoder
don't work properly* section, highlighting need to check / modify if
necessary if yours is a Ver 1/2 PCB.

https://www.qrp-labs.com/qcx/qcxtrouble.html#digital

Looking over the past posts when used before a factory reset, it has
being reported to 'fix' some side tone / no alignment signal
'funnies' where the MCU saved data becomes corrupt,
Sometimes it goes beyond repair?
It may fix your keying signal working in one function and not
another, may be not?
It won't cost anything to check.

Alan

On 02/04/2018 14:41, James Daldry W4JED wrote:
On Sun, 01 Apr 2018 18:15:54 -0700
"Jim Carlson"<tshotshoto@...> wrote:

Hi Jack,

I'd be happy to look at your QCX with the commitment on your part
that no money changes hands!  I'm just happy to help.  I have built
one QCX but it worked the first time so I don't have experience
trouble shooting but I am a retired electronics engineer (from
Motorola) so I have a lot of experience.  I have the proper test
equipment for this task.  Let me know if you would like to send it
to me.  My contact information is correct on qrz.com.

73,
Jim W7EED
Hi, Jim

For about 10 years at my last job (1988 - 2010) I repaired VCR's and
camcorders almost exclusively - maybe 40 a week. Yes, most of these
were mechanical problems - belts, etc - but a fair number were logic
problems. Most of these, in turn, were things like bad pickup coils,
bad hall effect devices, bad optocouplers, etc, but a significant
fraction were microcontroller problems. VCR's have anywhere from no
micro's (Panasonic NV-8170, with 2 large boards full of CMOS), to 6
or 7, depending on how servo systems were designed. Some micro's had
blown cmos capacitors on input pins (circuit is loaded down by the
input pin, and can be made to work by adding a current amplifier),
weak output "totem poles", etc, but occasionally you would have bad
firmware like a whole family of Matsushita 1985 decks that would
burn the front load assembly motor because there was no timeout on
the basket motor drive. The replacement was MN15846VRG3, which
replaced one without the 3. We kept 2 of that one in stock.

In this case I have a key_out line that is not responding to the
NOT_dit signal, but does respond to the keyer code practice
function. So the output pin is good. When you disable the key_out
by pulling the pin out of the socket, the s-meter goes full-scale
on key presses. The dit pin is functioning. The only thing between
them is the micro and its program. So - I've downloaded the hex
file and will be firing up avrdude to burn it to one of my own
'328's. I have a current-limitted supply so I won't be letting the
magic smoke out. Thanks for volunteering, but I think I have this
handled.

73

Jim Daldry W4JED


Hi, Guys

The bogus chip message is "Use original IC!". Ask me how I know.
Anyway, since the original is burned to use a crystal oscillator it
won't work off-board, so I spent yesterday evening wiring up an
in-circuit programming cable, tracing the wires from the socket pins on
the usbasp to the pins on the socket. Sometime today I'll be trying it
out. Here's hoping!

Jim


Re: QCX and peaking BPF

Alan de G1FXB
 

Anybody effected,
see if this helps?

https://groups.io/g/QRPLabs/message/22418

I suspect Han's has being sidetracked to have rewritten that section into the build manuals so far.
(Listen to any subsequent advice provided.)

Either now by default, or if experiencing difficulty in obtaining a good peak. Utilise a 50 Ohm termination to the Antenna input and retry?
Expect the peak value to be lower than being unterminated, but it should peak?

Examples of expected signal amplitudes are given on the trouble shooting web page.
Other things to suspect are:-
Bare in mind the warning in the build manual, C1 Trimmer polythene dielectric is easily damaged by excess heat during assembly.
The build manual describes you may observe more than one increase in the BPF response, but only one should have true peak.
One QCX 20 builder had Low BPF peak / sensitivity & Low TX power out and found the common cause was an excessive loss through the shared LPF section.
Incorrect  insertion / damaged / defective components away from the the BPF, can also give rise to low peak values, as proven by other builds documented.

Alan


On 03/04/2018 01:26, Steve via Groups.Io wrote:
Just to be clear, you want to disconnect the dummy load or antenna during alignment. Otherwise the peak BPF reading will be low. 

 

Steve N4IAG



Re: QCX and peaking BPF

lajes67
 

I had problems with my second kit, I couldn.t make any adjustment on the last 2 adjustment steps, turns out R27 was defective, when I plugged in the headphones and turned R27 I either had tone or didn't, checking R27 with a DVM I saw the resistance start out at 1 ohm and then the resistance would jump to 100 ohms and the higher, there was no gradual increase, I was lucky that I already had a working QCX and I was able to verify on that R27 as to what the problem was, as soon as I changed R27 I was able to proceed with the adjustments, hope this helps.

73 John K2IZ


Re: No Transmit QCX

Alan de G1FXB
 


James W4JED,

    if it's not too late, before you discover it the hard way...
The kit designer has implemented a gotcha to discourage unauthorised copies of the QCX being built.
Burning a non genuine QRP-Labs supplied ATmega IC will not result in a functioning QCX,
(I believe it's being reported elsewhere it displays something to the effect 'none genuine'?)

https://groups.io/g/QRPLabs/message/17805

You should be OK to reflash the original IC.


You may wish to review the Mods / Trouble shooting pages, to see if yours is a result of incomplete MCU boot / reset
Also separate comment specifically in the Buttons / rotary encoder don't work properly section, highlighting need to check / modify if necessary if yours is a Ver 1/2 PCB.

https://www.qrp-labs.com/qcx/qcxtrouble.html#digital

Looking over the past posts when used before a factory reset, it has being reported to 'fix' some side tone / no alignment signal 'funnies' where the MCU saved data becomes corrupt,
Sometimes it goes beyond repair?
It may fix your keying signal working in one function and not another, may be not?
It won't cost anything to check.

Alan

On 02/04/2018 14:41, James Daldry W4JED wrote:
On Sun, 01 Apr 2018 18:15:54 -0700
"Jim Carlson" <tshotshoto@...> wrote:

Hi Jack,

I'd be happy to look at your QCX with the commitment on your part
that no money changes hands!  I'm just happy to help.  I have built
one QCX but it worked the first time so I don't have experience
trouble shooting but I am a retired electronics engineer (from
Motorola) so I have a lot of experience.  I have the proper test
equipment for this task.  Let me know if you would like to send it to
me.  My contact information is correct on qrz.com.

73,
Jim W7EED
Hi, Jim

For about 10 years at my last job (1988 - 2010) I repaired VCR's and
camcorders almost exclusively - maybe 40 a week. Yes, most of these
were mechanical problems - belts, etc - but a fair number were logic
problems. Most of these, in turn, were things like bad pickup coils,
bad hall effect devices, bad optocouplers, etc, but a significant
fraction were microcontroller problems. VCR's have anywhere from no
micro's (Panasonic NV-8170, with 2 large boards full of CMOS), to 6 or
7, depending on how servo systems were designed. Some micro's had
blown cmos capacitors on input pins (circuit is loaded down by the
input pin, and can be made to work by adding a current amplifier), weak
output "totem poles", etc, but occasionally you would have bad firmware
like a whole family of Matsushita 1985 decks that would burn the front
load assembly motor because there was no timeout on the basket motor
drive. The replacement was MN15846VRG3, which replaced one without the
3. We kept 2 of that one in stock. 

In this case I have a key_out line that is not responding to the
NOT_dit signal, but does respond to the keyer code practice function.
So the output pin is good. When you disable the key_out by pulling the
pin out of the socket, the s-meter goes full-scale on key presses. The
dit pin is functioning. The only thing between them is the micro and
its program. So - I've downloaded the hex file and will be firing up
avrdude to burn it to one of my own '328's. I have a current-limitted
supply so I won't be letting the magic smoke out. Thanks for
volunteering, but I think I have this handled.

73

Jim Daldry W4JED





Re: #u3s #synth 27MHz Crystal on Si5351 module failure? U3S just showing boxes... #u3s #synth

Al Holt
 

Thanks Hans for clearing up the module's behavior when 'out of circuit.' As I alluded to in the other thread I mistakenly created, the module is currently working and my U3S has been running overnight transmitting WSPR and QRSS on 40 meters. The repair probably boiled down to inspecting it with a 'fine-toothed comb' as well as reheating connections and connectors. Probing the Si5351A chip is a challenge and I found a small sewing needle to be a great help.

I used a 'proto' type of breadboard to mount and power the Si5351A module to make it easier to troubleshoot away from the U3S. Not that I could get a lot of testing done with it, but it's got me thinking about doing some experimenting with the I2C bus structure. Maybe an Arduino sketch to simulate some commands...or just build some jumper header extenders.

But, away from the 'mother ship' the little module stood up pretty well; "took a licking and kept on ticking" as John Cameron Swayze used to say about Timex watches.

Thanks again!

--Al


Re: #u3s #synth 27MHz Crystal on Si5351 module failure? U3S just showing boxes... #u3s #synth

Hans Summers
 

All correct, Daniel

FYI the standard Si5351A-B-GTR does nothing on power-up, no clock outputs. It requires programming via I2C to make it do anything.

Custom versions are possible, which have default power-up configurations programmed in. I imagine you have to make a huge order to interest SiLabs in making a custom version! 

73 Hans G0UPL 

On Tue, Apr 3, 2018, 23:45 Daniel Ekman SA2KNG <knegge@...> wrote:
If I'm not mistaken, the lcd display is initialized before the mcu even speaks to the synth over i2c. So the two rows should disappear (and probably display text) before the i2c synth stuff begins. So the 27MHz crystal is irrelevant during this phase. The mcu has it's own 20MHz crystal to run, so it does not need anything from the synth, as is clear when you power up the board without the synth.
Search on the synth board for the problem first. I suspect there's something wrong with the level shifters (Q1,Q2) or the i2c pins (4,5) on the Si-chip (measure at R3,R4). They should both idle at 3.3V at the chip side and 5V at the pinheader to the QCU board.
I'm not so familiar with the Si-chip as to know what it does when it's powered up without a controller talking to it, perhaps in the datasheet. Still this does not help too much if the problem lies in the i2c pins and level shifters.


Re: #u3s #synth 27MHz Crystal on Si5351 module failure? U3S just showing boxes... (psst....It's working again!) #u3s #synth

Alan G4ZFQ
 

sorry, I hate it when it starts a new topic!
Al,

The "Subject" line is the topic.
Add to it, or change it produces a new topic.
(Unless there is a way to add something without changing the topic?)

73 Alan G4ZFQ


QCX 60m Tuning #qcx

 

I was about to ask about whether the tuning for the 60m QCX was channelized, as I couldn't find anything in the group message archives.
Then I thought to look at the Assembly manual. It indicates that tuning on the 60m version of the QCX is from 4.63 Mhz to 5.91 Mhz.
Since i had some difficulty finding this information, I thought that I would reiterate it for the benefit of anyone else wondering the same thing. 

This range encompasses the "5 channels" we have here in North America and also the "new" WRC-15 allocation from 5351.5 Mhz to 5366.5 Mhz,
which we hope to have access to at some point in the not too distant future.  In fact this tuning range is wide enough that I think everyone's 60m allocation
should be somewhere within this range. 

Recently I have noticed an increased use of 60m CW here in North America for SOTA and my experience is that this band is still quite under-utilized.
It works very well for daytime contacts within a 500 mile radius, making it well suited for SOTA use. 

It seems that the QCX would be a perfect 60m addition to my SOTA setup ! 

Cheers 

Michael VE3WMB / VA2NB 


Re: QCX and peaking BPF

Daniel Urbach
 

No one else has had low readings on the bpd peaking step? ...begining to make me think I have something seriously wrong.


Re: #u3s #synth 27MHz Crystal on Si5351 module failure? U3S just showing boxes... (psst....It's working again!) #u3s #synth

Al Holt
 

sorry, I hate it when it starts a new topic!