Re: #qcxmini BPF Alignment Issues
#qcxmini
No offense taken at all! I'll resolder the leg between C5 & C8.
?
I agree, from the front side it looks like an incomplete solder joint. From the back side it appears normal. I'm REALLY hoping this is it, I'm getting kind of discouraged after a few days of no progress in tracking down my mistake. I was very close to ordering a new board yesterday and starting over now that I have a little more experience.?
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
Hello Hans,
?
here are some new data I've got when analysing the USB data stream.
I started QMX and PuTTY and the collected data are starting the moment when hitting ENTER.
Each line is one packet (transmission).
?
FW 003
PC->QMX? BULK out "0d"
QMX->PC? BULK in "1b 5b 32 4a"
PC->QMX? BULK in (Response in)
QMX->PC? BULK out (Request in)
QMX->PC? BULK in "1b 5b 48 1b 5b 3f 32 35 6c"
PC->QMX? BULK in (Response in)
QMX->PC? BULK in (1b 5b 33 33 6d 1b 5b 32 34 3b ...) (the menu text)
?
FW 006
PC->QMX? BULK out "0d"
QMX->PC? BULK out (Request in)
QMX->PC? BULK in "1b 5b 32 4a"
?? nothing more
When hitting a character in PuTTY it's send from the PC -> QMX and the transmission is confirmed by the QMX. So the canal is not dead.
?
It looks like the second block (QMX->PC BULK out) is at the wrong place.
?
73 Ludwig
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
Thanks Moritz
I found one more single byte error in the 440-byte Compound USB descriptor. Amazing how Linux manages to sort everything out and work fine anyway, despite the errors.?
I've fixed that but I'm now going through the entire 440 byte descriptor and checking everything for each of the three modes (1, 2, 3 serial ports). Then I'll try booting in Win 10 and check it there. If that all works I'll publish a 1_01_007 that will hopefully resolve everything in all cases (hopefully also Win 7 but I can't check that so will wait for news from Ludwig on that).
73 Hans G0UPL
Hi,
?
the Problem with the USB Serial Ports = 3 persists on Windows 11.
While using am using WSL (Ubuntu Linux) and forwarding the USB ports to the WSL i got some more debugging output, that might help to track the issue further down:
Relevant dmesg output attaching the QMX with USB Serial Ports = 3:?
[ ?113.234442] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(3)
[ ?113.234452] vhci_hcd vhci_hcd.0: devid(524289) speed(2) speed_str(full-speed)
[ ?113.234542] vhci_hcd vhci_hcd.0: Device attached
[ ?113.517512] vhci_hcd: vhci_device speed not set
[ ?113.587627] usb 1-1: new full-speed USB device number 2 using vhci_hcd
[ ?113.667834] vhci_hcd: vhci_device speed not set
[ ?113.737950] usb 1-1: SetAddress Request (2) to port 0
[ ?113.776708] usb 1-1: config 1 contains an unexpected descriptor of type 0x2, skipping
[ ?113.776729] usb 1-1: config 1 interface 9 altsetting 0 has a duplicate endpoint with address 0x85, skipping
[ ?113.780855] usb 1-1: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00
[ ?113.780865] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ ?113.780870] usb 1-1: Product: QMX Transceiver
[ ?113.780873] usb 1-1: Manufacturer: QRP Labs
[ ?113.924261] vhci_hcd: connection closed
[ ?113.924577] vhci_hcd: stop threads
[ ?113.924584] vhci_hcd: release socket
[ ?113.924590] vhci_hcd: disconnect device
[ ?118.801330] usb 1-1: can't set config #1, error -110
[ ?118.851634] usb 1-1: USB disconnect, device number 2
?
In the Windows error log, there is also mentioned an error identifying a device according to an address issue.
?
I can confirm (as before), the other USB Serial Port Settings (1 and 2) do work.
?
73 de Moritz KO6DZX
?
|
#qmx New build, incomplete initialization problem?
#qmx
Good day. My QMX+ V3 seems to be stuck in firmware update. By providing a new firmware file it will try to initialize, and after a few minutes gets stuck on Band Version. Stays there for a minute or so, then reverts to the clock. After that, I can get to screens with garbage. I can sometimes get to the Menus and beyond, in and out to non-sense screens. Both push buttons seem to work, because I can easily navigate in the menu, until the system gets stuck on a choice, then it goes back to the clock. ith a right button push, I can go back to garbage screens and sometimes into the menu system. From some of the screens, a quick push on the top decoder will result in a shut-down and a new firmware update state.
I conclude it is not fully initializing, for reasons unknown. I have tried a "Factory Reset" many times, and that seems to get stuck, too.
Ideas? Thank you in advance!
|
Re: #qcxmini BPF Alignment Issues
#qcxmini
Hi Scott
From your enclosed pictures I still don't like the look of the joint between the C5 and C8 legends. In the pic it has a dark ring around the wire, which the others don't have, suggesting that the solder has not wicked-up around the wire.
My apologies for calling your competence into question but I thought a recheck and resolder here would be a whole lot easier than doing the whole of T1 again.
Keith, G0GNL
|
CW not working ? Just a stupid question. did you change back from Digi to CW ? Bonne chance
--
Martin
DK3UW
|
Many thanks Stan for all this infos.
With your parameters i have now tx in rtty. In cw its not working. I will see with my friends in the radioclub the next week for continue this configuration.
After this, i will give here other infos.
Andre F6APU.
|
#qmx SSB Firmware beta 1_01_006 release - calibration
#qmx
Hans, I think calibration in _006 is better, but there are still some issues.
I am attaching some screenshots from my QMX-lowband calibration that may help in diagnosing the phase-error cals that don't finish, and also a USB IMD optimization that was strange, and fixed itself when I repeated it.
?
I did the initial calibration from a factory-reset condition, using the 'R' option to do all of the optimizations, which I then reviewed.
The 80m Phase Error plot didn't complete - it stopped at about 700 on the x-axis.? And retrying it with the 'O' repeated the same results.
Then I retried a few more times and captured the attached 5 shots of the progression.? Note that it for some reason started with a high DAC value, not the one corresponding to the x-axis, which is why it stopped early.? Completely repeatable.
?
The 20m USB IMD optimization looked crazy.? The other IMDs looked OK.? So I retried 20m using the 'O', and it cleaned itself up.? See the initial and retry results in the last two attachments.
?
I hope this is helpful- I will check the cal process/results on my other QMX*, and let you know if anything else interesting shows up.
Stan KC7XE
?
?
|
Re: QMX: Is the latest firmware correcting the distorted audio?
Thank you Stan,
?
I just loaded .006 and ran the calibration. This is on my QMX 20-10. I need to re-read the diagnostics page to get more familiar what I¡¯m looking at. Overall everything looks better during calibration compared to earlier releases. 20 is still crazy like a lot of people are seeing.
I have tried the PrePhase setting without success. However, since .006 I¡¯m able to get intelligible audio and it sounds pretty good but I have a constant whistle. I can eliminate it by turning the mic gain way down into the 40s but then the audio starts to sound distorted again. I¡¯m also running the EQ. It doesn¡¯t make a difference if it¡¯s on or off. The whistle is still there. The mic gain is currently set to 59. Compression is set to 4. The whistle is on all bands. I don¡¯t hear this on my 80-20 QMX.?
I don¡¯t have the best test bench here. I¡¯m using an ic 705 with the antenna disconnected and the the RF gain set to 1. The QMX is connected to an EFHW for 40 meters.?
Don.
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
Hi,
?
the Problem with the USB Serial Ports = 3 persists on Windows 11.
While using am using WSL (Ubuntu Linux) and forwarding the USB ports to the WSL i got some more debugging output, that might help to track the issue further down:
Relevant dmesg output attaching the QMX with USB Serial Ports = 3:?
[ ?113.234442] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(3)
[ ?113.234452] vhci_hcd vhci_hcd.0: devid(524289) speed(2) speed_str(full-speed)
[ ?113.234542] vhci_hcd vhci_hcd.0: Device attached
[ ?113.517512] vhci_hcd: vhci_device speed not set
[ ?113.587627] usb 1-1: new full-speed USB device number 2 using vhci_hcd
[ ?113.667834] vhci_hcd: vhci_device speed not set
[ ?113.737950] usb 1-1: SetAddress Request (2) to port 0
[ ?113.776708] usb 1-1: config 1 contains an unexpected descriptor of type 0x2, skipping
[ ?113.776729] usb 1-1: config 1 interface 9 altsetting 0 has a duplicate endpoint with address 0x85, skipping
[ ?113.780855] usb 1-1: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00
[ ?113.780865] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ ?113.780870] usb 1-1: Product: QMX Transceiver
[ ?113.780873] usb 1-1: Manufacturer: QRP Labs
[ ?113.924261] vhci_hcd: connection closed
[ ?113.924577] vhci_hcd: stop threads
[ ?113.924584] vhci_hcd: release socket
[ ?113.924590] vhci_hcd: disconnect device
[ ?118.801330] usb 1-1: can't set config #1, error -110
[ ?118.851634] usb 1-1: USB disconnect, device number 2
?
In the Windows error log, there is also mentioned an error identifying a device according to an address issue.
?
I can confirm (as before), the other USB Serial Port Settings (1 and 2) do work.
?
73 de Moritz KO6DZX
?
|
Re: FT8CN Getting it to Work!
Thanks for your experiences with this. I've had thoughts of trying out something with no laptop, or making an all-in-one digital mode device, but FT8CN, as well as the zBitx/sbitx interfaces....well, they seem to me to be worth it to lug the laptop along, for me!
?
-Nate?
N8BTR
|
Mostly CW here too, but I did a couple of Qs on SSB. Local, but I got good signal and audio reports on 10m.?
--
73, Dan? NM3A
|
Re: QMX: Is the latest firmware correcting the distorted audio?
Don,
On the QMX that has distorted audio, please turn off the 'phase predistortion' option in the SSB menu, and see if that corrects the distorted audio.? If it does, please look at the calibration phase error plots for each band, and see if any of them are incomplete, i.e. they don't go all the way on the x axis to ~2000 (9V build) or 2600 (12V build), and see if that is the band where you heard distorted audio.? This data may be helpful in understanding what is happening.
?
v006 does have further changes to the calibration, so you may want to try to load _006 and re-do calibration, at least on any bands with incomplete plots.? But in general, I don't think you have to do a factory reset or update calibration when loading any of these new versions.
Stan KC7XE
|
8xAA battery pack, nice. I have just build one and plan on using it soon.
|
QMX: Is the latest firmware correcting the distorted audio?
All,?
Ive loaded.004 and it seems to work well on my QMX 80-20. I¡¯ve made a number of successful contacts on ssb. On my QMX 20-10 it has distorted audio after the update. I did a factory reset then calibrated. It was after this that the transmit audio is very distorted. I went back and changed the settings to the last known working numbers but it¡¯s still distorted.
Can anyone tell me if the new .006 has helped this? I¡¯m about to load it in both QMXs and the QMX+ and was wondering if it has helped?
Does a firmware update require a factory reset and calibration or leave it be?
?
Thanks..
?
Don N6NLX
|
|
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
FW006 Win 11 WSJTX/FLrig working for over an hour now using 2 com ports! (Putty cat mon). No joy on 3 com ports! setting!
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
No offense to Tony, but I would advise against re-assigning "In Use" port numbers.
I've gotten my Windows machine into a world of USB pain doing that. Unless you know with absolute certainty that the device that owned that port number (if you even know what device it was) will never ever be plugged in again.
I had to go into device manager, View, Show Hidden Devices and then delete all grayed out COM ports under Ports (COM & LPT) and all greyed out entries under Universal Serial Bus Controllers.?
--
Randy, N4OPI
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
Same result as before. That is why I dumped values for Hans, so he can see what Win 11 is recognizing it as. There must be some difference between Win 10 and Win 11 - his test system is Win 10.
?
Erik - AD7OV
|
Ok, weirdness prevails..
Q102 and D109 did fix the initial problem and it is up and running. Mostly
When I was troubleshooting why I wasn't getting 3.3v, I pressed the scope probe onto the drain of Q110 and it magically came to life. Mostly
VCC is 4.96
VDD is 3.3
The linear regulator has turned off and varying the input voltage makes the PWM duty cycles change. :-)
And VCC - VDD stay right where they belong.
But! The ADC_3V3 signal measures 1.24v and the diagnostics page shows that VDD is 2.54. Which it is not. It is 3.3.
I re-measured R110 and R112 and still both measure in the vicinity of 22k depending on how long I let the meter charge up C106. 24k this time around. And just to be sure I measured across both of them and I get 48k. So they seem to be ok.
--
Randy, N4OPI
|
Grant
Richard Dyer