Thanks for that info. Getting closer to what I really want. 

--

73 de Amir K9CHP

ARRL, Emergency Coordinator (EC)
Liverpool Amateur Repeater Club www.W2CM.org
Radio Amateurs of Greater Syracuse  www.ragsclub.org
Wilderness SAR (ret.) www.wsar.org
Eagle Valley Search Dogs (ret.) www.evdogs.org

On Mon, Jun 8, 2020, 15:57 John K9IJ <k9ij@...> wrote:

Amir,

While the drop down for power in JTAlertX only goes to 40W, you can type any power level you wish
in the box.. Mine is set to 95W and it works fine and is remembered when I start/stop JTAlertx.

John - K9IJ

On 6/8/2020 12:16 PM, Amir K9CHP wrote:

Thanks for your reply,  Scott.  I traced the source of the 0.1 power logged to JT-Alerts.  Their setting.  And it can be changed up to 40, but never representing the actual power used.  It is thus practically useless for me,  so I  simply disabled Power on the data field entry and move Power column way to the right side of the ACLog window where it won't be seen and bothering me. 

Thanks again for your help. 

--

73 de Amir K9CHP

ARRL, Emergency Coordinator, Onondaga County, NY
Radio Amateurs of Greater Syracuse  www.ragsclub.org
Wilderness SAR www.wsar.org (ret.)
Eagle Valley Search Dogs www.evdogs.org (ret.)

On Mon, Jun 8, 2020, 11:13 Scott Davis via groups.io <SNKDavis=aol.com@groups.io> wrote:

Hi Amir,

Thanks for your follow up and the screen shots.  Perhaps JTAlert has a setting to provide a power value via the API?  That is the only other thing I can think of.  The only 3 ways the power field can get a value is if you type one manually, it carries the previous QSO value forward or JTAlert is sending the value via the API.

One thing to try first - edit the last QSO, then actually close and restart AC Log.  If the problem still persists, you might want to ping the JTalert folks on that.

Good luck!

73, Scott

N3FJP

http://www.n3fjp.com

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...

-----Original Message-----
From: Amir K9CHP <sarlabs@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Mon, Jun 8, 2020 9:14 am
Subject: Re: [N3FJPSoftwareUsers] Power shows 0.1

Hi Scott,  

Unfortunately,  ACLog records 0.1 for power,  my rig can only do 5w at its lowest setting,  and I  have corrected the log entries manually,  which is time consuming,  tedious etc.  See the two pics below one showing my screen before I  logged the QSO and one showing the logged qso with 0.1 as power.  Note that none of the previous QSOs in the log had that power (all corrected manually) 

--

73 de Amir K9CHP

ARRL, Emergency Coordinator, Onondaga County, NY
Radio Amateurs of Greater Syracuse  www.ragsclub.org
Wilderness SAR www.wsar.org (ret.)
Eagle Valley Search Dogs www.evdogs.org (ret.)

On Mon, Jun 8, 2020, 05:28 Scott Davis via groups.io <SNKDavis=aol.com@groups.io> wrote:

Hi Amir,

Thanks for your e-mail.  AC Log defaults to the last power value entered.  Correct your most recent QSO record and then the next one will reflect that value.

Enjoy!

73, Scott

N3FJP

http://www.n3fjp.com

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...

-----Original Message-----
From: Amir K9CHP <sarlabs@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Sun, Jun 7, 2020 7:13 pm
Subject: [N3FJPSoftwareUsers] Power shows 0.1

Hi, 
New user. Yaesu FTDX101MP, running FT8, and using ACLog. Not using ACLog for rig control with FT8. When I log a QSO, using WSJT-X 2.2.0, the logging box contains the correct data, power etc. JT-ALERTS passes the data to ACLog but the power shown in ACLog is 0.1, which is definitely not what I used. Anyway to fix this? Maybe a setting I missed in ACLog? Thanks. 

-- 
No trees were killed in the sending of this message. However, a large number of electrons were terribly inconvenienced !

k9ij@...
Webmaster, Network Admin, Janitor

Hi Glenn,

Thanks for your e-mail.  That's actually a question for K1EL, the Winkeyer manufacturer.  He wrote the Winkeyer section of code that my software uses.

Enjoy!

73, Scott

N3FJP

http://www.n3fjp.com

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...

-----Original Message-----
From: Glenn AE0Q <ae0q@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Thu, Jun 4, 2020 10:32 pm
Subject: [N3FJPSoftwareUsers] WKUSB 31 embedded memory functions?

Is there a way to use the embedded memory functions of the WKUSB keyer with ACLog?

When I use the WKUSB 31 in standalone mode, I have my callsign programmed to insert a longer letter space after the first 2 characters.  I've been doing this for decades with my old CMOS 3 keyer, and it works great with the WKUSB using the /Inn command.  The A and E at the beginning of my call run together in normal spacing at higher speeds. Readability is improved by spacing them out a bit, but obviously not a word length or it wouldn't sound like a callsign.

What I can't get to work is inserting that spacing when programming memories with ACLog. 
Are the many embedded commands supposed to work from PC logging software?

Thanks - Glenn AE0Q

Thanks, Larry, I thought it was probably something simple! I am good now!

--Dennis NE6I