Re: [wsjt-devel] WSJT-X 2.2.1 GA, Hamlib error with FTdx3000 and Microham II router
It sounds like you're trying to do port sharing. I'm don't believe the microham supports that. I believe it does support PTT on one com port and CAT on another. And it can also echo CAT responses to another COM port for monitoring...but not CAT control. So if you turn off N1MM and connect WSJT-X to COM4 it all works OK? What kind of rig do you have? There are solutions for having multiple programs (like N1MM and WSJT-X) sharing the rig. Mike On Wednesday, June 10, 2020, 08:06:38 AM CDT, Tom Ramberg via wsjt-devel wrote: First it happens when I set the Com port In the radio tab WSJT-X settings (in this case COM5) and press the "Test CAT" button. It turns red, and a pop up window appears with the message "Rig Failiure. Hamlib error: I/O error while opening connection to rig". See screenshot. If I ignore the message by pressing OK, The button turns green, and if I exit the settings and try to change bands, it seems to work okay. But then on a second try to press the "Test CAT" button, the second error message appears, saing "Hamlib error: Communication bus colision while trying to get the current VFO, se screenshot. On CAT1 (in this case COM4), I am connected to N1MM+. I have also tried to use Omnirig, but that just makes WSJT-X crash without any warning messages at all. Tom OH6VDA > 10. jun. 2020 kl. 12:44 skrev Bill Somerville : > > On 10/06/2020 07:45, Tom Ramberg via wsjt-devel wrote: >> Starting WSJT-X with FTdx3000 and using 2nd CAT port in MicroHams device >> router gives Hamlib error. >> >> de OH6VDA TOM > > Hi Tom, > > what is the full error message, including details, please? When does it > happen? > > 73 > Bill > G4WJS. > > > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X Menu problems
> > I have just updated to WSJT-X 2.2.1 and have a problem with some items on > the menu being in Spanish instead of English > > In preferences only the options at the bottom are Cancelar and Aceptar > everything else is OK > > On the main program heading under WSJT-X all items are in Spanish i.e > Acerta de WSJT-X, Preferencias,Servicios. Ocultar WSJT-X, Ocultar Otros, > Salir de WSJT-X. > > I am using an IMac with High Sierra 10.13.6 > > I have had no problems with any previous versions of the software > > Is this a known problem > > Look forward to hearing you comments > > John ROSE G3OGE > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wsjt-devel Digest, Vol 76, Issue 93
> Fine to learn how it should work, but here, there is always the same crash,
> even in 2.2.1, trying to decode FT8 on the air or from a wav file. In
> contrast, FT4 decodes well.
Claude,
Please try this change to line 48 in gen_ft8wave.f90 and let me know if it
fixes your problem:
$ git diff
diff --git a/lib/ft8/gen_ft8wave.f90 b/lib/ft8/gen_ft8wave.f90
index 02e7fdbd..9e277375 100644
--- a/lib/ft8/gen_ft8wave.f90
+++ b/lib/ft8/gen_ft8wave.f90
@@ -45,7 +45,7 @@ subroutine
gen_ft8wave(itone,nsym,nsps,bt,fsample,f0,cwave,wave,icmplx,nwave)
! Calculate and insert the audio waveform
phi=0.0
dphi = dphi + twopi*f0*dt !Shift frequency up by f0
- wave=0.
+ if(icmplx .eq. 0) wave=0.
if(icmplx .ne. 0) cwave=0. !Avoid writing to memory we may not have access to
call timer('gen_loop',0)
Steve k9an
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.1 GA, Hamlib error with FTdx3000 and Microham II router
On 10/06/2020 14:11, Bill Somerville wrote: On 10/06/2020 14:01, Tom Ramberg wrote: First it happens when I set the Com port In the radio tab WSJT-X settings (in this case COM5) and press the "Test CAT" button. It turns red, and a pop up window appears with the message "Rig Failiure. Hamlib error: I/O error while opening connection to rig". See screenshot. Hi Tom, is COM5 really the serial port of your rig,or do you have something else in between? 73 Bill G4WJS. Other than the microHAM uRouter and interface device. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.1 GA, Hamlib error with FTdx3000 and Microham II router
On 10/06/2020 14:01, Tom Ramberg wrote: First it happens when I set the Com port In the radio tab WSJT-X settings (in this case COM5) and press the "Test CAT" button. It turns red, and a pop up window appears with the message "Rig Failiure. Hamlib error: I/O error while opening connection to rig". See screenshot. Hi Tom, is COM5 really the serial port of your rig,or do you have something else in between? 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.1 GA Release
FLDigi and FLRig do not do anything close to what WSJT-X does with rig control.FLDigi does notSet VFOA freq/modeSet VFOB freq/modeSet SplitTransmit And it does it all within milliseconds. It's kind of like saying "The noise my car makes doesn't happen going less than 10MPH". Mike W9MDB On Wednesday, June 10, 2020, 05:00:53 AM CDT, Topher Petty wrote: I have only seen this behavior with WSJT-X, and only when changing bands via ci-v/cat. I have been unable to reproduce this in FLDigi or FLRig.SKCClogger only reads freq and does not provide for any form of rig control. 73 de AI8W, Chris On Wed, Jun 10, 2020, 00:06 Black Michael via wsjt-devel wrote: I was able to test with a friend that has an IC-7300 and we could duplicate this problem -- but it's not easily reproducible. Has nothing to do with WSJT-X or hamlib. Appears to be some sort of bug in the IC-7300 where changing bands and quickly transmitting is causing some sort of burp that turns on the preamp randomly Mike W9MDB On Sunday, June 7, 2020, 07:54:55 AM CDT, Topher Petty wrote: Bill:You seem to be under the impression that I run these programs simultaneously. Let me clear this up... I do not.I quit SKCCLogger when working in WSJT-X. I quit WSJT-X when working CW (and using SKCCLogger to log my contacts). FLDIGI only has its HAMlib rig control activated when I'm working PSK or RTTY, and I usually close SKCCLogger when I'm doing that, because I log THOSE contacts in FLDIGI. Both SKCCLogger and FLDIGI had issues reading and writing to the rig while WSJT-X 2.1.x was installed, EVEN THOUGH WSJT-X WAS NOT RUNNING AT THE TIME. Simply having WSJT-X 2.1.x installed meant that I had to play the "unplug the cable, plug it back in, start up FLRig, start [SKCCLogger|FLDIGI] close FLRig, cross fingers" game every time I wanted to utilize either of those programs. This is why I asked for a version that isn't statically linked.Again, I'm done, here. You're smarter than everyone in the room. Everything I assert is rubbish. You can figure it out, or not, at your convenience. I lost all desire to work with you when the insults started to fly. If I feel the desire to work FT8, I'll just put up with whatever odd symptoms exist, and restart udev/play the cable game every time I feel like switching to another mode, or logging a CW contact. de AI8W, Chris -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS/CM/CC/E/IT/TW d-@ s+:+ !a C++$@ UBLVSCX*(on)$>$ P++>$ L+++$ E+@ W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ b+>$ DI++ D+ G++ e h r+++ y+++ --END GEEK CODE BLOCK-- On Sun, Jun 7, 2020 at 8:38 AM Bill Somerville wrote: On 07/06/2020 13:27, Topher Petty wrote: > Better than a screenshot, I present to you my config file. > > This entire exchange has felt like the time when Yaesu called me > everything except a HAM radio operator because their bad sourcing of > finals in their FT-100Ds caused repeated failures of the final > amplifier ICs. I never did get my money back, or an apology from Yaesu > for their "customer service" personnel's behavior both on the > telephone and in email, and they lost a customer for life because of it. > > So, rather than being accused of spreading more rubbish, this will be > my last communication regarding this on this list. My email address is > good on QRZ if you need any more information. > > 73 de AI8W, Chris Chris, does SKCCLogger emulate the Hamlib rigctld rig server, I ask because it appears to be talking directly to the rig. That would mean that no other application could get CAT control of the rig due to the serial port being unavailable. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Terminal output for Wayland users
On 10/06/2020 13:23, Richard Shaw wrote: It doesn't seem to cause a problem (unlike on MythTv, which I also maintain), but a user reported the following terminal output when running 2.1.2: "qt.qpa.wayland: Wayland does not support QWindow::requestActivate()" Thanks, Richard KF5OIM Hi Richard, we don't call that directly, probably inside some widget function implementation. It might mean the facility to bring the WSJT-X window to the front when an incoming UDP Message Protocol request has been accepted will not work. You could test message_aggregator to send a message to a WSJT-X instance. If it did work that way then that would be stealing keyboard focus which is not desirable, and I didn't think we did that anyway. It may just be Wayland noting that if we were to call QWindow::requestActivate() then it would not comply. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Terminal output for Wayland users
It doesn't seem to cause a problem (unlike on MythTv, which I also maintain), but a user reported the following terminal output when running 2.1.2: "qt.qpa.wayland: Wayland does not support QWindow::requestActivate()" Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.1 GA Release
I have only seen this behavior with WSJT-X, and only when changing bands via ci-v/cat. I have been unable to reproduce this in FLDigi or FLRig. SKCClogger only reads freq and does not provide for any form of rig control. 73 de AI8W, Chris On Wed, Jun 10, 2020, 00:06 Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I was able to test with a friend that has an IC-7300 and we could > duplicate this problem -- but it's not easily reproducible. > > Has nothing to do with WSJT-X or hamlib. Appears to be some sort of bug > in the IC-7300 where changing bands and quickly transmitting is causing > some sort of burp that turns on the preamp randomly > > Mike W9MDB > > > On Sunday, June 7, 2020, 07:54:55 AM CDT, Topher Petty > wrote: > > > Bill: > You seem to be under the impression that I run these programs > simultaneously. Let me clear this up... > I do not. > I quit SKCCLogger when working in WSJT-X. I quit WSJT-X when working CW > (and using SKCCLogger to log my contacts). FLDIGI only has its HAMlib rig > control activated when I'm working PSK or RTTY, and I usually close > SKCCLogger when I'm doing that, because I log THOSE contacts in FLDIGI. > Both SKCCLogger and FLDIGI had issues reading and writing to the rig while > WSJT-X 2.1.x was installed, EVEN THOUGH WSJT-X WAS NOT RUNNING AT THE TIME. > Simply having WSJT-X 2.1.x installed meant that I had to play the "unplug > the cable, plug it back in, start up FLRig, start [SKCCLogger|FLDIGI] close > FLRig, cross fingers" game every time I wanted to utilize either of those > programs. > This is why I asked for a version that isn't statically linked. > Again, I'm done, here. You're smarter than everyone in the room. > Everything I assert is rubbish. You can figure it out, or not, at > your convenience. I lost all desire to work with you when the insults > started to fly. If I feel the desire to work FT8, I'll just put up with > whatever odd symptoms exist, and restart udev/play the cable game every > time I feel like switching to another mode, or logging a CW contact. > > de AI8W, Chris > > -BEGIN GEEK CODE BLOCK- > Version: 3.1 > GCS/CM/CC/E/IT/TW d-@ s+:+ !a C++$@ UBLVSCX*(on)$>$ P++>$ L+++$ E+@ > W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ > b+>$ DI++ D+ G++ e h r+++ y+++ > --END GEEK CODE BLOCK-- > > > On Sun, Jun 7, 2020 at 8:38 AM Bill Somerville > wrote: > > On 07/06/2020 13:27, Topher Petty wrote: > > Better than a screenshot, I present to you my config file. > > > > This entire exchange has felt like the time when Yaesu called me > > everything except a HAM radio operator because their bad sourcing of > > finals in their FT-100Ds caused repeated failures of the final > > amplifier ICs. I never did get my money back, or an apology from Yaesu > > for their "customer service" personnel's behavior both on the > > telephone and in email, and they lost a customer for life because of it. > > > > So, rather than being accused of spreading more rubbish, this will be > > my last communication regarding this on this list. My email address is > > good on QRZ if you need any more information. > > > > 73 de AI8W, Chris > > Chris, > > does SKCCLogger emulate the Hamlib rigctld rig server, I ask because it > appears to be talking directly to the rig. That would mean that no other > application could get CAT control of the rig due to the serial port > being unavailable. > > 73 > Bill > G4WJS. > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.1 GA, Hamlib error with FTdx3000 and Microham II router
On 10/06/2020 07:45, Tom Ramberg via wsjt-devel wrote: Starting WSJT-X with FTdx3000 and using 2nd CAT port in MicroHams device router gives Hamlib error. de OH6VDA TOM Hi Tom, what is the full error message, including details, please? When does it happen? 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X 2.2.1 GA, Hamlib error with FTdx3000 and Microham II router
Starting WSJT-X with FTdx3000 and using 2nd CAT port in MicroHams device router gives Hamlib error. de OH6VDA TOM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wsjt-devel Digest, Vol 76, Issue 93
On 6/9/20 3:39 PM, Steven Franke via wsjt-devel wrote: Hi Steven, Using a 2.2.x version, decoding on a busy band has the following behavior: first decode in cycle picks up a few messages, second decode a few, then the third decode runs a long time (well into the next cycle) and the majority of messages get decoded on that third decode. What are your typical DT values, i.e. what is the median DT value for a cycle that has a good number of decodes? Normally, we expect to see the bulk of the decodes produced by the first decoding segment (say, 80%) and only a small number of decodes produced during the third segment. However, if there is significant receiver latency, this can push most of the decodes into the third segment. FWIW, no decoding is done during the second decode segment. This segment is used to subtract all of the decodes that were obtained during the first segment. Fine to learn how it should work, but here, there is always the same crash, even in 2.2.1, trying to decode FT8 on the air or from a wav file. In contrast, FT4 decodes well. Program received signal SIGSEGV, Segmentation fault. 0x080bed38 in gen_ft8wave (itone=..., nsym=79, nsps=1920, bt=2, fsample=12000, f0=0, cwave=is more than max-value-size>, wave=more than max-value-size>, icmplx=1, nwave=151680) at /home/claude/ham/JoeTaylor/wsjtx/lib/ft8/gen_ft8wave.f90:48 48wave=0. type = integer(kind=4) (79) type = complex(kind=4) (151680) type = real(kind=4) (151680) value requires 606720 bytes, which is more than max-value-size value requires 1213440 bytes, which is more than max-value-size #0 0x080bed38 in gen_ft8wave (itone=..., nsym=79, nsps=1920, bt=2, fsample=12000, f0=0, cwave=is more than max-value-size>, wave=more than max-value-size>, icmplx=1, nwave=151680) at /home/claude/ham/JoeTaylor/wsjtx/lib/ft8/gen_ft8wave.f90:48 #1 0x0809ef9d in subtractft8 ( dd0=more than max-value-size>, itone=0x0>, f0=0, dt=0, lrefinedt=0x0>) at /home/claude/ham/JoeTaylor/wsjtx/lib/ft8/subtractft8.f90:45 #2 0x in ?? () Best wishes and stay@Ω ! Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
