Date   

Re: PSK not working with WinWarbler

Dave AA6YQ
 

Transmitting RTTY AFSK uses the same signal paths, soundcard settings, and Windows mixer settings as transmitting PSK – so it’s not obvious why the latter is not working.

 

What changes did you make to your hardware or software around the time PSK transmission stopped working?

 

Do you have a Workspace populated with your “known good” settings?

 

       73,

 

             Dave, AA6YQ

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, July 24, 2017 1:33 PM
To: dxlab@...
Subject: RE: [dxlab] PSK not working with WinWarbler

 



Hi Dave,

 

AFSK.

 

Jim

 





Re: VS: Question

Jan Langerud <ja-lan@...>
 

The reply from  waiting for TQSL waiting to complete processing.  Upload to LotW add requested  qso. Was waiting approx. 1 hour and nothing happens.

 

Upgrade DxKeeper.exe from 7.1.9 to 14.0.1. Only a popup flashes and nothing happens.

 

73

Jan, LA6JEA

 

Fra: dxlab@... [mailto:dxlab@...]
Sendt: 24. juli 2017 14:23
Til: dxlab@...
Emne: Re: [dxlab] VS: Question

 

 

Why does what not stop?

On your DXKeeper question, what did you do, what did you expect to happen, what actually happened?
--
73, Rich - W3ZJ
www.w3zj.com

On 7/24/2017 5:22 AM, 'Jan Langerud' ja-lan@... [dxlab] wrote:

Emne: Question
 
 
 
Morning
 
Why does this not stop?
 
I am also not able to update Dxkeeper.exe in Dxlab (why?)
 
 
 
Vy 73  La6jea

 


Re: VS: Question

Jan Langerud <ja-lan@...>
 

Hi thanks for reply.

See commentes in red.

 

73

Jan.  LA6JEA

 

Fra: dxlab@... [mailto:dxlab@...]
Sendt: 24. juli 2017 16:21
Til: dxlab@...
Emne: RE: [dxlab] VS: Question

 

 

>>>AA6YQ comments below


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, July 24, 2017 5:23 AM
To:
dxlab@...
Subject: [dxlab] VS: Question

Why does this not stop?

>>>To what does the word "this" refer?

When I upload to LotW the ADD Requested (2100 qso), the popup window say Waiting for TQSL to complete processing.  I did wait for approx. 1 hour. Nothing happens.



I am also not able to update Dxkeeper.exe in Dxlab (why?)

>>>Exactly what happens when you direct the DXLab Launcher to update DXKeeper?

When I try to upgrade DxKeeper.exe from 7.1.9 to 14.0.7 a popup flash and will not start the upgrade. All the rest upgrade went OK.



73,

Dave, AA6YQ


Re: PSK not working with WinWarbler

Jim Cary
 

Hi Dave,

AFSK.

Jim


Re: PSK not working with WinWarbler

Dave AA6YQ
 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, July 24, 2017 11:15 AM
To: dxlab@...
Subject: [dxlab] PSK not working with WinWarbler

 

My RTTY is working fine with WinWarbler, but all of a sudden PSK is not.  When I go to PSK the transmitter keys, but no audio is generated.  The PSK settings are per the DXLab Wiki.  Like I said, it works fine in RTTY, but not PSK.

 

>>>Are you transmitting RTTY via AFSK or FSK?

 

       73,

 

             Dave, AA6YQ


Re: eQSL.cc Automatic Mode Update - Need Advice

Dave AA6YQ
 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, July 24, 2017 11:38 AM
To: dxlab@...
Subject: [dxlab] eQSL.cc Automatic Mode Update - Need Advice

 




I just logged into eQSL.cc to fix up some unmatched calls. One of the calls I noticed used mode PSK which I thought was odd.

 

When I logged into eQSL.cc it notified me of a mode update apparently related to ADIF v3.0.4. I ran the program and now it looks like it is about to change a lot of what I had previously recorded. For example:

 

Old Mode

New Mode

New SubMode

ADIF Version

 

PSK31

PSK

PSK31

3.0.4

PSK125

PSK

PSK125

3.0.4

 

PSK63

PSK

PSK63

3.0.4

 

How is the change going to affect DXKeeper logs or matching? Should I make changes or should I abort?

 

I much prefer all changes be made in DXKeeper and, if possible, DXKeeper keeps online logs in sync. DXKeeper is the database of record.

 

I know a lot of people like to use eQSL and Club Log and some others but this concern brings me one step closer ending all those updates and sticking with LotW only. eQSL.cc seems to require a whole lot of maintenance. I mainly keep it so I can confirm SWL reports.

 

73,

Kev K4VD





eQSL.cc Automatic Mode Update - Need Advice

kevin@...
 

I just logged into eQSL.cc to fix up some unmatched calls. One of the calls I noticed used mode PSK which I thought was odd.


When I logged into eQSL.cc it notified me of a mode update apparently related to ADIF v3.0.4. I ran the program and now it looks like it is about to change a lot of what I had previously recorded. For example:


Old ModeNew ModeNew SubModeADIF Version

PSK31PSKPSK313.0.4
PSK125PSKPSK1253.0.4

PSK63PSKPSK633.0.4


How is the change going to affect DXKeeper logs or matching? Should I make changes or should I abort?


I much prefer all changes be made in DXKeeper and, if possible, DXKeeper keeps online logs in sync. DXKeeper is the database of record.


I know a lot of people like to use eQSL and Club Log and some others but this concern brings me one step closer ending all those updates and sticking with LotW only. eQSL.cc seems to require a whole lot of maintenance. I mainly keep it so I can confirm SWL reports.


73,

Kev K4VD


PSK not working with WinWarbler

Jim Cary
 

My RTTY is working fine with WinWarbler, but all of a sudden PSK is not.  When I go to PSK the transmitter keys, but no audio is generated.  The PSK settings are per the DXLab Wiki.  Like I said, it works fine in RTTY, but not PSK.


The rig is a K3.


Jim

W2SM




Re: Dual QTH , incremental log update and LOTW

Dave AA6YQ
 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, July 24, 2017 8:20 AM
To: dxlab@...
Subject: [dxlab] Dual QTH , incremental log update and LOTW

 



Dear Dave,
Dear All,

My present query is about DXKeeper and the possibility of incremental updating // vs. LOTW.
Description:

I have 2 QTHs few miles away one from the other, A and B. I use in both QTHs the same callsign OD5YA, and they have the same grid square location. I have installed in each QTH the same rig: IC7300, R8 vertical, Dxlabsuite with a windows 7 professional PC. All systems work perfectly and correctly.

Suppose i have in QTH A dxkeeper 1500 qso's logged. I move for the weekend to QTHB (actually it happened this past weekend) and find out that i only have 1450 QSO's in my log because I did not update QTH B with the latest qso's. So, I work radio during the weekend and log some 210 NEW qso's from QTH B. Now I have in B 1450 + 210 =1660 qso's. I export to an ADIF (call it ADIF B)file and carry it back with me to QTH A today. If I import the ADIF B into location A (having 1500 qso's) I will be importing 1660 qso's, however the log should show  1500 + 210 = 1710 qso's because the 50 QSO i did at QTHA were not incrementally added to the imported file. In that case i will loose the 50 (incremental) QSO that were made at QTH A.

Questions:

1- Is there a way to have an incremental export like only exporting the 210 QSO's I did over the week end from QTH B ? i.e. can I export only those 210 qso's by filtering the date, so that, when weekend is over and i come back to QTH A I just increase the existing QSO's by the new 210 ones only?

2- If the above 1- is not possible, what do you suggest can be done? I know that the best way is to have QTH A exported to cloud BEFORE weekend, hence all 1500 qso's are in cloud, then import into QTH B before operating and then exporting QTH B..... it is tedious and requires remembering to do that before each and every weekend.

3- When I am uploading LOTW from QTH A (i  upload LOTW from A only) I am clicking on ADD REQUESTED, it shows 244 QSO's, when I upload, it says none uploaded because of 24 qso's  duplicate. How can I detect what are those duplicate and how can I remedy DXlab upload function? please note that I exported to ADIF and uploaded from TQSL and all went perfectly well and no error was mentioned. Only when I do it from DXlab and only recently (after this QTH A and B thing started I guess !!!!)

4- When I am uploading to eQSL, no duplicate error is announced and the upload happens with no problem. I am only getting a return page saying I have some SWL qsl pending. How can I answer the SWL's? Or is it just an information that eQSL is sending me that requires no further attention from my side?

all the best and thank you for the help. I truly appreciate it.

 

>>>You can filter the Log Page Display by date range by using the Advanced Sorts, Filters, and Modifiers window. When you select the Main window’s Export tab with the Log Page Display Filtered, DXKeeper will ask if you want the filter removed; click the “No” button, and then initiate the Export operation.

 

>>>If you’re going to operate from two locations as you describe, the only reliable approach is to ensure that the system you’re about to use to log QSOs, update LoTW, print QSL cards, or process incoming QSL cards contains your “master” log file. You can move the “master” log file between systems via the cloud, or with a thumb drive. This requires discipline, but you’re more likely to execute this process reliably than by continuously exporting subsets of your log from one system to the other.

 

>>>eQSL support for SWL confirmations is to my knowledge not documented, and thus not supported by DXKeeper.

 

      73,

 

            Dave, AA6YQ


Re: change in eQSL.cc Inbox

Dave AA6YQ
 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, July 24, 2017 8:14 AM
To: dxlab@...
Subject: [dxlab] Re: change in eQSL.cc Inbox

 

does that mean we should be looking back through our logs to assign sub-modes correctly to achieve matches with the augmented eQSL records or will differences be offered as warnings like zone, grid etc are when syncing LotW records?

I guess the important issue is whether a sub-mode only mismatch still constitutes an eQSL match.

 

>>>It should not be necessary to change any already-logged QSOs, or change the way QSOs are logged in the future from the way you’ve been logging them in the past.

 

       73,

 

              Dave, AA6YQ


Re: VS: Question

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, July 24, 2017 5:23 AM
To: dxlab@...
Subject: [dxlab] VS: Question

Why does this not stop?

To what does the word "this" refer?

I am also not able to update Dxkeeper.exe in Dxlab (why?)

Exactly what happens when you direct the DXLab Launcher to update DXKeeper?
73,

Dave, AA6YQ


Re: Dual QTH , incremental log update and LOTW

ghassan chammas
 

Dear Joe

Thank you very much.
Never ever had a faster response in any support system I invoked.
Faster then an ambulance. !!!!

Regards

Dr.Ghassan Chammas
AC2RA -- also OD5YA - Beirut - Lebanon

____________________________________

On 24/7/17 3:36 PM, 'Joe Subich, W4TV' lists@... [dxlab] wrote:

 


> 1- Is there a way to have an incremental export like only exporting
> the 210 QSO's I did over the week end from QTH B ?

Yes.

> i.e. can I export only those 210 qso's by filtering the date, so
> that, when weekend is over and i come back to QTH A I just increase
> the existing QSO's by the new 210 ones only?
Yes, enter YYYY-MM-DD in the filter textbox and click on the "Since"
button. This is even easier after the first use of the "Since" filter
as a Control-click on the "Since" button will filter for all QSOs since
the last time the "Since" filter was invoked.

I use this all the time to export QSOs from my "radio" computer for
importing into my laptop (where I do my QSL management).

> 3- When I am uploading LOTW from QTH A (i upload LOTW from A only) I
> am clicking on ADD REQUESTED, it shows 244 QSO's, when I upload, it
> says none uploaded because of 24 qso's duplicate.

In the QSL Config -> LotW tab, check "Permit uploading of QSOs already
uploaded to LotW". In the future, confine uploading to DXKeeper to
avoid confusing tQSL.

> I am only getting a return page saying I have some SWL qsl pending.
> How can I answer the SWL's?

DXKeeper does not automate eQSL SWL reports. You will need to go online
to eQSL and handle them manually.

73,

... Joe, W4TV

On 7/24/2017 8:19 AM, Ghassan Chammas ac2ra@... [dxlab] wrote:
> Dear Dave,
> Dear All,
>
> My present query is about DXKeeper and the possibility of incremental
> updating // vs. LOTW.
> Description:
>
> I have 2 QTHs few miles away one from the other, A and B. I use in both
> QTHs the same callsign OD5YA, and they have the same grid square
> location. I have installed in each QTH the same rig: IC7300, R8
> vertical, Dxlabsuite with a windows 7 professional PC. All systems work
> perfectly and correctly.
>
> Suppose i have in QTH A dxkeeper 1500 qso's logged. I move for the
> weekend to QTHB (actually it happened this past weekend) and find out
> that i only have 1450 QSO's in my log because I did not update QTH B
> with the latest qso's. So, I work radio during the weekend and log some
> 210 NEW qso's from QTH B. Now I have in B 1450 + 210 =1660 qso's. I
> export to an ADIF (call it ADIF B)file and carry it back with me to QTH
> A today. If I import the ADIF B into location A (having 1500 qso's) I
> will be importing 1660 qso's, however the log should show 1500 + 210 =
> 1710 qso's because the 50 QSO i did at QTHA were not incrementally added
> to the imported file. In that case i will loose the 50 (incremental) QSO
> that were made at QTH A.
>
> Questions:
>
> 1- Is there a way to have an incremental export like only exporting the
> 210 QSO's I did over the week end from QTH B ? i.e. can I export only
> those 210 qso's by filtering the date, so that, when weekend is over and
> i come back to QTH A I just increase the existing QSO's by the new 210
> ones only?
>
> 2- If the above 1- is not possible, what do you suggest can be done? I
> know that the best way is to have QTH A exported to cloud BEFORE
> weekend, hence all 1500 qso's are in cloud, then import into QTH B
> before operating and then exporting QTH B..... it is tedious and
> requires remembering to do that before each and every weekend.
>
> 3- When I am uploading LOTW from QTH A (i upload LOTW from A only) I am
> clicking on ADD REQUESTED, it shows 244 QSO's, when I upload, it says
> none uploaded because of 24 qso's duplicate. How can I detect what are
> those duplicate and how can I remedy DXlab upload function? please note
> that I exported to ADIF and uploaded from TQSL and all went perfectly
> well and no error was mentioned. Only when I do it from DXlab and only
> recently (after this QTH A and B thing started I guess !!!!)
>
> 4- When I am uploading to eQSL, no duplicate error is announced and the
> upload happens with no problem. I am only getting a return page saying I
> have some SWL qsl pending. How can I answer the SWL's? Or is it just an
> information that eQSL is sending me that requires no further attention
> from my side?
>
> all the best and thank you for the help. I truly appreciate it.



Re: Dual QTH , incremental log update and LOTW

Joe Subich, W4TV
 

1- Is there a way to have an incremental export like only exporting
the 210 QSO's I did over the week end from QTH B ?
Yes.

i.e. can I export only those 210 qso's by filtering the date, so
that, when weekend is over and i come back to QTH A I just increase
the existing QSO's by the new 210 ones only?
Yes, enter YYYY-MM-DD in the filter textbox and click on the "Since"
button. This is even easier after the first use of the "Since" filter
as a Control-click on the "Since" button will filter for all QSOs since
the last time the "Since" filter was invoked.

I use this all the time to export QSOs from my "radio" computer for
importing into my laptop (where I do my QSL management).

3- When I am uploading LOTW from QTH A (i upload LOTW from A only) I
am clicking on ADD REQUESTED, it shows 244 QSO's, when I upload, it
says none uploaded because of 24 qso's duplicate.
In the QSL Config -> LotW tab, check "Permit uploading of QSOs already
uploaded to LotW". In the future, confine uploading to DXKeeper to
avoid confusing tQSL.

I am only getting a return page saying I have some SWL qsl pending.
How can I answer the SWL's?
DXKeeper does not automate eQSL SWL reports. You will need to go online
to eQSL and handle them manually.

73,

... Joe, W4TV


On 7/24/2017 8:19 AM, Ghassan Chammas ac2ra@... [dxlab] wrote:
Dear Dave,
Dear All,
My present query is about DXKeeper and the possibility of incremental updating // vs. LOTW.
Description:
I have 2 QTHs few miles away one from the other, A and B. I use in both QTHs the same callsign OD5YA, and they have the same grid square location. I have installed in each QTH the same rig: IC7300, R8 vertical, Dxlabsuite with a windows 7 professional PC. All systems work perfectly and correctly.
Suppose i have in QTH A dxkeeper 1500 qso's logged. I move for the weekend to QTHB (actually it happened this past weekend) and find out that i only have 1450 QSO's in my log because I did not update QTH B with the latest qso's. So, I work radio during the weekend and log some 210 NEW qso's from QTH B. Now I have in B 1450 + 210 =1660 qso's. I export to an ADIF (call it ADIF B)file and carry it back with me to QTH A today. If I import the ADIF B into location A (having 1500 qso's) I will be importing 1660 qso's, however the log should show 1500 + 210 = 1710 qso's because the 50 QSO i did at QTHA were not incrementally added to the imported file. In that case i will loose the 50 (incremental) QSO that were made at QTH A.
Questions:
1- Is there a way to have an incremental export like only exporting the 210 QSO's I did over the week end from QTH B ? i.e. can I export only those 210 qso's by filtering the date, so that, when weekend is over and i come back to QTH A I just increase the existing QSO's by the new 210 ones only?
2- If the above 1- is not possible, what do you suggest can be done? I know that the best way is to have QTH A exported to cloud BEFORE weekend, hence all 1500 qso's are in cloud, then import into QTH B before operating and then exporting QTH B..... it is tedious and requires remembering to do that before each and every weekend.
3- When I am uploading LOTW from QTH A (i upload LOTW from A only) I am clicking on ADD REQUESTED, it shows 244 QSO's, when I upload, it says none uploaded because of 24 qso's duplicate. How can I detect what are those duplicate and how can I remedy DXlab upload function? please note that I exported to ADIF and uploaded from TQSL and all went perfectly well and no error was mentioned. Only when I do it from DXlab and only recently (after this QTH A and B thing started I guess !!!!)
4- When I am uploading to eQSL, no duplicate error is announced and the upload happens with no problem. I am only getting a return page saying I have some SWL qsl pending. How can I answer the SWL's? Or is it just an information that eQSL is sending me that requires no further attention from my side?
all the best and thank you for the help. I truly appreciate it.


Re: VS: Question

Richard B Drake
 

Why does what not stop?

On your DXKeeper question, what did you do, what did you expect to happen, what actually happened?
--
73, Rich - W3ZJ
www.w3zj.com

On 7/24/2017 5:22 AM, 'Jan Langerud' ja-lan@... [dxlab] wrote:

Emne: Question

 

Morning

Why does this not stop?

I am also not able to update Dxkeeper.exe in Dxlab (why?)

 

Vy 73  La6jea


Dual QTH , incremental log update and LOTW

ghassan chammas
 

Dear Dave,
Dear All,

My present query is about DXKeeper and the possibility of incremental updating // vs. LOTW.
Description:

I have 2 QTHs few miles away one from the other, A and B. I use in both QTHs the same callsign OD5YA, and they have the same grid square location. I have installed in each QTH the same rig: IC7300, R8 vertical, Dxlabsuite with a windows 7 professional PC. All systems work perfectly and correctly.

Suppose i have in QTH A dxkeeper 1500 qso's logged. I move for the weekend to QTHB (actually it happened this past weekend) and find out that i only have 1450 QSO's in my log because I did not update QTH B with the latest qso's. So, I work radio during the weekend and log some 210 NEW qso's from QTH B. Now I have in B 1450 + 210 =1660 qso's. I export to an ADIF (call it ADIF B)file and carry it back with me to QTH A today. If I import the ADIF B into location A (having 1500 qso's) I will be importing 1660 qso's, however the log should show  1500 + 210 = 1710 qso's because the 50 QSO i did at QTHA were not incrementally added to the imported file. In that case i will loose the 50 (incremental) QSO that were made at QTH A.

Questions:

1- Is there a way to have an incremental export like only exporting the 210 QSO's I did over the week end from QTH B ? i.e. can I export only those 210 qso's by filtering the date, so that, when weekend is over and i come back to QTH A I just increase the existing QSO's by the new 210 ones only?

2- If the above 1- is not possible, what do you suggest can be done? I know that the best way is to have QTH A exported to cloud BEFORE weekend, hence all 1500 qso's are in cloud, then import into QTH B before operating and then exporting QTH B..... it is tedious and requires remembering to do that before each and every weekend.

3- When I am uploading LOTW from QTH A (i  upload LOTW from A only) I am clicking on ADD REQUESTED, it shows 244 QSO's, when I upload, it says none uploaded because of 24 qso's  duplicate. How can I detect what are those duplicate and how can I remedy DXlab upload function? please note that I exported to ADIF and uploaded from TQSL and all went perfectly well and no error was mentioned. Only when I do it from DXlab and only recently (after this QTH A and B thing started I guess !!!!)

4- When I am uploading to eQSL, no duplicate error is announced and the upload happens with no problem. I am only getting a return page saying I have some SWL qsl pending. How can I answer the SWL's? Or is it just an information that eQSL is sending me that requires no further attention from my side?

all the best and thank you for the help. I truly appreciate it.
--

Dr.Ghassan Chammas
AC2RA -- also OD5YA - Beirut - Lebanon

____________________________________


Re: change in eQSL.cc Inbox

g4wjs
 

Hi Dave,

does that mean we should be looking back through our logs to assign sub-modes correctly to achieve matches with the augmented eQSL records or will differences be offered as warnings like zone, grid etc are when syncing LotW records?

I guess the important issue is whether a sub-mode only mismatch still constitutes an eQSL match.

73
Bill
G4WJS.


VS: Question

Jan Langerud <ja-lan@...>
 

Fra: Jan Langerud [mailto:ja-lan@...]
Sendt: 12. juli 2017 14:35
Til: dxlab-subscribe@...
Emne: VS: Question







Fra: Jan Langerud [mailto:ja-lan@...]
Sendt: 12. juli 2017 14:04
Til: 'dxlab@...'
Emne: Question



Morning

Why does this not stop?

I am also not able to update Dxkeeper.exe in Dxlab (why?)



Vy 73 La6jea

Jan Langerud

Email: ja-lan@...

Phone: +47 928 60438


change in eQSL.cc Inbox

Dave AA6YQ
 

When you invoke DXKeeper’s “Sync eQSL.cc QSLs” function, the “Inbox” returned by eQSL now specifies both MODE and SUBMODE for each QSO whose MODE includes one or more SUBMODEs in the ADIF specification, whereas it previously only specified MODE. Thus if you submitted a QSO to eQSL.cc whose MODE is PSK31, the “Inbox” entry will now specify

 

PSKPSK31

 

Previous (a few days ago), the “Inbox” entry specified

 

PSK31

 

This change causes the DXKeeper’s “Sync eQSL.cc QSLs” function to incorrectly report “no QSO matching callsign, band, and mode“.

 

I have extended a new version of DXKeeper to handle this change, and sent it to several users to test. When this new version (or its descendant) is publicly released, you’ll be able to set the “Last eQSL Sync Date” back in time, and thus reprocess eQSL confirmations that were incorrectly rejected as a result of the Inbox change.

 

Plus ça change, plus c'est la même chose.

 

       73,

 

              Dave, AA6YQ/VE2

 


Re: Kenwood TS-850 and Commander settings

Ed Douglass
 

Thanks for your continuing interest, Dave.

No scope here so I can't follow your suggestion.

On Sun, Jul 23, 2017 at 8:56 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, July 23, 2017 9:38 PM
To: dxlab@...
Subject: Re: [dxlab] Kenwood TS-850 and Commander settings



Thanks, Dave.  All of your setting suggestions are what I have been using.  The serial cable is not the null modem type. There are no bent pins. 

The dual serial port is old.  The manufacturer was NetMos Technology.  In November 2012, NetMos was acquired by MosChip Semiconductor.  The driver number was NM9835S.  It could the 98 in the number is a reference to Windows 98? That old??  In February of this year, the company that is responsible and supplies drivers became ASIX Electronics.  Their driver number, MCS9835, is version 2.0.4.0  It is digitally signed by Microsoft Windows Compatibility Publisher.

Here's a thought.  This card was working in Windows 7.  I think it has not worked since I changed the motherboard and began using Windows 10, 64 bit.  Could it be that this old dual port card can no longer make it in the W10 environment?  This would fit your suspicion that I have a hardware problem and not a DXLab software issue.

 

>>>Since there are no reported but uncorrected defects in Commander, and since many ops successfully use Commander with Kenwood radios every day, it is unlikely that your situation is the result of a defect in Commander.

 

>>>If you have an oscilloscope, monitor the radio’s CAT port’s TX data pin to see if there’s any response to the CAT commands being sent by Commander.

 

     73,

 

             Dave, AA6YQ



Re: Kenwood TS-850 and Commander settings

Dave AA6YQ
 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, July 23, 2017 9:38 PM
To: dxlab@...
Subject: Re: [dxlab] Kenwood TS-850 and Commander settings



Thanks, Dave.  All of your setting suggestions are what I have been using.  The serial cable is not the null modem type. There are no bent pins. 

The dual serial port is old.  The manufacturer was NetMos Technology.  In November 2012, NetMos was acquired by MosChip Semiconductor.  The driver number was NM9835S.  It could the 98 in the number is a reference to Windows 98? That old??  In February of this year, the company that is responsible and supplies drivers became ASIX Electronics.  Their driver number, MCS9835, is version 2.0.4.0  It is digitally signed by Microsoft Windows Compatibility Publisher.

Here's a thought.  This card was working in Windows 7.  I think it has not worked since I changed the motherboard and began using Windows 10, 64 bit.  Could it be that this old dual port card can no longer make it in the W10 environment?  This would fit your suspicion that I have a hardware problem and not a DXLab software issue.

 

>>>Since there are no reported but uncorrected defects in Commander, and since many ops successfully use Commander with Kenwood radios every day, it is unlikely that your situation is the result of a defect in Commander.

 

>>>If you have an oscilloscope, monitor the radio’s CAT port’s TX data pin to see if there’s any response to the CAT commands being sent by Commander.

 

     73,

 

             Dave, AA6YQ

41261 - 41280 of 211173