Re: Telemetry mystery

Rob Giuliano

It looks to me like the solution needs to be in Direwolf.
You jyst need 2 new sources N7FHML-1 and N7FHML-2.

The problem is they have to use the common device.
So maybe contruct the entire packet in the python or pearl scripts.
At least for the parameter info.


On Mon, Aug 16, 2021 at 18:06, Fred Hillhouse
<fmhillhouse@...> wrote:

“Fred wanted to use (a).”

Hmm, not really. J But it is what my config was doing.


Thank you for identifying the problem. Now to work a solution in!


Best regards,

Fred N7FMH



From: [] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 5:38 PM
Subject: Re: [APRSISCE] Telemetry mystery


For APRSISCE/32, (b) is the only one that would work to define telemetry.  Fred wanted to use (a).  (c) and (d) are modifying the "tocall" which is neither the originator nor the addressee of the message.  The originator is before the > and the addressee is between the :: and :.

And yes, you'd repeat (b) 4 times from/to N7FMHL-1 and 4 more times for N7FMHL-2.  The 4 times are for the 4 different definition messages: PARM, UNIT, EQNS, and BITS.

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

On 8/16/2021 4:58 PM, Rob Giuliano via wrote:


I am not sure I am following this properly.


Which of these (if any) should work?

a) N7FMH-2>APDW17,WIDE2-1::N7FMHL-1 :PARM.Charge,V1Volts,V2Volts,Temperature,Power

b) N7FMHL-1>APDW17,WIDE2-1::N7FMHL-1 :PARM.Charge,V1Volts,V2Volts,Temperature,Power

c) N7FMHL-1> N7FMHL-1,WIDE2-1::N7FMHL-1 :PARM.Charge,V1Volts,V2Volts,Temperature,Power

d) N7FMH-2> N7FMHL-1,WIDE2-1::N7FMHL-1 :PARM.Charge,V1Volts,V2Volts,Temperature,Power


The key parameter being that the data is associated with the highlighted (pseudo) callsign-ssid of N7FMHL-1.

The second set of data would use N7FMHL-2.


Robert Giuliano  KB8RCO



Join to automatically receive all group messages.