Yes, if N7FMHL-1 sends its own telemetry definitions to itself,
APRSISCE/32 will pick them up and subsequently use them for any
telemetry coming from N7FMHL-1.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
toggle quoted messageShow quoted text
On 8/16/2021 4:37 PM, Fred Hillhouse
wrote:
One
of the reasons I can get away with the extra character is
because I am starting with a 1x3 rather than a 2x3.
Otherwise I would need to create a “tactical” for the
battery box.
I
have a second station, N7FMH-3 which would send N7FMHG-x and
it will have more than 5 data fields. If is not up and
running yet as I am still working the kinks out of N7FMH-2.
Again,
the intent is to have N7FMH-2 send telemetry as definitions
and telemetry as N7FMHL-x. See example:
2021-08-16 03:50:14 EDT: N7FMHL-1>APDW17,UNCAN*,WIDE2*,qAR,W1MV-1::N7FMHL-1 :PARM.Charge,V1Volts,V2Volts,Temperature,Power
2021-08-16 05:50:17 EDT: N7FMHL-1>APDW17,UNCAN,WIDE2*,qAR,W1IRK-1::N7FMHL-1 :UNIT.%,V,V,F,W
2021-08-16 06:50:28 EDT: N7FMHL-1>APDW17,UNCAN,WIDE2*,qAR,W1TG-1::N7FMHL-1 :EQNS.0,.1,0,0,.01,0,0,.01,0,0,.18,32,0,.35,-2100
It
is already sending telemetry correctly:
2021-08-16 07:37:00 EDT: N7FMHL-1>APDW17,UNCAN,WIDE2*,qAR,N3LEE-4:!4259.90N/07130.39WGN7FMH LiFe-Po4|!x.n/Z!##.bg|
The
goal is to be able to send more than 5 channels of data.
If
it did that, then APRSIS32 will work?
Best
regards,
Fred
N7FMH
On 8/16/2021 3:51 PM, Fred Hillhouse wrote:
Not
sure what you mean by this.
“Out of curiosity, do you happen to know what Direwolf does
with the "extra" telemetry station ID's if you start with a
full station callsign like KJ4ERJ-12?”
If N7FMH-2 becomes N7FMHL-2, then KJ4ERJ-12 would become
KJ4ERJL-12 which is completely invalid because the base
callsign is limited to 6 characters.
The
intent is for N7FMH-2 to send telemetry definitions and
telemetry as N7FMHL-x.
That is exactly what APRSISCE/32 won't handle as
definitions. The definitions need to come from and be
addressed to the station sending the telemetry.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
I'm pretty sure APRSISCE/32 doesn't check the validity of
the callsign prefix vs suffix length.
But your problem is how Direwolf is sending out the
telemetry definitions. The definition of the definitions is
a station sending a message to itself, not a station sending
a message to another station. Consider:
2021-08-16 03:50:14 EDT: N7FMH-2>APDW17,UNCAN*,WIDE2*,qAR,W1MV-1::N7FMHL-1 :PARM.Charge,V1Volts,V2Volts,Temperature,Power
2021-08-16 05:50:17 EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1IRK-1::N7FMHL-1 :UNIT.%,V,V,F,W
2021-08-16 06:50:28 EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1::N7FMHL-1 :EQNS.0,.1,0,0,.01,0,0,.01,0,0,.18,32,0,.35,-2100
2021-08-15 12:04:13 EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,N3LEE-4::N7FMHL-2 :PARM.Current,PeakCurrent,ChargeMeter,PowerMeter,TimeSinceStart
2021-08-15 12:04:33 EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1::N7FMHL-2 :EQNS.0,.025,-150,0,.01,0,0,-1,0,0,0,-4000,0,.1,0
2021-08-16 04:50:46 EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1::N7FMHL-2 :UNIT.A,A,C,W,D
Those are N7FMH-2 sending messages to N7FMHL-1 and
N7FMHL-2. APRSISCE/32 will not treat those as telemetry
definitions, but as messages addressed to those stations.
The spec doesn't explicitly say who the sender of the
messages is allowed/expected to be, only that the messages
are addressed to the station that will be generating the
telemetry. To avoid false definitions, I decided a long
time ago that the definitions should also come FROM and be
addressed TO the exact station generating the telemetry.
Out of curiosity, do you happen to know what Direwolf does
with the "extra" telemetry station ID's if you start with a
full station callsign like KJ4ERJ-12?
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 8/16/2021 2:23 PM, Fred Hillhouse
wrote:
Hi
James,
I
had not thought of that but I am almost positive it
worked sometime in the past. I tinker with direwolf.conf
and the Python script every now and then, so, it is very
possible something was broken. However, in theory, the
only thing I changed recently was the offset. I found I
was generating a negative value occasionally.
Best
regards,
Fred
N7FMH
From:
APRSISCE@groups.io [mailto:APRSISCE@groups.io]
On Behalf Of James Ewen
Sent: Monday, August 16, 2021 2:10 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery
You have a 4 letter suffix on those
two stations.
The program might be barking at
that.
Have you tried it with a three letter
suffix?
Greetings
Lynn,
I
have a bit of a telemetry mystery. The station
is N7FMH-2 and telemetry packets are for
N7FMHL-1 and N7FMHL-2. There is no record of
telemetry in my APRSIS32.xml. However, It does
show up on APRS.FI
(copies below). That is the mystery.
N7FMH-2
is a battery box with a Raspberry Pi Zero
running Direwolf Version 1.7A. It is only over
RF.
Direwolf
1.7A has a feature which allows N7FMH-2 to send
multiple telemetry packet by changing the
“source”. It is sending from two sources,
N7FMHL-1 and N7FMHL-2. There are 10 fields in
use.
Thank
you!
Best
regards,
Fred
N7FMH
Excerpt
from: https://aprs.fi/?c=raw&call=N7FMH-2
2021-08-16 03:50:14
EDT: N7FMH-2>APDW17,UNCAN*,WIDE2*,qAR,W1MV-1::N7FMHL-1 :PARM.Charge,V1Volts,V2Volts,Temperature,Power
2021-08-16
05:50:17 EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1IRK-1::N7FMHL-1 :UNIT.%,V,V,F,W
2021-08-16
06:50:28 EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1::N7FMHL-1 :EQNS.0,.1,0,0,.01,0,0,.01,0,0,.18,32,0,.35,-2100
2021-08-15 12:04:13
EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,N3LEE-4::N7FMHL-2 :PARM.Current,PeakCurrent,ChargeMeter,PowerMeter,TimeSinceStart
2021-08-15 12:04:33
EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1::N7FMHL-2 :EQNS.0,.025,-150,0,.01,0,0,-1,0,0,0,-4000,0,.1,0
2021-08-16 04:50:46
EDT: N7FMH-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1::N7FMHL-2 :UNIT.A,A,C,W,D
From:
https://aprs.fi/?c=raw&call=N7FMHL-1
2021-08-16 07:37:00
EDT: N7FMHL-1>APDW17,UNCAN,WIDE2*,qAR,N3LEE-4:!4259.90N/07130.39WGN7FMH LiFe-Po4|!x.n/Z!##.bg|
2021-08-16 09:52:04
EDT: N7FMHL-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1:!4259.90N/07130.39WGN7FMH LiFe-Po4|"0bf-&!4JY%^|
Telemetry
pages:
https://aprs.fi/telemetry/N7FMHL-1
Values:
Charge: 126 %
(TLM: 1260 EQN: 0,0.1,0)
V1Volts: 13.310
V (TLM: 1331 EQN: 0,0.01,0)
V2Volts: 0.020
V (TLM: 2 EQN: 0,0.01,0)
Temperature:
67.100 F (TLM: 195 EQN: 0,0.18,32)+
Power: -5.250 W
(TLM: 5985 EQN: 0,0.35,-2100)
https://aprs.fi/telemetry/N7FMHL-2
Values:
Current: -0.400
A (TLM: 5984 EQN: 0,0.025,-150)
PeakCurrent:
10.970 A (TLM: 1097 EQN: 0,0.01,0)
ChargeMeter:
-19 C (TLM: 19 EQN: 0,-1,0)
PowerMeter:
-4000 W (TLM: 3787 EQN: 0,0,-4000)
TimeSinceStart:
42.500 D (TLM: 425 EQN: 0,0.1,0)
|
|
This
email has been checked for viruses by
Avast antivirus software.
www.avast.com
|
--
|
