Date   

Re: What is "sound" used for in APRSIS32?

Greg Depew
 

I believe sound is the dings etc when you have windows sound turned on and you receive a message or have a port error. 



Greg KB3KBR Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: "'Fred Hillhouse' fmhillhouse@... [aprsisce]"
Date: 5/27/19 19:41 (GMT-05:00)
To: aprsisce@...
Subject: RE: [aprsisce] What is "sound" used for in APRSIS32?

 

Sound doesn’t seem to do much of anything. At least I have never found anything.

 

Fred N7FMH

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Monday, May 27, 2019 1:57 PM
To: aprsisce@...
Subject: [aprsisce] What is "sound" used for in APRSIS32?

 

 

Per the subject but specifically does APRSIS32 have the capability to synthetically voice spots or more importantly messages (such as in UI-View or
Xastir) - great for keeping eyes on the road while still monitoring selected APRS traffic and messages.    Thanks - Gord VE1AJF-9

 


Virus-free. www.avast.com


Re: What is "sound" used for in APRSIS32?

Fred Hillhouse
 

Sound doesn’t seem to do much of anything. At least I have never found anything.

 

Fred N7FMH

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Monday, May 27, 2019 1:57 PM
To: aprsisce@...
Subject: [aprsisce] What is "sound" used for in APRSIS32?

 

 

Per the subject but specifically does APRSIS32 have the capability to synthetically voice spots or more importantly messages (such as in UI-View or
Xastir) - great for keeping eyes on the road while still monitoring selected APRS traffic and messages.    Thanks - Gord VE1AJF-9

 


Virus-free. www.avast.com


Passcode Request

Frank Kostelac
 

Request Pas Code for APRSISCE/32

Thanks

Frank / N7ZEV



Re: What is "sound" used for in APRSIS32?

Lynn Deffenbaugh
 

Negative.  Sorry.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 5/27/2019 1:56 PM, gskiffing@... [aprsisce] wrote:
Per the subject but specifically does APRSIS32 have the capability to synthetically voice spots or more importantly messages (such as in UI-View or
Xastir) - great for keeping eyes on the road while still monitoring selected APRS traffic and messages.    Thanks - Gord VE1AJF-9



What is "sound" used for in APRSIS32?

Gordon Skiffington
 

Per the subject but specifically does APRSIS32 have the capability to synthetically voice spots or more importantly messages (such as in UI-View or
Xastir) - great for keeping eyes on the road while still monitoring selected APRS traffic and messages.    Thanks - Gord VE1AJF-9



Re: Multiple Instances of APRSIS?

WH6FQE
 

Rob,

I have no idea what happened. The only way I could bring the Tracker back into KISS mode was to shut APRSIS down and reattach the Tracker to BPQ32 which brought it into KISS mode, then shut BPQ32 back down and bring APRSIS back up. It stayed in KISS mode until I went into the Configure/Ports/SatGate screen and unchecked the Beacons box. When I did that, it took it back out of KISS mode and I had to go back through the BPQ32 process again to put it back into KISS mode.

For some reason, APRSIS will not put it into KISS mode when it starts up but BPQ32 will.

The Quiet Time is set to 0 and the port is Simply(KISS).

It shows to be in KISS mode now, however, it also shows to be Receive Only and will not transmit anymore.

RC
WH6FQE


Re: Multiple Instances of APRSIS?

Rob Giuliano
 

Filters don't do anything to the port - as far as sending commands, so if isn't the filter.

Are you sure your TNC is set to remain in KISS mode over power cyvce/reset and you are using a Simply(KISS) port?
  That, truly is thd best method.

Check you port settings for "Quiet Time".  If your not a Simply(KISS) port, It could be that a period of inactivity on the port is sending the Close/Open commands and reseeting the port.
  Of course Simply(KISS) has those cleared out.

Try Quiet Time zero.


On Sun, May 26, 2019 at 0:10, wh6fqe@... [aprsisce]
wrote:
 

Ok, not sure what happened now. I found the wiki page where it showed to add the filter:


b/RS0ISS*/W3ADO-1/ARISS d/RS0ISS*/W3ADO-1/ARISS

Yet once I added this, it kicked my SCS Tracker back out of KISS mode. What the heck?


RC
WH6FQE


Re: Multiple Instances of APRSIS?

Lynn Deffenbaugh
 

Filters have nothing to do with KISS mode on the RF ports.  Something else is going on.


Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 5/26/2019 12:10 AM, wh6fqe@... [aprsisce] wrote:
Ok, not sure what happened now. I found the wiki page where it showed to add the filter:

b/RS0ISS*/W3ADO-1/ARISS d/RS0ISS*/W3ADO-1/ARISS

Yet once I added this, it kicked my SCS Tracker back out of KISS mode. What the heck?


RC
WH6FQE


Re: Multiple Instances of APRSIS?

WH6FQE
 

Ok, not sure what happened now. I found the wiki page where it showed to add the filter:

b/RS0ISS*/W3ADO-1/ARISS d/RS0ISS*/W3ADO-1/ARISS

Yet once I added this, it kicked my SCS Tracker back out of KISS mode. What the heck?


RC
WH6FQE


Re: APRSIS Internet to RF | I-Gate | Software to Kenwood TM-D710A

Chris Morrison
 

Problem solved. The issue was the APRS-IS port didn't have the IS to RF port checked. The RF port did have it checked and packets were hitting the tracefilter from the APRS-IS so I didn't think there was an issue from the APRS-IS side. 

My other instance didn't work but for that one it was easier to delete the conf file and start again from fresh rather than troubleshoot. 

Your previous message is very useful and I've archived in my email inbox for future reference. I would be useful to have that iGate troubleshooting list on the wiki. 

Many thanks,
Chris
MB7UCM / MM1PTT 


Re: Multiple Instances of APRSIS?

WH6FQE
 

Lynn,

Ok, I figured out what needed to be changed. I simply changed the normal Open and Close command in the XML file over to:

<OpenCmd>^027~!!1</OpenCmd>
<OpenCmd>^064^075!!0</OpenCmd>
<CloseCmd>^192^255^192~!!1</CloseCmd>
<CloseCmd>^027~!!1</CloseCmd>

and now when I bring up APRSIS it puts the SCS Tracker into KISS mode and now allows it to transmit.

Not really sure what all that coding means, but the Tracker is now staying in KISS mode like it is supposed to and it appears to be working correctly. Will have to wait and see if it actually picks up the Satellite APRS signals or not.


RC
WH6FQE


Re: Multiple Instances of APRSIS?

Lynn Deffenbaugh
 

Can you e-mail your APRSIS32.XML configuration file to KJ4ERJ@...?  And the name of the port that is connected to the SCS.  The default for Simply(KISS) is no s.  But if you (or someone) manually added some they'll be in there.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 5/23/2019 6:30 PM, wh6fqe@... [aprsisce] wrote:
Lynn,

Everytime it is put into KISS mode, when I launch APRSIS it takes it back out of KISS mode and the red KISS mode light goes back off. The port in APRSIS is set as Simply(KISS) protocol.

RC
WH6FQE


Re: Multiple Instances of APRSIS?

WH6FQE
 

Lynn,

Everytime it is put into KISS mode, when I launch APRSIS it takes it back out of KISS mode and the red KISS mode light goes back off. The port in APRSIS is set as Simply(KISS) protocol.

RC
WH6FQE


Re: Multiple Instances of APRSIS?

Lynn Deffenbaugh
 

You need to use a terminal emulator or something to put your SCS Tracker back into KISS mode.  But before you do that, delete the (probably) KISS-type port you created for it and create it as a Simply(KISS).  The former is designed for Kenwood APRS radios (other than the D74) and does send the exit KISS command when the port is disabled or the program is closed.  The latter does not do any commands to the TNC at all.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 5/23/2019 2:24 AM, wh6fqe@... [aprsisce] wrote:
Lynn,

Ok, I rebooted BPQ32, which that Comport was attached to, and that resolved that issue, apparently somehow it was still attached and holding the comport open.

The Satgate OK now shows up in the APRSIS as it should, but APRSIS has knocked my SCS Tracker out of Kiss Mode now. The red KISS light on the Tracker went off once BPQ32 was rebooted and it let go of the comport.

It has to be APRSIS that is forcing it out of KISS mode because the DIP switch on the front of the Tracker is set to be in KISS mode.

RC
WH6FQE


Re: Multiple Instances of APRSIS?

WH6FQE
 

Robert,

The port was apparently somehow still connected to BPQ32, when I rebooted BPQ32 it released it and APRSIS could connect to it, but it forced the SCS Tracker out of KISS mode now even though the Trackers DIP switch is set for KISS mode.


RC
WH6FQE


Re: Multiple Instances of APRSIS?

WH6FQE
 

Lynn,

Right, I have my normal APRS IGate set to -3 and the SatGate set to -6


RC
WH6FQE


Re: Multiple Instances of APRSIS?

WH6FQE
 

Lynn,

Ok, I rebooted BPQ32, which that Comport was attached to, and that resolved that issue, apparently somehow it was still attached and holding the comport open.

The Satgate OK now shows up in the APRSIS as it should, but APRSIS has knocked my SCS Tracker out of Kiss Mode now. The red KISS light on the Tracker went off once BPQ32 was rebooted and it let go of the comport.

It has to be APRSIS that is forcing it out of KISS mode because the DIP switch on the front of the Tracker is set to be in KISS mode.

RC
WH6FQE


Re: messages failing - message lockup

Michael Wright
 

If it hasn't worked for the past two years
overall this has worked, it is simply my station I can't send a short message "OK" to let people at Start line know I received info on riders and start times. As mentioned before I can still receive but transmitting fails between 9 am and 12 noon.

I just adjusted my set to send only Wide 1-1 to reduce hops.

You will clobber other stations and make people mad
not really, I don't beacon and only send short message "copy" or "OK" so station that sends race data know I received it. Our voice channels can get busy. Other stations are at lower level.

Team has a number of Tinytrack radios they put in SAG vehicles with magmount antenna.

Mike K6MFW


Re: messages failing - message lockup

Greg D
 

I think the suggestion to move to a non-APRS digital channel might be a good one.  If you need a presence on APRS-IS, an iGate at the top of the hill could do that.  I'm involved in some large events, where we use both voice and Winlink on VHF.  A good bit of effort is spent optimizing channel usage, both voice and data, to improve reliability, and it really helps.

Greg  KO6TH


James Ewen ve6srv@... [aprsisce] wrote:

 
W6TCP looks like a digi you might be trying to use. I can't tell if it is listening on 144.390 or not.

Here's what it is listening to on a regular basis.
https://aprs.fi/#!v=heard&call=a%2FW6TCP&timerange=3600&tail=3600  

The graphs of activity make me wonder what's going on.

This shows even fewer users which makes me think it's not on 144.390.


WA6ODP-2 looks like it is on 144.390 and hears far too much...
 
You can see from the graphs that it regularly hears stations out to 100 miles away.

Here's another look at all the digi users.

If you are trying to use these digipeaters to support your event, perhaps you can look at placing digipeaters at these sites on an alternate frequency temporarily and using that instead.

If it hasn't worked for the past two years and you are doing nothing to change the way you are operating, chances are it won't work again this year.

James
VE6SRV


On Wed, May 22, 2019 at 5:52 PM James Ewen <ve6srv@...> wrote:
Here’s the view from an outsider looking in with little information. 

If you are wanting to transmit onto 144.390 from a site overlooking SAN Fransisco at 4300 feet ASL, you will need to ignore the input. Easy way to do so is to not connect a receiver to the APRSISCE/32 instance. Transmit blind.. You will clobber other stations and make people mad, but you will never find a quiet time to be able to transmit otherwise.

If you need to receive information from other stations and they are on 144.390, then you’re out of luck for transmitting, unless somehow no one is operating on 144.390.

An alternate solution is to use a frequency that is not over saturated and run all operations on that frequency you will have an empty channel to transmit into, and will likely find that you have far better success with hearing other stations in the quiet rather than trying to pick them out of the noise.

Simple radio concepts that people seem to forget when they work in digital.

If there’s a pile up on HF, do you try to rag chew with your buddy overtop of the pile up, or do you look for a quiet frequency and have a nice chinwag with each other?

You are not locked on 144.390 unless you’re still using a crystal controlled radio.

James
VE6SRV

On May 22, 2019, at 5:21 PM, 'Michael Wright' mfwright@... [aprsisce] <aprsisce@...> wrote:

>> Read about PERSIST and SLOTTIME for your TNC to understand how a KISS TNC determines if the channel is busy.
>
> I read that this morning, I was wondering if I set these in config file to zero and Direwolf will transmit no matter what. At 4300 feet Mt Hamilton overlooks entire SF bay area plus Monterey bay area and a good portion of central calif. Last year I tried putting squelch to maximum but the radio still would not transmit. At that altitude even an FRS radio will have full quieting.
>
> Before I left for work, I fired up my laptop to see how well it holds up during the day. And appears to do quite well, I probably should widen times between beacons and remove telemetry transmissions so not be one to congest 144.39.
>
> For this Sunday's Mt Hamilton Classic bike race, I will not beacon and will not have Ack checked for messaging. We can always say a brief "got data" by voice.
>
> thanks, Mike K6MFW
>
>
> ------------------------------------
> Posted by: "Michael Wright" <mfwright@...>
> ------------------------------------
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
> <*> To visit your group on the web, go to:
>    http://groups.yahoo.com/group/aprsisce/
>
> <*> Your email settings:
>    Individual Email | Traditional
>
> <*> To change settings online go to:
>    http://groups.yahoo.com/group/aprsisce/join
>    (Yahoo! ID required)
>
> <*> To change settings via email:
>    aprsisce-digest@...
>    aprsisce-fullfeatured@...
>
> <*> To unsubscribe from this group, send an email to:
>    aprsisce-unsubscribe@...
>
> <*> Your use of Yahoo Groups is subject to:
>    https://info.yahoo.com/legal/us/yahoo/utos/terms/
>


Re: messages failing - message lockup

Rob Giuliano
 

Option 2:
SDR for receive (maybe with a TX mute to prevent overload) and disconnect the receive capability to the TNC that is doing the TX.  This could be done with separate ports (and possible sound cards) in an app like Dire Wolf.  Since APRSIS32 can only TX on the first AGW stream, you can use the second stream for receive and give no receieve audio to the first.  WIth Cheap USB sound cards this would be fairly easy to accomplish.

Robert Giuliano

KB8RCO



On Wednesday, May 22, 2019, 7:53:20 PM EDT, James Ewen ve6srv@... [aprsisce] wrote:


 

Here’s the view from an outsider looking in with little information.

If you are wanting to transmit onto 144.390 from a site overlooking SAN Fransisco at 4300 feet ASL, you will need to ignore the input. Easy way to do so is to not connect a receiver to the APRSISCE/32 instance. Transmit blind.. You will clobber other stations and make people mad, but you will never find a quiet time to be able to transmit otherwise.

If you need to receive information from other stations and they are on 144.390, then you’re out of luck for transmitting, unless somehow no one is operating on 144.390.

An alternate solution is to use a frequency that is not over saturated and run all operations on that frequency you will have an empty channel to transmit into, and will likely find that you have far better success with hearing other stations in the quiet rather than trying to pick them out of the noise.

Simple radio concepts that people seem to forget when they work in digital.

If there’s a pile up on HF, do you try to rag chew with your buddy overtop of the pile up, or do you look for a quiet frequency and have a nice chinwag with each other?

You are not locked on 144.390 unless you’re still using a crystal controlled radio.

James
VE6SRV

On May 22, 2019, at 5:21 PM, 'Michael Wright' mfwright@... [aprsisce] wrote:

>> Read about PERSIST and SLOTTIME for your TNC to understand how a KISS TNC determines if the channel is busy.
>
> I read that this morning, I was wondering if I set these in config file to zero and Direwolf will transmit no matter what. At 4300 feet Mt Hamilton overlooks entire SF bay area plus Monterey bay area and a good portion of central calif. Last year I tried putting squelch to maximum but the radio still would not transmit. At that altitude even an FRS radio will have full quieting.
>
> Before I left for work, I fired up my laptop to see how well it holds up during the day. And appears to do quite well, I probably should widen times between beacons and remove telemetry transmissions so not be one to congest 144.39.
>
> For this Sunday's Mt Hamilton Classic bike race, I will not beacon and will not have Ack checked for messaging. We can always say a brief "got data" by voice.
>
> thanks, Mike K6MFW
>
>
> ------------------------------------
> Posted by: "Michael Wright"
> ------------------------------------
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>

2141 - 2160 of 35599