Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread David Gilbert
You're still wrong. It isn't at all a lack of ethics to use the software ... only to use the software for full automatic AND UNATTENDED operation.  It isn't unethical (or illegal) to use the software in full automatic mode if a licensed operator is in attendance ... it's only unethical to use

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread Neil Zampella
If that was the case, why is there a 'Auto QSO' box on the main screen, and on the Sourceforge site it still says: "Tool was previously known as WSJT-X xxx Full-Auto Mod" (xx removes the callsign) On 8/18/2019 9:26 PM, Ryan Tourge wrote: Well you are wrong. As it is released it doesn’t

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread Neil Zampella
I was planning to, considering that no one can see the lack of ethics in adding code to make an automatic QSO machine.   Using the fact that I called the software 'illegal' instead of looking at the fact that it can enable an illegal 'full auto' machine points that out. On 8/18/2019 10:03 PM,

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread David Gilbert
You're changing your story now.  Your previous messages simply said the software itself was illegal, and when I challenged that your argued the point and said I was rationalizing. Just give it up, OK? Dave   AB7E On 8/18/2019 6:12 PM, Neil Zampella wrote: By the software being 'illegal'

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread Ryan Tourge
Well you are wrong. As it is released it doesn’t have that ability. If someone byte bangs some hack to make it so then your skewed theory would make just about any ham radio software “illegal.” Ryan, N2YQT On Sun, Aug 18, 2019 at 9:19 PM Neil Zampella wrote: > By the software being 'illegal' I

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread Neil Zampella
By the software being 'illegal' I mean that it has the capability to allow an illegal act to be performed.  I agree, the use of such software is illegal, having the software is not, however, the mere fact that it does have the capability to be used as a bot for automatic, non-attended QSOs should

[wsjt-devel] Fwd: Welcome to the "wsjt-devel" mailing list

2019-08-18 Thread Christopher Diederich via wsjt-devel
I have been accepted to the list, but my posts keep getting rejected because I am a non-member. Am I doing something wrong? 73de K1LDOChris Diederich -- Forwarded message -- From: Date: Thu, Aug 15, 2019 at 11:19 AM -0400 Subjec

Re: [wsjt-devel] WSJT-X ver 2.1.0 spontaneous frequency changes

2019-08-18 Thread Andy Durbin
"What values are you using for Poll and Timeout in OmniRig?" The values were declared in my post. Here they are again - poll 250, timeout 1000, Baud 38,400. I used my station controller to generate a 'scope trigger when TS-590 data was not refreshed within 500 (later changed to 600 ms). I n

Re: [wsjt-devel] WSJT-X ver 2.1.0 spontaneous frequency changes

2019-08-18 Thread Andy Durbin
"May I suggest that WSJT-X should be desensitized from these transient OmniRig fault reports by only responding if they persist for x seconds. " I made a temporary change to my controller code to flag TS-590 data fail if either IF, or FA, or FB is not received for 500 ms. This configuration de

Re: [wsjt-devel] WSJT-X ver 2.1.0 spontaneous frequency changes

2019-08-18 Thread Hasan al-Basri
Andy, What values are you using for Poll and Timeout in OmniRig? I'm using 100 ms polling and 200 ms timeout. I ask because I have been having a problem with transmitting (with an external radio in FM mode when using SDRC's External Radio capability) I have played with the Polling and Timeout va

Re: [wsjt-devel] WSJT-X ver 2.1.0 spontaneous frequency changes

2019-08-18 Thread Andy Durbin
I have attempted to use WSJT-X ver 2.1.0 a few more times but continue to be plagued by rig control failure messages. I have found that WSJT-X rig control failures are associated with OmniRig Client declarations "Status: Rig not responding. However, OmniRig seems to issue these messages w

Re: [wsjt-devel] Crash report

2019-08-18 Thread Rick Drexel
Hi Jari, That’s useful information. Especially if it can be reproduced. It says that the DLL named Qt5Core caused an EXCEPTION_ACCESS_VIOLATION. (Exception Code: c005) Simply put, it tried to access a memory address it did not have permission to read or write. But that’s not helpful. Th

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread Jim Shorney
Well, yeah, that would be why I also referenced the definition of "Automatic Operation". 73 -Jim NU0C On Sat, 17 Aug 2019 14:03:16 -0700 Jim Preston wrote: > Under FCC rules, automatic control means not having a control operator > present at a control point. _

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread David Gilbert
No, the software by itself is not illegal.  The software is capable of unattended operation, but it isn't illegal unless it is used in that way. I can let someone who isn't licensed use my station while I am not even in the U.S., but neither I nor my station is performing an illegal act unle

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread Neil Zampella
The software in question is not the software we're referring to. I'm amazed at the reaction to what is an obvious circumvention of the original developers wishes, so much for ethics. Neil, KN3ILZ On 8/17/2019 5:21 PM, Andras Bato wrote: Hi Andy, Plese try to make QSOs using MSHV! (I am just us

Re: [wsjt-devel] Illegal auto mode?

2019-08-18 Thread Neil Zampella
"Man is not a rational animal, but a rationalizing one!" The program is designed to make QSOs without someone being there. Illegal in the US, the person who put the program together could have removed the code and left the UI.  He didn't, and added a 'legal notice' which is worth the paper it