Date   

Re: VARA P2P NOW AVAILABLE !

 

Andy, did you get P2P VARA working?

Ted


On 3/7/2018 12:01 PM, Andrew OBrien wrote:
although, I am getting the following error when Winlink Express tries to conenct with VARA software

*** Launching VARA TNC
Could not connect to VARA Command Port 8301  Connection failed: No connection could be made because the target machine actively refused it 127.0.0.1:8301
*** Failure to open Command Port 8301 to Vara TNC.
Check and make sure port is unused.

I have tried 8300, 8310, same result.

Andy K3UK


Virus-free. www.avg.com


Re: VARA P2P NOW AVAILABLE !

Andrew OBrien
 

although, I am getting the following error when Winlink Express tries to conenct with VARA software

*** Launching VARA TNC
Could not connect to VARA Command Port 8301  Connection failed: No connection could be made because the target machine actively refused it 127.0.0.1:8301
*** Failure to open Command Port 8301 to Vara TNC.
Check and make sure port is unused.

I have tried 8300, 8310, same result.

Andy K3UK


VARA P2P NOW AVAILABLE !

Andrew OBrien
 

VARA peer to peer is now possible when using Winlink Express, latest version.

Andy K3UK


ARIM Messaging Program v1.5

Bob NW8L
 

Hello,
 
ARIM v1.5 is available for download:
 
https://www.whitemesa.net/arim/arim.html#inst
 
Fix bug, refine "channel busy" functionality.
 
Details in change log excerpt below.
 
Special thanks to Doug WB6VAC for help in beta testing.
 
Files are also available at the ardop applications Files area at
groups.io:
 
https://ardop.groups.io/g/applications/files
 
and in the Files area at the arim-ham Yahoo group:
 
https://groups.yahoo.com/neo/groups/arim-ham/files
 
Station NW8L will be on dial 14.066 in daytime, 7.101 at night and
sometimes 10.131 for a while in-between, for testing.
 
73, Bob NW8L
 
v1.5  06Mar2018
---------------
1. Fix bug where ARIM's busy state not reset when detaching from TNC,
   which prevented attempts to initiate a new operation if ARIM's
   busy state was TRUE at the time.
2. Force reset of ARIM's busy state when the ESC key is pressed.
   ARIM depends on notifications from the TNC which indicate the state
   of the TNC's busy detector. In some cases, ARIM may not receive a
   BUSY FALSE notification when one is expected. This can leave ARIM
   stuck in the [RF CHANNEL BUSY] state, and attempts to start a new
   operation will fail. If this happens, the operator can recover by
   pressing the <ESC> key to reset ARIM's busy state.
3. Remove delay in changing ARIM busy state after receiving BUSY FALSE
   notification from TNC.
4. Update embedded Help and PDF Help file.


Re: Vara Large File Transfer Video via NVIS

Jeremy Allen
 

I'm interested to see tests with S/N ratios in the range of 2-10 dB.  With so many tones and a relatively wide bandwidth, I worry about the viability of the link at low ends of the propagation spectrum.  Most of the ARQ modes do really well over 10 dB, but the true test is when S/N is in the single digits and there is high phase dispersion.

As an aside, VARA is taking a line from Clover's playbook by using the most robust mode to maintain the link.

73
N1ZZZ


Re: FSK4/13

Steinar LA5VNA
 

OK, we tried ;)

S LA5VNA


On 06.03.2018 22:01, Sholto Fisher wrote:
Nothing copied Steinar


Re: Monitoring VARA

Graham
 

Thank's Trevor ,  perhaps reached the  same  , by differing  paths . 

The  next version of  VARA , will  have  a  selectable  CW  identification , which would  appear to follow the  consensus as to  station  ID 

Though, I am minded, Where  as  CW is  universally  permitted,  from the link,  119-b-[3] , there is a  mode continuity requirement , in terms of
station ID. 

73-G,


Re: FSK4/13

Sholto Fisher
 

Nothing copied Steinar


Re: FSK4/13

Steinar LA5VNA
 

Send CQ now

LA5VNA S

On 06.03.2018 21:52, Steinar Aanesland wrote:
Using a small beam and 500w pointing west

I will run a beacon for a few minutes.

LA5VNA S





On 06.03.2018 21:46, Sholto Fisher wrote:
Hi Steinar,

I'm pretty sure we have no path at any hour but I am also on 14.103 usb dial with a center of 1500hz.

I see that you can select the speed and shift of this mode from the menu. Looks like the default is 25 baud with a 50hz shift between carriers.

73

Sholto
K7TMG


Re: FSK4/13

Steinar LA5VNA
 

Using a small beam and 500w pointing west

I will run a beacon for a few minutes.

LA5VNA S

On 06.03.2018 21:46, Sholto Fisher wrote:
Hi Steinar,

I'm pretty sure we have no path at any hour but I am also on 14.103 usb dial with a center of 1500hz.

I see that you can select the speed and shift of this mode from the menu. Looks like the default is 25 baud with a 50hz shift between carriers.

73

Sholto
K7TMG


Re: FSK4/13

Sholto Fisher
 

Hi Steinar,

I'm pretty sure we have no path at any hour but I am also on 14.103 usb dial with a center of 1500hz.

I see that you can select the speed and shift of this mode from the menu. Looks like the default is 25 baud with a 50hz shift between carriers.

73

Sholto
K7TMG


Re: FSK4/13

Steinar LA5VNA
 

I am qrv on 14.103 dial freq, but from Norway..

LA5VNA S



On 06.03.2018 21:15, Sholto Fisher wrote:
I don't like replying to my own messages but I don't think I made the first post clear.

The new beta of TrueTTY has two new modes FSK4/13 and FSK4/9.
http://www.dxsoft.com/en/products/truetty/

There isn't a lot of info in the history file but FSK4/13 sound intriguing:
"Experimental mode FSK4/13 was made. This mode uses 13-bit symbols with minimal code distance 4, so all single and some double errors can be fixed"

Anybody want to give it a shot?

73

Sholto
K7TMG


Re: FSK4/13

Sholto Fisher
 

I don't like replying to my own messages but I don't think I made the first post clear.

The new beta of TrueTTY has two new modes FSK4/13 and FSK4/9.
http://www.dxsoft.com/en/products/truetty/

There isn't a lot of info in the history file but FSK4/13 sound intriguing:
"Experimental mode FSK4/13 was made. This mode uses 13-bit symbols with minimal code distance 4, so all single and some double errors can be fixed"

Anybody want to give it a shot?

73

Sholto
K7TMG


Re: No sign of VARA gateways

KC9SGV
 

The KC9SGV VARA testing station is up on the air again on 7.101 MHz USB.
Also running Winmor 1600 on the same frequency.

Please test both modes with about 5k files to compare thruput.

Bernie,
KC9SGV
Chicago.


Re: Monitoring VARA

M5AKA
 

"if the  section  is  defined  as  ''data''  then  using a  CW   ID  is  not to the  word of the  regulation's"

Graham, US amateurs can, if they really want to, ID in CW as well the mode they are using. The FCC don't prohibit it, CW is permitted everywhere, see §97.305 Authorized emission types:

(a) Except as specified elsewhere in this part, an amateur station may transmit a CW emission on any frequency authorized to the control operator.


73 Trevor M5AKA



On Tuesday, 6 March 2018, 17:19, Graham <g0nbd@...> wrote:



Tnx Walter  

Ok....That's the  codes  and  cypher clause ,  as every one  can  download the  same  software , that  get's round  the  issue of 'obscurement' ...  so  far so  good , not aimed at disclosure of the source  code , that's  under  IP rites etc 

However , in the  link Trevor  provided , there  may be a  catch ,   

If I'm  correct,  the  part97  defines as to  which  modes  and  emissions  may be  used in  what  part of the  bands ,  if the  section  is  defined  as  ''data''  then  using a  CW   ID  is  not to the  word of the  regulation's ?   ''emission authorized for the transmitting channel''

''The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:''

Would  that  imply  ID to  be a DATA  transmission ''only''  in a data  section  of the  band ???

Tnx -G,




Virus-free. www.avg.com


Re: No sign of VARA gateways

Graham
 

Andy,

That sounds like a  good  use  for the  Opera  beacon ,  that  will  give  you a  single  pass   s/n in 2.4 Khz b/w  and   %  data loss , as the  % fade , Its actually  designed  as  a  engineering tool,  to  provide  path  data  .

The  s/n  readings  are  accurate, so you  can  scale up  , if  1  watt gives  you  , say  -10 db  s/n , then you  would need  10 watts  to reach 0 dB  s/n  and  most likely  100  watts  to  establish a  VARA link over the  path ,  OFDM  needing  about  x 10 power of  MFSK 

73-Graham
G0NBD


Re: Monitoring VARA

Graham
 


Tnx Walter  

Ok....That's the  codes  and  cypher clause ,  as every one  can  download the  same  software , that  get's round  the  issue of 'obscurement' ...  so  far so  good , not aimed at disclosure of the source  code , that's  under  IP rites etc 

However , in the  link Trevor  provided , there  may be a  catch ,   

If I'm  correct,  the  part97  defines as to  which  modes  and  emissions  may be  used in  what  part of the  bands ,  if the  section  is  defined  as  ''data''  then  using a  CW   ID  is  not to the  word of the  regulation's ?   ''emission authorized for the transmitting channel''

''The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:''

Would  that  imply  ID to  be a DATA  transmission ''only''  in a data  section  of the  band ???

Tnx -G,


Re: Monitoring VARA

Sholto Fisher
 

Trevor,

I don't think an ID sent in a mode (without the possibility of reasonably being able to monitor it) is in the spirit of Part 97 even if you insist it is fully complying with the regulations. I can easily imagine the FCC would turn this argument on its head and suggest that if you are unable to ID a particular mode then it is up to the operator to decide its legality under Part 97 and whether or not to use it.

It just seems common sense to me that authors of digital modes (to be used in the Amateur service) would ensure an easy method of monitoring transmissions.

I am fully aware that CW IDs are not legal requirements but it seems reasonable that if there is no chance of identifying a transmission using the software itself a CW ID does makes sense.

73

Sholto
K7TMG


Re: Monitoring VARA

M5AKA
 

Graham, the latest version of § 97.119 Station identification is at


73 Trevor M5AKA


On Tuesday, 6 March 2018, 16:26, Graham <g0nbd@...> wrote:


Andy / Sholto, 

Is it possible  for  some  one to  quote the  actual  wording  part97 requirement ?
is this the  same  for  all  bands and or  sub-bands  etc ?

Need  the ID be in the  same  mode that  is  being  used ,  or  part of therein ?

Tnx-Graham.





Virus-free. www.avg.com


Re: Monitoring VARA

M5AKA
 

I feel it unlikely FCC would take a dim view of someone fully complying with the Part 97 ID requirement.

In your earlier post you can the impression CW IDs were "legal" requirements, they are not.

But if someone really wants to add an extra ID in CW to all their digital transmissions then they can, even though it in unnecessary.

73 Trevor M5AKA



Virus-free. www.avg.com

On Tuesday, 6 March 2018, 15:55, Sholto Fisher <sholto.fisher@...> wrote:


Hi Trevor,

I'm aware that IDs can be done in the mode itself but if there's no way of monitoring the ID I'm sure the FCC would take a dim view of it.
After all what's the point of an ID if there is no ready method to observe it? Shouldn't be a problem though if there's going to be a CW ID in the software.

Going back to Andy's point, during long Pactor message transfers (like a WX fax) does the Winlink software ID every 10 minutes for both the RMS and client? I always assumed it did but now I'm not sure.

I'm fairly sure it does in WinMOR.

73

Sholto
K7TMG


1241 - 1260 of 51633