Locked
Re: Alinco DX-SR8T, DX-Commander and WSJYX rig control
Dave AA6YQ
+ AA6YQ comments below
Wait.... what.... ? Ok, either I am way too tired & am misreading what you just said, or you're too tired and forgot what work you did on your own program that you just linked... ...or both... But here is what it says on your linked page... (green emphasis, mine) " * Control your Transceiver from your PC Screenshot with right side of window showing filters and frequency-dependent device settings * Alinco DX77-E, DX77-T, DX-SR8 * Looks to me like you did hear about it, and supported it.... + You are assuming that a DX-SR8 and a DX-SR8T are the same radio, or at least employ the same CAT instruction set. Is that the case? + Think the Yaesu FTDX-101 is anything like an FT-101? 73, Dave, AA6YQ |
|||||
|
|||||
Locked
Re: Alinco DX-SR8T, DX-Commander and WSJYX rig control
JP Tucson, AZ
Wait.... what.... ? Ok, either I am way too tired & am misreading what you just said, or you're too tired and forgot what work you did on your own program that you just linked... ...or both... But here is what it says on your linked page... (green emphasis, mine) "
Looks to me like you did hear about it, and supported it.... Ok folks, Mulligans all the way around... let's try again... 73 - John - N7GHZ On Mon, Jun 1, 2020, 10:28 PM Dave AA6YQ <aa6yq@...> wrote: + AA6YQ comments below |
|||||
|
|||||
Locked
Re: Alinco vDX-Commander and WSJYX rig control
Dave AA6YQ
+ AA6YQ comments below
DX-8SR is the seventh transceiver in Commander's list of transceivers. + Commander supports the DX-SR8. Is this the same as the DX-SR8T? 73, Dave, AA6YQ |
|||||
|
|||||
Locked
Re: Alinco DX-SR8T, DX-Commander and WSJYX rig control
Dave AA6YQ
+ AA6YQ comments below
My radio is not in that page, i add an xml to gain access and control it + Commander does not support the DX-SR8T, for two reasons: 1. I didn't know that the DX-SR8T existed before reading this thread 2. No one has ever asked that Commander be extended to support the DX-SR8T + The radios supported by Commander are listed here: <https://www.dxlabsuite.com/commander/> + The fact that you "added an XML" (whatever that means) to obtain some subset of transceiver control functionality does not mean that Commander will be able to provide transceiver control services to WSJT-X with this radio selected. + If you point me at a specification of the DX-SR8T's CAT protocol, I'll be able to consider extending Commander to support it. 73, Dave, AA6YQ (Developer, DXLab) |
|||||
|
|||||
Locked
Re: Language Change rc3.
On Mon, Jun 1, 2020 at 09:55 AM, Bill Somerville wrote:
--language=enThanks Bill for your answer. I don't use spaces in the argument. I have tried again and I can't get the interface to be in English.
Thank you. Cedric EA4AC |
|||||
|
|||||
Locked
Re: My request for info about FT891 and macbook.
I have just run a simple test comparing my FT-991 to my FT-891.
On the left is a “snip” from Device Manager.
I connected DC power to the FT-991, plugged in a USB cable from PC to RIG, and ran Device Manager.
There are two Audio CODECS.
Here I did the same thing with my FT-891.
There are no Audio CODECS.
I had been confused about this for some time and even though I have a SignaLink, I bought an SCU-17 to try to learn more.
I could have saved the money if I had done what I did today 😉
Cheers and 73,
Greg Winterflood VK8KMD Alice Springs, Central Australia
From: main@WSJTX.groups.io <main@WSJTX.groups.io>
On Behalf Of Tom Arny
Sent: Tuesday, 2 June 2020 12:05 To: WSJTX@groups.io Subject: [WSJTX] My request for info about FT891 and macbook.
I wanted to thank the several people who made excellent and helpful suggestions about how to get my FT891 running WSJTx on a MacBook. It is working splendidly now. I ended up going the Signalink route with two cables to the laptop..one from the FT891’s USB port and one from its data port. I could not find a Mac driver at the Yaesu site, but I did have the driver for the (I think) FT991 from SiLabs and that seems to work. When I finish playing around with the working set-up, I’ll try going to just one cable. Thank you all again. It’s a great group. |
|||||
|
|||||
Locked
Re: Effect of TX IM3 on SN
My error
Mark was covering IMD (not too good on 3rd) while my mind drifted to TX phase noise (awesome)
73 W5AJ
Robert Midland, Texas
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Mark N2QT via groups.io
Actually no. Take a look at ARRLs review in Jan 09 QST. They showed TX 3rd order at 25 dB which is pretty bad don’t you think. That was probably due to them running the k3 at a lower dc voltage. |
|||||
|
|||||
Locked
Re: Strike through zero font
Joe Subich, W4TV
For Windows, several of the built-in fonts include a "slashed" zero.
toggle quoted message
Show quoted text
Of particular interest are Andale Mono and Consolas - both are mono spaced fonts. Mono spaced fonts are ideal for use with WSJTX RX Window, e-mail programs and spreadsheets where one wants columns to line up. 73, ... Joe, W4TV On 2020-06-01 10:04 PM, Jim Shorney wrote:
The problem with this method is the ALT character does not render as an actual zero to any software that is looking for numbers. This can cause unexpected problems. Best to use a font that actually supports the slashed zero. |
|||||
|
|||||
Locked
Re: Alinco DX-SR8T, DX-Commander and WSJYX rig control
Joe Subich, W4TV
DX-8SR is the seventh transceiver in Commander's list of transceivers.
toggle quoted message
Show quoted text
If your installation does not have it, you need to update the Radios.txt file in the Commander directory. I've been using DXLab Suite for more than 20 years and don't know how to expand the list of controllable transceivers through an XML file. Please explain *in detail* what you are doing. The error message you post indicates that Commander does not know the mode of your transceiver. 73, ... Joe, W4TV On 2020-06-01 10:33 PM, robert gagnon wrote:
My radio is not in that page, i add an xml to gain access and control itOn Jun 1, 2020, at 5:34 PM, d_ziolkowski <dan.ziolkowski@...> wrote: |
|||||
|
|||||
Locked
My request for info about FT891 and macbook.
Tom Arny
I wanted to thank the several people who made excellent and helpful suggestions about how to get my FT891 running WSJTx on a MacBook. It is working splendidly now.
I ended up going the Signalink route with two cables to the laptop..one from the FT891’s USB port and one from its data port. I could not find a Mac driver at the Yaesu site, but I did have the driver for the (I think) FT991 from SiLabs and that seems to work. When I finish playing around with the working set-up, I’ll try going to just one cable. Thank you all again. It’s a great group. |
|||||
|
|||||
Locked
Re: Alinco DX-SR8T, DX-Commander and WSJYX rig control
robert gagnon
My radio is not in that page, i add an xml to gain access and control it
toggle quoted message
Show quoted text
On Jun 1, 2020, at 5:34 PM, d_ziolkowski <dan.ziolkowski@...> wrote:
|
|||||
|
|||||
Locked
Re: Strike through zero font
Monty Wilson, NR0A
A second problem is this impacts the handi-hams that are blind. Their screen readers will see the slashed zero and the letter O and their screen readers will read out NI OH K or NR OH A.
toggle quoted message
Show quoted text
Monty Wilson, NR0A Jwilson16@... -----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Jim Shorney Sent: Monday, June 1, 2020 09:05 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] Strike through zero font The problem with this method is the ALT character does not render as an actual zero to any software that is looking for numbers. This can cause unexpected problems. Best to use a font that actually supports the slashed zero. http://www.g0hwc.com/ham_radio_fonts.html 73 -Jim NU0C On Mon, 1 Jun 2020 20:42:01 -0500 "john ni0k" <jasimmons@...> wrote: How to make a “Slashed Ø” for your Callsign Mark R. Henry, WAØWIK |
|||||
|
|||||
Locked
Re: Strike through zero font
And some more here:
http://www.wm8c.com/slashed_zero_fonts.htm 73 -Jim NU0C On Mon, 1 Jun 2020 21:04:51 -0500 "Jim Shorney" <jshorney@...> wrote: The problem with this method is the ALT character does not render as an actual zero to any software that is looking for numbers. This can cause unexpected problems. Best to use a font that actually supports the slashed zero. |
|||||
|
|||||
Locked
Re: no power output when all else seems to be OK
Henry Kiernan
Hi Bill and Joe
output problem solved - shazaam! receive problem remains.
new soundcard, unlike my old one, has no "line-out" port. so I connected playback mode to the new card's speakers port. turns out the output has to be connected to the new card's "headphone" port (which I tried out of desperation). voila! immediately made a good qso with LZ1RR, -8 report. when in transmit, "playback" shows full max green bars going out. so settings were all OK.
receive problem remains however. this AM I was receiving 25-35 decodes every 15 seconds on old computer, but only 5-10 decodes on new computer. when in "recording" only getting 1 occasional green bar on receive, suggesting very low input to computer. enough to decode a few signals but far less than what is on the band.
old computer set to 0 db in recording level, see only 1 bar, WSJTX slider around 50-60 level (more than 30 recommended)
new computer set to 0 db in recording level, and 0 mic boost, see no bars in record, WSJTX slider around 40
if I change new computer to 9db recording level and 30 db mic boost (max), WSJTX slider goes into red zone above 80 and I see a few more bars in record, but still see same number of decodes - still less than half what old computer sees at same time.
so something still left to figure out. any ideas?
Hank
-----Original Message-----
From: Bill Somerville <g4wjs@...> To: main@WSJTX.groups.io Sent: Mon, Jun 1, 2020 11:40 am Subject: Re: [WSJTX] no power output when all else seems to be OK On 01/06/2020 16:35, Henry Kieran via groups.io wrote:
> not sure what rig setting could be the problem - equipment is same as > it always has been except new computer/sound card, and old computer > works just fine. rig is in USB mode when testing Tx, not USB-D. > however I tried it with USB-D and get same result - no output. > > Hank Hi Hank, rig does not take audio from rear data connector unless you have USB-D selected, also you need that to make the microHAM router use BBB DIGITAL mode. If you check the WSJT-X "Settings->Radio->Mode->Data/PKT" option then that should all happen automatically. 73 Bill G4WJS. |
|||||
|
|||||
Locked
Re: Strike through zero font
The problem with this method is the ALT character does not render as an actual zero to any software that is looking for numbers. This can cause unexpected problems. Best to use a font that actually supports the slashed zero.
http://www.g0hwc.com/ham_radio_fonts.html 73 -Jim NU0C On Mon, 1 Jun 2020 20:42:01 -0500 "john ni0k" <jasimmons@...> wrote: How to make a “Slashed Ø” for your Callsign |
|||||
|
|||||
Locked
Re: Effect of TX IM3 on SN
Hasan Schiers N0AN
Making comments about 200-300 watts being excessive power primarily indicates that the person has no real experience in weak signal work on either 160 or 6 meters with WSJT-X modes. Before making such patently silly pronouncements, do more homework, because that 65 years of so-called experience didn't do the job. 73, N0AN Hasan On Mon, Jun 1, 2020, 7:56 PM Robert W5AJ <woodr90@...> wrote: Mark, your comment "K3, which doesn't have the best TX intermod performance" using WSJT "degrades my tx purity to the point it affects decoding..." |
|||||
|
|||||
Locked
Re: Strike through zero font
john ni0k
Mark R. Henry, WAØWIK Awhile back, someone asked me how I generate a “slashed Ø” when typing my call into an e-mail or other document. Some of you may be familiar with the procedure necessary to do this. So I will explain the procedure for you if you are not “in the know”. The PC uses what are known as “fonts” which are codes used to generate characters on either the screen or in a document. The keys you see on your keyboard are the “normal code page” characters that you use everyday to “talk to” your computer. Hidden inside the installed fonts on your machine are what is known as Alt Codes or Special Characters.These are used to embed seldom-used characters into documents such as this character,which is used in the Spanish, language to “frame” a question. Here is an example. The speaker is asking a question. “¿Habla Espanõl?. In this example, I have used two Alt codes to be able to convey the question in the speaker’s own language; “Do you speak Spanish? One code is the “inverted” question mark ¿” and the other is the “tilde o”. There are approximately 107 Alt Codes available in most fonts commonly installed on your PC. So how do you insert the “slashed Ø” or other special character into your callsign when you want to do so? Below are the steps necessary to do it. 1.Find and push the “Num lock” key on your keyboard. Make sure the “Num lock”light is lit on the keyboard .2.You must use the numerical keypad on your keyboard only to do this. The numerical keypad is generally on the right side of the keyboard and has the numbers1 – Ø and usually a “+” and “-“ key on it as well. The number keys on the top of your keyboard will not work for this operation. 3.Type your normal text such as “This is KC0XXX”. When you get to the “zero” part of the text, press and hold down the “ALT” key on your keyboard. While holding the “Alt” key depressed, enter the code 0216 (Zero, Two, One, Six) on the numerical keypad on your keyboard. When you have entered the above code, release the “Alt”key and you should have a “Ø” in your text. By the way, the “Alt” code for the lowercase slashed zero is 0248. This will give you this character: ø. Personally, I like to capitalize my callsign in correspondence but that is a matter of choice. Also, on some laptop computers, the numerical keypad is embedded into the normal keyboard and will cause all manners of problems if you forget to turn off the “Num lock”function. If you start getting strange characters, check that your “Num lock” function is off. Well that is how you put a “slashed zero” into your documents. NOTE: You can copy and paste the slashed zero. On my laptop the numeric keys are accessed with the Fn key- no need to use the NUM LOCK. -de John NIØK robert kupps wrote on 6/1/2020 5:26 PM: Hi David, |
|||||
|
|||||
Locked
Re: Effect of TX IM3 on SN
Mark N2QT
Actually no. Take a look at ARRLs review in Jan 09 QST. They showed TX 3rd order at 25 dB which is pretty bad don’t you think. That was probably due to them running the k3 at a lower dc voltage.
Not it sure what charts you see, but 12 volt PAs aren’t the gold standard for IM. Mark n2qt |
|||||
|
|||||
Locked
Re: Effect of TX IM3 on SN
Mark, your comment "K3, which doesn't have the best TX intermod performance" using WSJT "degrades my tx purity to the point it affects decoding..."
toggle quoted message
Show quoted text
Nope. The K3 TX IMD was the gold standard for many years (There may be better now but it's still in "Gold" class). It was only rig allowed at many FD operations for years because on same band two modes, No Hash... I use two K3 with SO2R at 100watts, no Hash on rig that is receiving... Unless something is broke in your K3, it's not the TX IMD... Insure your ALC isn't pegged when transmitting and no compression (Default in Data "A") You might be looking at Wrong Graph for K3 TX IMD 73 W5AJ PS: WSJT, 160Meters, 1KW out, FT8 to get a -16 report from TX7T on 160meters....& was happy to put them in log! Robert Midland, Texas -----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Mark N2QT via groups.io Sent: Monday, June 01, 2020 5:43 PM To: WSJTX@groups.io Subject: [WSJTX] Effect of TX IM3 on SN I seem to always get a worse SN report than I give out, especially on 6M. I run an K3 which doesn’t have the best TX intermod performance and I wonder if that degrades my tx purity to the point it affects decoding and the SN report I receive. I do have an amp that ups the power to 600+ watts (and I’ve confirmed it doesn’t degrade the TX IM3 of the exciter alone). Everyone else can’t be running kilowatts, can they? Is SN within wsjt x calculated such that close in intermod products (say 25db down from any desired tone) degrade the result? Mark. N2QT |
|||||
|
|||||
Locked
Re: Effect of TX IM3 on SN
Jim Rogers <rogers9466@...>
Personally I think that is excessive. More than 50 watts is unnecessary in most cases. If you have to resort to power then do a better job on your antenna system. My antenna is a random wire in my attic and I am happy with its performance on 160-6M.
toggle quoted message
Show quoted text
W4ATK 65+ years and still having fun! On Jun 1, 2020, at 7:22 PM, Jim Brown <k9yc@...> wrote: |
|||||
|