Keyboard Shortcuts
Likes
- QRPLabs
- Messages
Search
|
Re: QCX-mini Adjustment and Alignment Issues: Excessively Sensitive Gain and Inability to Adjust IQ, Low and High -THANK YOU ALL!
Hi everyone, ? Tim VE1XR Tim VE1XR |
|
Re: QDX New build zero RF output
#qdx
Make sure your computer audio levels are at 100% and the power slider in WSJT-X is all the way up.
-- 73, Dan - W2DLC |
|
Re: QDX Power Increase?
Guys - adjusting the turns on L3 and L4 made a difference. Prior to that on 20 meters I used to need 10.5v to get 3.7 watts out. Squeezing L4 turns together a tad and lowering the input voltage to 9.5 I now get 4.6 watts out at 500ma current. Pretty much the same on 30 meters, just a bit less output. On 40 meters at that voltage I get 4.4 watts out, so that's fine.
However, 80 meters is an issue. In order to keep the output voltage at about 42-43 volts I need to lower my supply voltage down to 8 volts. L2 can't have its turns spread out much more, as it's already pretty cramped. I'm thinking I might just pull two turns off of it and see what happens. Worst case is that I'll have to squeeze them together a bit to get enough inductance with two turns gone. Time to heat up the soldering pencil... BTW - VE3EGA: I live in a very HOA/CC&R restricted neighborhood. NO outside antennas are allowed. However they can't exclude flag poles so that's what I'm using - a 30 foot tall Zerofive Heavy Duty flag pole, with 10 various length radials. Unfortunately I don't have the luxury of a tower or ever several wire antennas. Out here in the west part of Idaho I seldom even hear EU stations on FT8 and when I do, they're usually at -12 or worse. I've found that the -12 mark is about the limit on who I can work. So in my case the difference between 3 watts and 4 watts might be enough to mean logging the DX or not. This morning on 40 meters with the QDX at 4.4 watts into the flagpole I worked FK8HM in New Caledonia - that was a pleasant surprise. Went up to 30 meters and logged two stations in Indonesia. Makes a big difference when the path to the DX is nearly all over water. :-) :-) -- Jim / K7TXA Eagle, ID SKCC 10447 BUG 301 |
|
Re: QDX New build zero RF output
#qdx
On 09/02/2023 15:13, Mike Easterbrook wrote:
RX is good.? TX has zero RF out on all bands.Mike, At high magnification there are indications of damageAre you sure? It seems unlikely that the RX would work, IC11 is the frequency generator. I suspect brief transmission into open circuit as cause. BS170 show noobvious damage. TX into nothing is reputed to have blown many BS170s, but very few, almost no 5351s. Check voltages on the BS170s when TX into dummy load. 73 Alan G4ZFQ |
|
QDX New build zero RF output
#qdx
Hi All
m QDX? High Band Rev 5? board, Firmware 1.07.? Wound for 9V, supply at 7.5V This is my 3rd QDX and 1st high band version.? RX is good.? TX has zero RF out on all bands.? Status LED suggests TX is working when selected by "Tune", "Enable TX" or "Teminal Emulator", suggesting audio levels are OK.? Current draw increases a bit as expected (Standby/RX 150 mA, TX 240mA.? Out of enclosure, no sign of magic smoke but getting hot in region of TXCO.? At high magnification there are indications of damage to IC11, MS5351M (tiny puncture wound & small fluid leak) Assuming IC11 has failed and needs replacing, can I expect and be prepared for other component failures? I suspect brief transmission into open circuit as cause. BS170 show no obvious damage. Anyone any experience sourcing MS5351M?? I can only see it direct from manufacturer in China.? I do still have one or two of the old Si chips somewhere at my other shack (along with a load of BS170 which I got before Farnell were surcharging small orders). I thought Hans did mention that the MS chip had slightly better performance at cost of small increase in current draw.? Unsure whether to try to buy now and get the job done or wait a month til I'm back in the other location and can use the Si chip. I had been hoping to take advantage of the recent good conditions on the higher bands from here.? Testing my patieince and commonsense! Any thoughts/guidance welcome.? Thanks. 73 Mike |
|
Re: QDX Power Increase?
ve3ega
JIm,
A 9V build running at 11V - not good! Try pinching/ moving the turns on the BPF's - I and others have used this method to optimise output. Elsewhere I believe it is stated 3.5 - 4W is where you should be with QDX - 5W is practically impossible and expect smoke! Dont despair, 3.0W will work most of EU on 20m - what's your Ant? - I use a OCFD, 41ft and 25ft with a 4:1 unun at 23ft 73 |
|
Re: #QDX Hamlib Error
#qdx
ve3ega
Greg,
I cant edit my post but perhaps tell us what else you have connected to the HUB and maybe remove one device at a time as it may be be demanding exclusive use? Of course with the USBC connection my original reply will assume you have a dongle/adaptor to try without using the HUB? 73 |
|
Re: #QDX Hamlib Error
#qdx
ve3ega
Greg,
Greg, I missed this at first when I was reading your post : NOV8 TECH? 13 device HUB <--- probably the issue! Try WITHOUT the HUB and then maybe install this Virtual Com-Port driver: Generally, if I have had any issues with PC not seeing any Ports for QDX I have used the 'Silabs USB-UART Drivers', See Below - which always fixes missing COM Port issues for me, and it should not harm anything else because it just creates Virtual Com Ports, which different applications can make use of as needed! ? - Use this Driver - d/l : (Disclaimer: As always, in these try-this fix-it-situations - It's 'Your PC/Your Risk' -? these scenarios are suggestions and not instructions! Hi)Hope this helps? 73 Terry |
|
Re: #QDX Hamlib Error
#qdx
On 09/02/2023 10:16, Greg - Gmail wrote:
I have also tried Omnirig with no success either.? It fails to open the port.Greg, If one software will not open the port then no software will open this port. What does Device Manager say about it? Presumably Windows has installed the driver? Have you checked the power saving settings? I do not know about how USB3 may handle the dual-purpose QDX or, if your hub is compatible with a dual purpose USB device. You do know that with Windows the QDX does not work like a normal USB device? It requires a power cycle each time you plug it in. 73 Alan G4ZFQ |
|
Re: #QDX Hamlib Error
#qdx
Hi Alan, JIm and John
I realised that I did not say I was running Windows 10 in my original post. I have tried several COM port numbers with no success. I have also tried connecting directly to the Laptop via its own USB port.? There is only one.? No luck there either. I will try FLRig tomorrow and see if I have any success with it. I have also tried Omnirig with no success either.? It fails to open the port. Thanks for your help so far.? I will let you know how I get on. Greg VK4GRM |
|
Re: #QDX Hamlib Error
#qdx
On 09/02/2023 05:31, Greg - Gmail wrote:
The problem on the laptop seems to be that when a first attempt is made to open the COM port using WSJT-X (latest version installed) that the port gets locked up or is maybe blocked in some fashion.? Any further attempts just get rejected and I get the following error message:Greg, If the COM port is blocked for some reason Hamlib will not work and give the error messages. Does the terminal work on this laptop? If not then all I can suggest is trying various combinations with the USB connection. Have you tried changing the COM port number? 73 Alan G4ZFQ |
|
Re: #QDX Hamlib Error
#qdx
¿ªÔÆÌåÓýYet another hamlib struggle.My suggestion is to load up FLRig and tell FLRig you are running a Kenwood TS480. ?Then tell ?WSJIT that your transceiver is ¡°FLRig¡±. ?Think of FLRig as a HAL (hardware abstraction layer) that is *way* ?better at understanding how to talk to rig hardware
than Hamlib.
Also if you are OK with compiling your own FLRig from source the latest (test) bits include native support for the QDX . ?So you can tell FLRig that you are running a QDX not a Kenwood TS480.
I had nothing but trouble with hamlib and was very very happy to ¡°just say no¡± to it . ?FLRig rocks : its ?well documented, well supported and frequently updated to add support for new rigs (e.g the QDX will soon be supported in release builds). ? Hamlib
on the other hand is frequently the subject of emails such as yours :-(
|
|
#QDX Hamlib Error
#qdx
Hi
I have been struggling with this for a few days without success and was wondering if someone can provide some guidance.? I have had a good troll around the previous posts but have not found any that give me a clue to what the problem is. I am trying to use the QDX on a laptop for portable use.? I have had it working on a desktop so am reasonably happy that the QDX is working correctly though it took a few attempts to get it operational on the desktop.? Mostly changing the USB ports that it was connecting to.? I was able to upgrade the QDX firmware to the latest version and also use PuTTY to look at all the new screens that Hans has added in the latest version of the firmware. I am using an ASUS ZenBook14 with a NOV8 TECH? 13 device HUB.? The QDX is connected to one of the USB3 ports on the hub which has a USBC connection to the ZenBook. The problem on the laptop seems to be that when a first attempt is made to open the COM port using WSJT-X (latest version installed) that the port gets locked up or is maybe blocked in some fashion.? Any further attempts just get rejected and I get the following error message: Hamlib error: 1:rig.c(1409):rig_close returning(-1) Invalid parameter ? 1:rig.c(817):rig_open entered rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\WSJT\wsjtx rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist rig_open: async_data_enable=0, async_data_supported=0 serial_open: COM5 serial_open(229): open failed#1 serial_open(229): open failed#2 serial_open(229): open failed#3 serial_open(229): open failed#4 serial_open: Unable to open COM5 - No such file or directory port_open: serial_open(COM5) status=-6, err=No such file or directory rig_open: rs->comm_state==0?=0 1:rig.c(1023):rig_open returning(-6) IO error ? IO error IO error while opening connection to rig ? Timestamp: 2023-02-09T05:03:40.626Z In Device Manager I have made visible all of the hidden COM Ports and deleted all of these and then switched on the QDX which comes up with a COM port number.? Switching on the QDX brings up USB Serial Device (COM5) as the active port.? Using PuTTY and selecting Serial and COM5 and clicking the Open button gives the following popup: I assume that this indicates that the port is locked?? Trying to run WSJT-X gives a Rig Control Error as follows: Hamlib error: rig_token_lookup called for no_xchg rig_confparam_lookup called for no_xchg 1:rig.c(817):rig_open entered rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\WSJT\wsjtx rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist rig_open: async_data_enable=0, async_data_supported=0 serial_open: COM5 serial_open(229): open failed#1 serial_open(229): open failed#2 serial_open(229): open failed#3 serial_open(229): open failed#4 serial_open: Unable to open COM5 - No such file or directory port_open: serial_open(COM5) status=-6, err=No such file or directory rig_open: rs->comm_state==0?=0 1:rig.c(1023):rig_open returning(-6) IO error ? IO error IO error while opening connection to rig ? Timestamp: 2023-02-09T05:23:03.879Z Does anyone have an idea of what may be causing this problem? Any help or suggestions as to what to try would be greatly appreciated. Regards Greg VK4GRM |
|
Hi Paul I can add those pads for the next PCB revision yes. But there are already 1000 Rev 5 in production now so it will take some time to get through those. For now, I imagine this will be a rare requirement... and is not incrementally too hard, considering you already will need to remove the 25MHz TCXO and make modifications, to solder on a wire to the existing pads... Note that you do need to ensure you use a 25MHz external reference, not some other frequency. QDX will ONLY work on 25MHz reference, it's used for *everything*... generating the 48 MHz clock for USB, the 24.576 MHz master clock for 512fs (48ksps) ADC I2S bus, all the internal timing, you name it.? 73 Hans G0UPL On Thu, Feb 9, 2023 at 6:11 AM Paul WB6CXC (tech-blog: ) <paul@...> wrote: And any chance of getting two pads on the multi-band (or single-band) QDX, for the external reference input wires?? One at the buffer input, and the other a close-by ground?? There are already available pads for 3.3V and power ground.? I don't mind removing the TCXO coupling cap, so no need for an option there.? These new pads can be small, just big enough for #28 wire would be fine. |
|
Re: QDX - High Band - too 'hot' on 20m
Tom Yes, reducing power supply voltage, and tweaking the toroid turn squeezing to reduce the power output are viable options.? ANOTHER idea (applicable to Rev 4 and up PCBs)... is to reduce the PIN diode forward bias for the band that has too high power output. You can use this PIN diode forward bias to do some equalizing of power across the bands. The control range of the PIN diode forward bias regulator is 5mA to 60mA. You need to go into the configuration by connecting a terminal emulator, then you will find this setting in the Band Configuration screen. The default value is 30mA. As you go lower, eventually you get a fraction of a dB more insertion loss in the PIN diodes and that will be enough to reduce your power output a bit and cool things down. No it doesn't just move heat from the PA to the PIN diodes, it increases the impedance and that reduces the overall current consumption. Try it and you'll see. Note that this is NOT a good plan for 80m (maybe also 60m and 40m). At low HF you NEED the high forward bias current to ensure sufficient linearity performance in the PIN diodes, otherwise you will get 2nd order harmonics generated in the PIN diodes. But on a high-bands QDX you can reduce the forward bias current to put in some fractional-dB insertion loss and take a watt or two off the power output. 73 Hans G0UPL On Thu, Feb 9, 2023 at 6:50 AM Evan Hand <elhandjr@...> wrote: Tom, |
|
Re: QDX - High Band - too 'hot' on 20m
Tom,
I would suggest tweaking the two toroids of the low pass filter.? Reading from the build manual would be L2 and L6.? I would start by spreading the turns on L2 to see if that lowers the power on 20 meters.? If spreading the turns does not help, try compressing the turns on the toroid.? You can also try tweaking L6.? 73 Evan AC9TU |
|
Re: QDX - High Band - too 'hot' on 20m
Tom,
My QDX low band has the same characteristics - much higher output on 80 than on 20. I wound T1 for 9 volts. If I set the input voltage for 4.5 watts out on 20 meters, I get WAY more out on 80 than is healthy for the little transistors. I've gotten around the problem by using a variable voltage input. I bought a little inexpensive boost/buck device on Amazon ()? that allows me to dial the QDX supply voltage to whatever I want. I connected the output of the QDX to my oscilloscope via a three-way BNC plug and measured the RF output voltage on each band, varying the input voltage until I found the right setting that gave me about four watts out. Wrote them down and now when I change bands I set the voltage corresponding to the band I'm using. Takes about three seconds and I know my BS170s age gonna be happy campers! :-) -- Jim / K7TXA Eagle, ID SKCC 10447 BUG 301 |
|
And any chance of getting two pads on the multi-band (or single-band) QDX, for the external reference input wires?? One at the buffer input, and the other a close-by ground?? There are already available pads for 3.3V and power ground.? I don't mind removing the TCXO coupling cap, so no need for an option there.? These new pads can be small, just big enough for #28 wire would be fine.
-- Paul Elliott - WB6CXC |
|
QDX - High Band - too 'hot' on 20m
Just finished up my QDX high band, and when checking the outputs into a dummy load, it's putting out a little over 6 watts (drawing around 1.1 A).? I've configured it to use 12v.?? According to the manual, this is too high and will damage the Q's (and release the 'magic smoke')
Other bands seem to be within expected ranges (3.5, 2.5, 4.0 and 2.5 watts/17m, 15m, 12m and 10m). I've verified components, and didn't find anything out of place. Any ideas/suggestions greatly appreciated. Tom W5VS |
|
Re: Question About Number of Turns
#qcx
37 turns is probably just fine. When you peak the receive in menu 8.7, as long as C1 is not completely closed or open, it's perfectly fine. One turn off on a 40 meter rig is unlikely to be a problem.?
-- 73, Dan? NM3A |
Tim Delaney
Daniel Conklin