Re: [aprsisce] Re: Delayed digipeats
- I was reading somewhere that there is an implementation where the use is reversed.That was what prompted the thought.Robert Giuliano
KB8RCO---------------------------------------------From: James Ewen <ve6srv@...>
Sent: Monday, March 18, 2013 5:12 PM
Subject: Re: [aprsisce] Re: Delayed digipeatsOn Mon, Mar 18, 2013 at 8:52 AM, asbjorn.hauge <mailto:asbjorn.hauge%40yahoo.no> wrote:
> --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@...> wrote:
>> Are you sure this is not related to your "SlotTime" and "Persist" settings?
> That may just be the answer! I will check that when I get home.
3 to 15 seconds seems awfully long for slottime and persist.
If persist were set very low, then the odds of it being hit are pretty
slim, and if slottime were very high you could wait a long time
between random checks.... I suppose it is possible.
- --- In firstname.lastname@example.org, James Ewen <ve6srv@...> wrote:
> Do you have a user manual for your TNC? I only have the KPC-3 manualYes I have the manual. I've checked out every parameter and tried out settings for everything that is related to KISS-mode. It works, but it's slow.
> which describes the settings as it pertains to that device, but they
> should be similar.
Just to try out other possibilities: I have configured my TinyTrak4 to work in KISS, hooked it up and set APRSISCE/32 to use that one. It all works fairly well and all received packets are transferred to the software blazing fast (running 57600 baud). I still have a fair bit of delay using this setup (never less than three seconds from a free channel), while the same TNC config in UI-View is super-snappy (instant digipeat if channel is clear).
From the logs I posted earlier, I see that APRSISCE/32 adds some strange traffic to the RS232-port and logs sent strings as mostly HEX data. Could it be the way the program sends data or handles the COM-port? I will try running it on another computer and different serial port just for comparison.