I'm on that frequency, but with a poor antenna. I try to receive.
toggle quoted message
Show quoted text
Nothing until now. Pietro I2OIM Il giorno mer 25 mag 2022 alle ore 14:12 James Buie <ars.kn4flo@...> ha scritto: 05/25/2022 12:09 UTC Today I will be using JT9-10F and JT9-10G. I will |
|
Locked
Use of hardware com port 1 causes WSJT-X to throw and error...
#wsjt-x-crashing
NO9B
Good Day:
I didn't see a solution for this topic. I have tried using PSTRotator and DXSuite-DXView to control my rotor using COM port 1 which is a DB9 on the back of the computer, the radio is an IC7300 plugged in using the USB cable. If I bring up the rotor program and command it to move the rotor WSJT-X will crash asking me to reconnect which I cannot. The only way I can get WSJT-X to connect to the radio again is to reboot the computer. Killing the offending program doesn't help. Suggestions? Thanks Steve |
|
Ken
Hi Dave,
toggle quoted message
Show quoted text
These settings work for me. I start WSJT-X first, then JTAlert, and N3FJP ACLog last. I've used this setup to log WSJT-X FT4 and FT8 QSO's directly into N3FJP ACLog for several years now. One PC uses Windows 7 and the other PC uses Windows 10. Both work fine. YMMV ! Ken - W8KEN On 5/24/2022 1:55 AM, David Tucker wrote:
I can't get WSJT-x and ACLOG to log qso's. I have tried in JT alert to manual log or auto log.. Neither seems to work. I have tried both API settings in ACLOG . Any help would be appreciated. |
|
Jim Brown
Why is this on the reflector rather than direct email?
toggle quoted message
Show quoted text
73, Jim K9YC On 5/24/2022 7:33 AM, James Buie wrote:
Thank You Bobby, N4AU. KN4FLO, 73. |
|
Marvin Ross
Dave,
Have you check out this article by Scott at N3FJP/ACLog? https://n3fjp.com/help/wsjt-x-integration-with-n3fjp-software.html Marv W0PSY |
|
Randy Buxton, W4IFI
Here's my setup
WSJT-X: Under Logging,,, check the boxes for Prompt me to log QSO, dB reports to comments, Clear DX call and grid after logging Under Network Services,,,check the box for Enable PSK Reporter Spotting Under UDP Server,,,,, UDP Server = 224.0.0.1 UDP Server port number 2237 Outgoing interfaces,,,,Drop down and check all boxes Multicast TTL = 1 Check all boxes to the right N3FJP: Settings>Rig Interface>=None>Done Settings>API>Check the box for TCP API Enabled (Server),,,,Port = 2237 Check the box for Listen for WSJT-X Check done That's it. -Randy, W4IFI |
|
Robert44
One more question, when I try to open the wsjtx_log.adi file where (I think) my new logs are stored I get a message that my MacBook Pro does not have software to open the file. I then got directed to the Apple App Store and I downloaded some recommended software that has nothing to do with opening this .adi file. Does this sound right? How can I open this file? Many thanks!
Rober KI5TPC |
|
Randy Buxton, W4IFI
Dave,
Here's my setup. ACLog: Settings>Rig Interface>Select Rig=None Settings>API>TCP API Enabled (Server) [Check the box],,,Port=2237 Under WSJT-X Interface check the box for Listen for WSJT-X Click Done WSJT-X: File>Settings>Reporting Under Logging- Check only the boxes for Prompt me to log QSO, dB reports to comments, Clear DX call and grid after logging Under Network Services- Check the box for Enable PSK Reporter Spotting (not necessary but I do it anyway) Under UDP Server: UDP Server = 224.0.0.1 UDP Server port number = 2237 Outgoing interfaces, click the dropdown and check all the boxes Multicast TTL = 1 Check all three boxes to the right Click OK and that 's it. -Randy Buxton, W4IFI |
|
Bob Hardwick
I have ACL and WSJT-X working. Just go to the N3FJP website the instructions work fine. Also ACLOG must be running for it to work.
toggle quoted message
Show quoted text
Bob WA6NFJ On 23-May-22 10:55 PM, David Tucker wrote:
I can't get WSJT-x and ACLOG to log qso's. I have tried in JT alert to manual log or auto log.. Neither seems to work. I have tried both API settings in ACLOG . Any help would be appreciated. |
|
neil_zampella <neilz@...>
I see you posted to the hamapps.groups.io support group.
toggle quoted message
Show quoted text
That's the best place to get assistance for JTAlert. Neil, KN3ILZ On 5/24/2022 12:55 AM, David Tucker wrote:
I can't get WSJT-x and ACLOG to log qso's. I have tried in JT alert to manual log or auto log.. Neither seems to work. I have tried both API settings in ACLOG . Any help would be appreciated. |
|
Reino Talarmo
Hi Terry
As Mike told he needs to know more about CAT-control related issues as the error message is generated with a low power and related to SWR measurement. We may need to know how SWR measurement is actually done. I assume that you are using IC-705 for that. Some comments inline. I am testing to a telescopic vertical mounted on a three plate mag mount on a 1/2 sq metre of steel with some 15ft radials hanging vertically. I was running at 1% power.The power is so low that it is not the RFI reason, if system fails only on the SWR measurement. You said "radials hanging vertically". Is your 1/2 sq metre steel in an elevated location and are those radials hanging close to the feedline? You did not mentioned any current balun, have you got one at the feedpoint? It may not be needed, if you can make QSOs using a higher power. HOWEVER, as I went back to the setup to see if I could find other error messages, I unplugged and then reconnected the usb cable (which has ferrites) and it now appears to be fine. I can still create that error if I go to the swr option on the 705 and use wsjt-x to tune. The tx locks up in transmit and won't die unless I get drastic and pull the power/usb or go into settings and press test cat and test ptt then test cat again which breaks the ptt. So I am guessing that hamlib doesn't like wsjt-x running the IC-705 swr test.It seems that SWR measurement for some still mysterious reason uses VFOB in a manner that is not supported in IC-705 and Hamlib combination. Do you have selected in wsjt-x IC-705 as the rig or do you use rigctld? 73, Reino OH3mA |
|
Michael Black
I need to know if you are using rigctld.
toggle quoted message
Show quoted text
I see in your message that it's trying to switch to VFOB and that should only be if you are running rigctld without the --vfo option.It appears the 705 doesn't like the SWR mode and VFOB. Mike W9MDB On Tuesday, May 24, 2022, 02:19:31 PM CDT, groups.io@... <groups.io@...> wrote:
Thanks Reino. So your rx is fine and tx starts transmitting and lose connection to your rig. Do you get an error message? Do you use CAT control for PTT?Yes, to your first question, error message uploaded, Yes to CAT control. The real reason could be RFI in sack. The first question is usually what kind antenna you are using? Is it an unbalanced antenna without a current balun in a proper location, usually at the feed point? If the failure is repeatable, does a lower output power helps?I am testing to a telescopic vertical mounted on a three plate mag mount on a 1/2 sq metre of steel with some 15ft radials hanging vertically. I was running at 1% power. HOWEVER, as I went back to the setup to see if I could find other error messages, I unplugged and then reconnected the usb cable (which has ferrites) and it now appears to be fine. I can still create that error if I go to the swr option on the 705 and use wsjt-x to tune. The tx locks up in transmit and won't die unless I get drastic and pull the power/usb or go into settings and press test cat and test ptt then test cat again which breaks the ptt. So I am guessing that hamlib doesn't like wsjt-x running the IC-705 swr test. I hope that makes sense guys. Thanks again for your help Reino, |Chuck & Michael, it is appreciated, but I hope that I can leave you alone for now. 73 de Terry |
|
Hello Hisami, 7L4IOU. That video was nice to see. I enjoyed it. I will no longer be testing the JT9 Fast Submodes. Instead I will be using them periodically and hope others will join in as well. TNX, KN4FLO, James, 73.
|
|
groups.io@...
Thanks Reino.
So your rx is fine and tx starts transmitting and lose connection to your rig. Do you get an error message? Do you use CAT control for PTT?Yes, to your first question, error message uploaded, Yes to CAT control. The real reason could be RFI in sack. The first question is usually what kind antenna you are using? Is it an unbalanced antenna without a current balun in a proper location, usually at the feed point? If the failure is repeatable, does a lower output power helps?I am testing to a telescopic vertical mounted on a three plate mag mount on a 1/2 sq metre of steel with some 15ft radials hanging vertically. I was running at 1% power. HOWEVER, as I went back to the setup to see if I could find other error messages, I unplugged and then reconnected the usb cable (which has ferrites) and it now appears to be fine. I can still create that error if I go to the swr option on the 705 and use wsjt-x to tune. The tx locks up in transmit and won't die unless I get drastic and pull the power/usb or go into settings and press test cat and test ptt then test cat again which breaks the ptt. So I am guessing that hamlib doesn't like wsjt-x running the IC-705 swr test. I hope that makes sense guys. Thanks again for your help Reino, |Chuck & Michael, it is appreciated, but I hope that I can leave you alone for now. 73 de Terry |
|
hisami dejima
Hi James-san and All
Had you seen the K2MO's nice video for MS by JT9G? "10 Meter Meteor Scatter QSO" https://www.youtube.com/watch?v=y-C8XMhgkF4 I still hoping to try, but haven't had a chance. 73, Hisami 7L4IOU |
|
Chuck Gelm
On 5/24/22 13:46, groups.io@... wrote:
I had upgraded the IC-705 to 1.27.When? Before or after https://wsjtx.groups.io/g/main/message/34626 ? 73, Chuck |
|
Michael Black
That doesn't sound like RFI to me.
toggle quoted message
Show quoted text
Something is trying to set_vfo. Are you using rigctld? If so please use the --vfo option. Mike W9MDB On Tuesday, May 24, 2022, 01:17:11 PM CDT, Reino Talarmo <reino.talarmo@...> wrote:
Hi Terry, With my limited knowledge on Hamlib errors I still consider that it is RFI. When you are moving and thatching rig to measure SWR you changed a bit RFI current in CAT control connection. Mark W9MDB may confirm this. You did not answered questions that could explain potential RFI situation. 73, Reino OH3mA Original mail: Thanks all for coming back. I fired up the radio this evening and all looked fine and TUNE seemed ok, but then I was checking the swr and : --------------------------- WSJT-X - IC705 --------------------------- Rig failure --------------------------- Hamlib error: Command rejected by the rig rig_set_vfo: return -9, vfo=VFOB, curr_vfo=VFOA rig_set_vfo: elapsed=5ms rig.c(2503):rig_set_vfo return(-9) Command rejected by the rig rig_set_vfo: return -9, vfo=VFOB, curr_vfo=VFOA rig_set_vfo: elapsed=5ms rig_set_vfo: elapsed=5ms while exchanging VFOs --------------------------- OK --------------------------- I agree that Windows© updates are often a problem, but not this time. I had upgraded the IC-705 to 1.27. |
|
Reino Talarmo
Hi Terry,
With my limited knowledge on Hamlib errors I still consider that it is RFI. When you are moving and thatching rig to measure SWR you changed a bit RFI current in CAT control connection. Mark W9MDB may confirm this. You did not answered questions that could explain potential RFI situation. 73, Reino OH3mA Original mail: Thanks all for coming back. I fired up the radio this evening and all looked fine and TUNE seemed ok, but then I was checking the swr and : --------------------------- WSJT-X - IC705 --------------------------- Rig failure --------------------------- Hamlib error: Command rejected by the rig rig_set_vfo: return -9, vfo=VFOB, curr_vfo=VFOA rig_set_vfo: elapsed=5ms rig.c(2503):rig_set_vfo return(-9) Command rejected by the rig rig_set_vfo: return -9, vfo=VFOB, curr_vfo=VFOA rig_set_vfo: elapsed=5ms rig_set_vfo: elapsed=5ms while exchanging VFOs --------------------------- OK --------------------------- I agree that Windows© updates are often a problem, but not this time. I had upgraded the IC-705 to 1.27. |
|
groups.io@...
Thanks all for coming back. I fired up the radio this evening and all looked fine and TUNE seemed ok, but then I was checking the swr and :
--------------------------- WSJT-X - IC705 --------------------------- Rig failure --------------------------- Hamlib error: Command rejected by the rig rig_set_vfo: return -9, vfo=VFOB, curr_vfo=VFOA rig_set_vfo: elapsed=5ms rig.c(2503):rig_set_vfo return(-9) Command rejected by the rig rig_set_vfo: return -9, vfo=VFOB, curr_vfo=VFOA rig_set_vfo: elapsed=5ms rig_set_vfo: elapsed=5ms while exchanging VFOs --------------------------- OK --------------------------- I agree that Windows© updates are often a problem, but not this time. I had upgraded the IC-705 to 1.27. |
|
05/24/2022 17:20 UTC. I have decided that this concludes the testing of the JT9-10G testing and all other testing that has been completed today. Thank You and I appreciate it. KN4FLO, James, 73.
|
|