Date   
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
>
>
>

Re: Multiple Instances of APRSIS?

Rob Giuliano
 

The 4 args are 9600,n,8,1 -> normal port settings.
Best guess on the error is that the port is already in use.
   Are you running another app that is accessing the same TNC or leave a configuration app open?

Robert Giuliano
KB8RCO



On Wednesday, May 22, 2019, 10:15:58 PM EDT, Randy Love rlove31@... [aprsisce] wrote:


 

Lynn will have to decipher those. 
He can find them in the code and give you a good idea what needs to be wiggled. 

Randy
WF5X 

On Wed, May 22, 2019, 9:41 PM wh6fqe@... [aprsisce] <aprsisce@...> wrote:
 

I am not finding where the problem with the SatGate radio setup is.. In the logging it shows this over and over again:


Port(SatGate):2019-05-23T01:37:55.866 Opening COM14:9600,N,8,1
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 with 4 Args
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 Got -1 Error 5
Port(SatGate):2019-05-23T01:37:55.866 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
Port(SatGate):2019-05-23T01:37:55.866 Error Opening COM14:9600,N,8,1 LastError 0

But I don't have a clue what all of that means.

RC
WH6FQE

Re: Multiple Instances of APRSIS?

Lynn Deffenbaugh
 

Also, the two instances need to use two different -SSIDs if you didn't already know that.

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

On 5/22/2019 9:40 PM, wh6fqe@... [aprsisce] wrote:
I am not finding where the problem with the SatGate radio setup is. In the logging it shows this over and over again:

Port(SatGate):2019-05-23T01:37:55.866 Opening COM14:9600,N,8,1
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 with 4 Args
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 Got -1 Error 5
Port(SatGate):2019-05-23T01:37:55.866 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
Port(SatGate):2019-05-23T01:37:55.866 Error Opening COM14:9600,N,8,1 LastError 0

But I don't have a clue what all of that means.

RC
WH6FQE

Re: Multiple Instances of APRSIS?

Lynn Deffenbaugh
 

It is highly likely that something else has COM14 open (Error 5).  Possibly your original instance still has that port defined?  If so, simply disable it there.

If you have any other programs using COM14, APRSISCE/32 won't be able to open it either.  A terminal emulator, a TNC utility, anything.  Windows only allows one program at a time to use most COM ports.

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

On 5/22/2019 9:40 PM, wh6fqe@... [aprsisce] wrote:
I am not finding where the problem with the SatGate radio setup is. In the logging it shows this over and over again:

Port(SatGate):2019-05-23T01:37:55.866 Opening COM14:9600,N,8,1
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 with 4 Args
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 Got -1 Error 5
Port(SatGate):2019-05-23T01:37:55.866 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
Port(SatGate):2019-05-23T01:37:55.866 Error Opening COM14:9600,N,8,1 LastError 0

But I don't have a clue what all of that means.

RC
WH6FQE

Re: Multiple Instances of APRSIS?

Rob Giuliano
 

I personally prefer the shortcut method in the second directory.
Make sure you have the  "Start in:" folder set to the second instance and point the "Target:" to the actual executable.
This makes it easier to update the EXE file on both instances at the same time.

Also recommend setting a path to your maps in the XML of each to the same folder so that you can use common map tiles

Robert Giuliano
KB8RCO



On Wednesday, May 22, 2019, 7:35:59 PM EDT, Randy Love rlove31@... [aprsisce] wrote:


 

Yes, very easily actually.

Just make a different folder for your second instance and install it again from the .zip file.
You can point it to the maps of the first instance if you don't want to duplicate the folders and data for them.



73,
Randy
WF5X



On Wed, May 22, 2019 at 6:47 PM wh6fqe@... [aprsisce] <aprsisce@...> wrote:
 

I am still having trouble trying to get a SatGate setup here in Hawaii. I tried using a different program which was recommended for SatGates, however I am getting absolutely no support over there at all in trying to figure out how to get the program to function. So I am back to this one which works fine for my APRS iGate that I operate.


We figured out that I can not have the APRSIS system set up with two different radios on different frequencies, but is there a way of running multiple instances of APRSIS, one connected to each radio?


RC

WH6FQE

Re: Multiple Instances of APRSIS?

Randy Love
 

Lynn will have to decipher those. 
He can find them in the code and give you a good idea what needs to be wiggled. 

Randy
WF5X 

On Wed, May 22, 2019, 9:41 PM wh6fqe@... [aprsisce] <aprsisce@...> wrote:
 

I am not finding where the problem with the SatGate radio setup is. In the logging it shows this over and over again:


Port(SatGate):2019-05-23T01:37:55.866 Opening COM14:9600,N,8,1
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 with 4 Args
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 Got -1 Error 5
Port(SatGate):2019-05-23T01:37:55.866 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
Port(SatGate):2019-05-23T01:37:55.866 Error Opening COM14:9600,N,8,1 LastError 0

But I don't have a clue what all of that means.

RC
WH6FQE

Re: Multiple Instances of APRSIS?

WH6FQE
 

I am not finding where the problem with the SatGate radio setup is. In the logging it shows this over and over again:

Port(SatGate):2019-05-23T01:37:55.866 Opening COM14:9600,N,8,1
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 with 4 Args
Port(SatGate):2019-05-23T01:37:55.866 Opening COM14 Got -1 Error 5
Port(SatGate):2019-05-23T01:37:55.866 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
Port(SatGate):2019-05-23T01:37:55.866 Error Opening COM14:9600,N,8,1 LastError 0

But I don't have a clue what all of that means.

RC
WH6FQE

Re: messages failing - message lockup

James Ewen
 

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

James Ewen
 

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


Re: Multiple Instances of APRSIS?

Randy Love
 

Ok.

It should just be particular to the setting for that port and TNC.

Good luck!

73,
Randy
WF5X


On Wed, May 22, 2019 at 7:48 PM wh6fqe@... [aprsisce] <aprsisce@...> wrote:
 

Randy,


Thanks. I got the program duplicated to another folder and both instances are now running, I just have to track down an issue with the new one. Where the original at the top left flashes back and forth between APRS-IS OK and Radio OK the new one is flashing between APRS-IS OK and SatGate Open and will not transmit.

Had to commandeer my SCS Tracker that I normally run my VHF Winlink Gateway on to use for this to see if I can get the SatGate working, but something isn't quite right somewhere with the settings yet.

RC
WH6FQE

Re: Multiple Instances of APRSIS?

WH6FQE
 

Randy,

Thanks. I got the program duplicated to another folder and both instances are now running, I just have to track down an issue with the new one. Where the original at the top left flashes back and forth between APRS-IS OK and Radio OK the new one is flashing between APRS-IS OK and SatGate Open and will not transmit.

Had to commandeer my SCS Tracker that I normally run my VHF Winlink Gateway on to use for this to see if I can get the SatGate working, but something isn't quite right somewhere with the settings yet.

RC
WH6FQE

Re: Multiple Instances of APRSIS?

Randy Love
 

Yes, very easily actually.

Just make a different folder for your second instance and install it again from the .zip file.
You can point it to the maps of the first instance if you don't want to duplicate the folders and data for them.



73,
Randy
WF5X



On Wed, May 22, 2019 at 6:47 PM wh6fqe@... [aprsisce] <aprsisce@...> wrote:
 

I am still having trouble trying to get a SatGate setup here in Hawaii. I tried using a different program which was recommended for SatGates, however I am getting absolutely no support over there at all in trying to figure out how to get the program to function. So I am back to this one which works fine for my APRS iGate that I operate.


We figured out that I can not have the APRSIS system set up with two different radios on different frequencies, but is there a way of running multiple instances of APRSIS, one connected to each radio?


RC

WH6FQE

Re: messages failing - message lockup

Michael Wright
 

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

Multiple Instances of APRSIS?

WH6FQE
 

I am still having trouble trying to get a SatGate setup here in Hawaii. I tried using a different program which was recommended for SatGates, however I am getting absolutely no support over there at all in trying to figure out how to get the program to function. So I am back to this one which works fine for my APRS iGate that I operate.


We figured out that I can not have the APRSIS system set up with two different radios on different frequencies, but is there a way of running multiple instances of APRSIS, one connected to each radio?


RC

WH6FQE

Re: messages failing - message lockup

Rob Giuliano
 

Read about PERSIST and SLOTTIME for your TNC to understand how a KISS TNC determines if the channel is busy.

In reality, since SLOTTIME and PERSIST define a probability, if any signal is detected within the parameters the TNC won't TX.  

Simple Test:  does the setup transmit on the bench into a dummy load with no signals present?
If so, you are going to have issue with that amount of local RF.

Since you brought it up, you need to "trick" the TNC into thinking the RF is clear in order to TX.  Since most modern (DSP based) TNCs use open squelch and an algorithm to determine if the RF has "data", the only method I can think of is raise the Squelch level.  Set the Squelch so that very weak signals will not break it and you should be able to TX.

TWO ISSUES:
  Keep in mind that it will be on top of another "weaker" signal.
  Those signals that were heard before the raised squelch won't be decoded, DIGI'ed or handled in any way.

Within those parameters, you can decide how you want the system to work.

Robert Giuliano
KB8RCO



On Wednesday, May 22, 2019, 8:53:19 AM EDT, 'Lynn W Deffenbaugh (Mr)' kj4erj@... [aprsisce] <aprsisce@...> wrote:


 

APRSIS32 is completely unaware of the channel conditions.  When it wants
to transmit (except for messages blocked by non-acknowledged pending
one), it sends the packet over to the TNC.  It's up to the TNC to
evaluate channel conditions and decide when it is clear enough to transmit.

If you're using DireWolf, you need to check there for settings affecting
transmits.  But feel free to post back to the group here if you find
something.

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

On 5/22/2019 12:24 AM, 'Michael Wright' mfwright@... [aprsisce]
wrote:
>> It almost sounds like your TNC thinks the channel is always busy and
>> won't transmit anything.  Have you listened to 144.390 (or whatever
> I suspect the same thing, at 4300 ft, it is wall to wall signal. I wonder if APRSISCE can do a force transmit. fyi, my TNC is Direwolf and a SignalinkUSB for radio interface.
>
>> enable the Transmit window as well as the Port().
>> You should see trace logs in those windows whenever APRSISCE/32 actually
>> sends stuff to the TNC.
> I will try that.
>
> Thanks for the help, Mike K6MFW
>
> ------------------------------------
> Posted by: "Michael Wright" > ------------------------------------
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>

Re: messages failing - message lockup

Lynn Deffenbaugh
 

APRSIS32 is completely unaware of the channel conditions.  When it wants to transmit (except for messages blocked by non-acknowledged pending one), it sends the packet over to the TNC.  It's up to the TNC to evaluate channel conditions and decide when it is clear enough to transmit.

If you're using DireWolf, you need to check there for settings affecting transmits.  But feel free to post back to the group here if you find something.


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

On 5/22/2019 12:24 AM, 'Michael Wright' mfwright@... [aprsisce] wrote:
It almost sounds like your TNC thinks the channel is always busy and
won't transmit anything.  Have you listened to 144.390 (or whatever
I suspect the same thing, at 4300 ft, it is wall to wall signal. I wonder if APRSISCE can do a force transmit. fyi, my TNC is Direwolf and a SignalinkUSB for radio interface.

enable the Transmit window as well as the Port(<YourPortName>).
You should see trace logs in those windows whenever APRSISCE/32 actually
sends stuff to the TNC.
I will try that.

Thanks for the help, Mike K6MFW

------------------------------------
Posted by: "Michael Wright" <mfwright@...>
------------------------------------


------------------------------------

Yahoo Groups Links