Telemetry mystery


Fred Hillhouse
 

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



James Ewen
 

Fred,

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?

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


--
James
VE6SRV


Fred Hillhouse
 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



--

James
VE6SRV


Randy Love
 

Yeah, a 4 long suffix fails AX.25 protocol for a callsign.
It should be fine as an object/item name tho.

Randy
WF5X


On Mon, Aug 16, 2021 at 2:23 PM Fred Hillhouse <fmhillhouse@...> 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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



--

James
VE6SRV


Randy Love
 

Wait, scratch that... it will pass because the total number of letters/number in the Callsign is under 6... 

however, something like WB5ABCD will NOT... 

Randy
WF5X

On Mon, Aug 16, 2021 at 2:33 PM Randy Love via groups.io <rlove31=gmail.com@groups.io> wrote:
Yeah, a 4 long suffix fails AX.25 protocol for a callsign.
It should be fine as an object/item name tho.

Randy
WF5X


On Mon, Aug 16, 2021 at 2:23 PM Fred Hillhouse <fmhillhouse@...> 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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



--

James
VE6SRV


Fred Hillhouse
 

Greetings,

 

Interesting thought. If I understand this correctly, a KB1ABC will work at 6 characters but N7FMHL will not at 6 characters. PIGEON, with 6 characters work and it isn’t even a call sign. The question I have is, would PIGEON work if it was PIGEON-1? If so, then N7FMHL-1 should work.

 

I do know that APRS.FI will handle nearly everything thrown at it. Before compressing my data into Base91, I could send raw data and it didn’t care. However, APRSIS32 did not recognize it so I wanted to formalize the data.

 

Best regards,

Fred N7FMH

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Randy Love
Sent: Monday, August 16, 2021 2:34 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

Wait, scratch that... it will pass because the total number of letters/number in the Callsign is under 6... 

 

however, something like WB5ABCD will NOT... 

 

Randy

WF5X

 

On Mon, Aug 16, 2021 at 2:33 PM Randy Love via groups.io <rlove31=gmail.com@groups.io> wrote:

Yeah, a 4 long suffix fails AX.25 protocol for a callsign.

It should be fine as an object/item name tho.

 

Randy

WF5X

 

 

On Mon, Aug 16, 2021 at 2:23 PM Fred Hillhouse <fmhillhouse@...> 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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com

 

--

James
VE6SRV


Lynn Deffenbaugh
 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



--

James
VE6SRV


Fred Hillhouse
 

Hi Lynn,

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?

Hmm, it seems that maybe I left out a setting in the .CONF since the telemetry looks like it is sent 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|

2021-08-16 09:52:04 EDT: N7FMHL-2>APDW17,UNCAN,WIDE2*,qAR,W1TG-1:!4259.90N/07130.39WGN7FMH LiFe-Po4|"0bf-&!4JY%^|

The intent is for N7FMH-2 to send telemetry definitions and telemetry as N7FMHL-x.

Thank You!

 

Best regards,

Fred N7FMH

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com




--

James
VE6SRV


Lynn Deffenbaugh
 

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

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com




--

James
VE6SRV


Robert Bruninga
 

Warning!

The APRSSERVER software at all IGatges will not pass non-valid calls.
This is NOT a restriction of the APRS protocol but of the opinion of the
APRSRVER author.

Not sure what happens when it finds one.

FOr example, there was some kind of conflict for packegts from my PSAT and PSAT2 
satellites that would not go through  the APRS-IS because of this restriction.
THough I maybe forgetting something because all my PSAT and PSAT2 web
pages do seem to get their data.

Bob

On Mon, Aug 16, 2021 at 3:22 PM Fred Hillhouse <fmhillhouse@...> wrote:

Greetings,

 

Interesting thought. If I understand this correctly, a KB1ABC will work at 6 characters but N7FMHL will not at 6 characters. PIGEON, with 6 characters work and it isn’t even a call sign. The question I have is, would PIGEON work if it was PIGEON-1? If so, then N7FMHL-1 should work.

 

I do know that APRS.FI will handle nearly everything thrown at it. Before compressing my data into Base91, I could send raw data and it didn’t care. However, APRSIS32 did not recognize it so I wanted to formalize the data.

 

Best regards,

Fred N7FMH

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Randy Love
Sent: Monday, August 16, 2021 2:34 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

Wait, scratch that... it will pass because the total number of letters/number in the Callsign is under 6... 

 

however, something like WB5ABCD will NOT... 

 

Randy

WF5X

 

On Mon, Aug 16, 2021 at 2:33 PM Randy Love via groups.io <rlove31=gmail.com@groups.io> wrote:

Yeah, a 4 long suffix fails AX.25 protocol for a callsign.

It should be fine as an object/item name tho.

 

Randy

WF5X

 

 

On Mon, Aug 16, 2021 at 2:23 PM Fred Hillhouse <fmhillhouse@...> 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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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|

 

From: https://aprs.fi/?c=raw&call=N7FMHL-2

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com

 

--

James
VE6SRV


Fred Hillhouse
 

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

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 4:15 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com





--

James
VE6SRV


Lynn Deffenbaugh
 

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


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

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 4:15 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com





--

James
VE6SRV


Rob Giuliano
 

Lynn,
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


On Monday, August 16, 2021, 04:14:44 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


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

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com




--

James
VE6SRV


Fred Hillhouse
 

If the station was N7FMHL-1 then any definition/telemetry sent works.

The issue is my configuration of Direwolf is sending the telemetry correctly but I don’t have it sending the definitions correctly. I need to fix that.

 

This is the correct way to send definitions (copied from APRS.FI):

KJ4ERJ-12>APWA01,TCPIP*,qAC,T2SWEDEN::KJ4ERJ-12:PARM.Acceleration,Battery,Temperature,SatInView,SatInUse,A/C,Charging,GPS,GPS,NA,NA,NA,NA

 

Based on that, item (b) is correct.

 

Yes, N7FMHL-1 is the first 5 channels and N7FMHL-2 is the second 5 channels, all sent from N7FMH-2 as N7FMHL-1 and N7FMHL-2.

 

Fred N7FMH

 

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Rob Giuliano via groups.io
Sent: Monday, August 16, 2021 4:58 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

Lynn,

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

 

 

On Monday, August 16, 2021, 04:14:44 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:

 

 

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

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



--

James
VE6SRV


Lynn Deffenbaugh
 

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 groups.io wrote:
Lynn,
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


On Monday, August 16, 2021, 04:14:44 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


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

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast
                                                logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com




--

James
VE6SRV


Fred Hillhouse
 

“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: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 5:38 PM
To: APRSISCE@groups.io
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 groups.io wrote:

Lynn,

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

 

 

On Monday, August 16, 2021, 04:14:44 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:

 

 

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

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 3:28 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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

 

Fred,

 

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?

 

On Mon, Aug 16, 2021 at 12:07 PM Fred Hillhouse <fmhillhouse@...> wrote:

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)

 


Avast
                                                logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



--

James
VE6SRV


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.

Rob KB8RCO


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: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 5:38 PM
To: APRSISCE@groups.io
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 groups.io wrote:

Lynn,

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

<snip>

_<sni<p>


Fred Hillhouse
 

The solution was in Direwolf. The skill set to figure this out was Lynn.

 

Version 1.7A added a “source” option. It allows a station to do exactly what is happening here. N7FMH-2 is the LiFe-Po4 Battery Box station.

 

It looks like I have it right.

From my APRSIS32.XML:

<TelemetryDefinition Time="2021-08-17T06:15:37">:N7FMHL-1 :UNIT.%,V,V,F,W</TelemetryDefinition>

<TelemetryDefinition Time="2021-08-17T00:58:46">:N7FMHL-2 :PARM.Current,PeakCurrent,ChargeMeter,PowerMeter,TimeSinceStart</TelemetryDefinition>

<TelemetryDefinition Time="2021-08-17T00:58:46">:N7FMHL-2 :EQNS.0,.025,-150,0,.01,0,0,-1,0,0,0,-4000,0,.1,0</TelemetryDefinition>

 

The local digipeater seems to be off air so the rest of the definitions haven’t been heard yet. I guess I should fire up a RPi Rx Gate for testing so I don’t have to rely on the rest of the system.

 

In my direwolf.conf, I had the blue highlighted text which is why the telemetry was from N7FMHL-x. I added the yellow highlighted last night. Now the definitions are from N7FMHL-x as well.

 

# this group for final design

PBEACON sendto=0 delay=2:10 every=15 via=WIDE2-1 symbol="grid" source="N7FMHL-1" lat=42^59.904N long=071^30.39W comment="N7FMH LiFe-Po4" commentcmd="telem-data91.pl `python3 /home/pi/ThornwavePy/DCPMRead-T.py -A -b CC:03:E6:5D:EE:52`"

PBEACON sendto=0 delay=2:20 every=15 via=WIDE2-1 symbol="grid" source="N7FMHL-2" lat=42^59.904N long=071^30.39W comment="N7FMH LiFe-Po4" commentcmd="telem-data91.pl `python3 /home/pi/ThornwavePy/DCPMRead-T.py -B -b CC:03:E6:5D:EE:52`"

 

CBEACON delay=0:30 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-parm.pl N7FMHL-1 Charge V1Volts V2Volts Temperature Power"

CBEACON delay=0:40 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-unit.pl N7FMHL-1 % V V F W"

CBEACON delay=0:50 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-eqns.pl N7FMHL-1 0 .1 0 0 .01 0 0 .01 0 0 .18 32 0 .35 -2100"

 

CBEACON delay=1:00 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-parm.pl N7FMHL-2 Current PeakCurrent ChargeMeter PowerMeter TimeSinceStart"

CBEACON delay=1:10 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-unit.pl N7FMHL-2 A A C W D"

CBEACON delay=1:20 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-eqns.pl N7FMHL-2 0 .025 -150 0 .01 0 0 -1 0 0 0 -4000 0 .1 0"

 

Now that it is working, I need to spend a little more time working on the data. I think I have 9 of the 10 channels working correctly. Channel B4 (PowerMeter) appears wonky. But, it could be because all the definitions have not been updated across APRS yet. Yep, time to build a Rx Test iGate!

 

Best regards,

Fred N7FMH

 

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Rob Giuliano via groups.io
Sent: Monday, August 16, 2021 8:53 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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.

 

Rob KB8RCO

 

 

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: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 5:38 PM
To: APRSISCE@groups.io
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 groups.io wrote:

Lynn,

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

<snip>

_<sni<p>




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Lynn Deffenbaugh
 

That change to the Direwolf config allows the definition messages to match APRSIS32's expectations exactly (sent from and addressed to the same station that will be sending the telemetry data), as indicated by the snippet from your APRSIS32.xml file.  Congratulations!

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


On 8/17/2021 10:56 AM, Fred Hillhouse wrote:

The solution was in Direwolf. The skill set to figure this out was Lynn.

 

Version 1.7A added a “source” option. It allows a station to do exactly what is happening here. N7FMH-2 is the LiFe-Po4 Battery Box station.

 

It looks like I have it right.

From my APRSIS32.XML:

<TelemetryDefinition Time="2021-08-17T06:15:37">:N7FMHL-1 :UNIT.%,V,V,F,W</TelemetryDefinition>

<TelemetryDefinition Time="2021-08-17T00:58:46">:N7FMHL-2 :PARM.Current,PeakCurrent,ChargeMeter,PowerMeter,TimeSinceStart</TelemetryDefinition>

<TelemetryDefinition Time="2021-08-17T00:58:46">:N7FMHL-2 :EQNS.0,.025,-150,0,.01,0,0,-1,0,0,0,-4000,0,.1,0</TelemetryDefinition>

 

The local digipeater seems to be off air so the rest of the definitions haven’t been heard yet. I guess I should fire up a RPi Rx Gate for testing so I don’t have to rely on the rest of the system.

 

In my direwolf.conf, I had the blue highlighted text which is why the telemetry was from N7FMHL-x. I added the yellow highlighted last night. Now the definitions are from N7FMHL-x as well.

 

# this group for final design

PBEACON sendto=0 delay=2:10 every=15 via=WIDE2-1 symbol="grid" source="N7FMHL-1" lat=42^59.904N long=071^30.39W comment="N7FMH LiFe-Po4" commentcmd="telem-data91.pl `python3 /home/pi/ThornwavePy/DCPMRead-T.py -A -b CC:03:E6:5D:EE:52`"

PBEACON sendto=0 delay=2:20 every=15 via=WIDE2-1 symbol="grid" source="N7FMHL-2" lat=42^59.904N long=071^30.39W comment="N7FMH LiFe-Po4" commentcmd="telem-data91.pl `python3 /home/pi/ThornwavePy/DCPMRead-T.py -B -b CC:03:E6:5D:EE:52`"

 

CBEACON delay=0:30 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-parm.pl N7FMHL-1 Charge V1Volts V2Volts Temperature Power"

CBEACON delay=0:40 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-unit.pl N7FMHL-1 % V V F W"

CBEACON delay=0:50 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-eqns.pl N7FMHL-1 0 .1 0 0 .01 0 0 .01 0 0 .18 32 0 .35 -2100"

 

CBEACON delay=1:00 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-parm.pl N7FMHL-2 Current PeakCurrent ChargeMeter PowerMeter TimeSinceStart"

CBEACON delay=1:10 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-unit.pl N7FMHL-2 A A C W D"

CBEACON delay=1:20 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-eqns.pl N7FMHL-2 0 .025 -150 0 .01 0 0 -1 0 0 0 -4000 0 .1 0"

 

Now that it is working, I need to spend a little more time working on the data. I think I have 9 of the 10 channels working correctly. Channel B4 (PowerMeter) appears wonky. But, it could be because all the definitions have not been updated across APRS yet. Yep, time to build a Rx Test iGate!

 

Best regards,

Fred N7FMH

 

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Rob Giuliano via groups.io
Sent: Monday, August 16, 2021 8:53 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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.

 

Rob KB8RCO

 

 

On Mon, Aug 16, 2021 at 18:06, Fred Hillhouse

“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: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 5:38 PM
To: APRSISCE@groups.io
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 groups.io wrote:

Lynn,

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

<snip>

_<sni<p>




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Fred Hillhouse
 

And, I learned something new about telemetry.

 

Thank you for your help!

 

Fred N7FMH

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Tuesday, August 17, 2021 11:15 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

That change to the Direwolf config allows the definition messages to match APRSIS32's expectations exactly (sent from and addressed to the same station that will be sending the telemetry data), as indicated by the snippet from your APRSIS32.xml file.  Congratulations!

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

On 8/17/2021 10:56 AM, Fred Hillhouse wrote:

The solution was in Direwolf. The skill set to figure this out was Lynn.

 

Version 1.7A added a “source” option. It allows a station to do exactly what is happening here. N7FMH-2 is the LiFe-Po4 Battery Box station.

 

It looks like I have it right.

From my APRSIS32.XML:

<TelemetryDefinition Time="2021-08-17T06:15:37">:N7FMHL-1 :UNIT.%,V,V,F,W</TelemetryDefinition>

<TelemetryDefinition Time="2021-08-17T00:58:46">:N7FMHL-2 :PARM.Current,PeakCurrent,ChargeMeter,PowerMeter,TimeSinceStart</TelemetryDefinition>

<TelemetryDefinition Time="2021-08-17T00:58:46">:N7FMHL-2 :EQNS.0,.025,-150,0,.01,0,0,-1,0,0,0,-4000,0,.1,0</TelemetryDefinition>

 

The local digipeater seems to be off air so the rest of the definitions haven’t been heard yet. I guess I should fire up a RPi Rx Gate for testing so I don’t have to rely on the rest of the system.

 

In my direwolf.conf, I had the blue highlighted text which is why the telemetry was from N7FMHL-x. I added the yellow highlighted last night. Now the definitions are from N7FMHL-x as well.

 

# this group for final design

PBEACON sendto=0 delay=2:10 every=15 via=WIDE2-1 symbol="grid" source="N7FMHL-1" lat=42^59.904N long=071^30.39W comment="N7FMH LiFe-Po4" commentcmd="telem-data91.pl `python3 /home/pi/ThornwavePy/DCPMRead-T.py -A -b CC:03:E6:5D:EE:52`"

PBEACON sendto=0 delay=2:20 every=15 via=WIDE2-1 symbol="grid" source="N7FMHL-2" lat=42^59.904N long=071^30.39W comment="N7FMH LiFe-Po4" commentcmd="telem-data91.pl `python3 /home/pi/ThornwavePy/DCPMRead-T.py -B -b CC:03:E6:5D:EE:52`"

 

CBEACON delay=0:30 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-parm.pl N7FMHL-1 Charge V1Volts V2Volts Temperature Power"

CBEACON delay=0:40 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-unit.pl N7FMHL-1 % V V F W"

CBEACON delay=0:50 every=60 via=WIDE2-1 source="N7FMHL-1" infocmd="telem-eqns.pl N7FMHL-1 0 .1 0 0 .01 0 0 .01 0 0 .18 32 0 .35 -2100"

 

CBEACON delay=1:00 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-parm.pl N7FMHL-2 Current PeakCurrent ChargeMeter PowerMeter TimeSinceStart"

CBEACON delay=1:10 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-unit.pl N7FMHL-2 A A C W D"

CBEACON delay=1:20 every=60 via=WIDE2-1 source="N7FMHL-2" infocmd="telem-eqns.pl N7FMHL-2 0 .025 -150 0 .01 0 0 -1 0 0 0 -4000 0 .1 0"

 

Now that it is working, I need to spend a little more time working on the data. I think I have 9 of the 10 channels working correctly. Channel B4 (PowerMeter) appears wonky. But, it could be because all the definitions have not been updated across APRS yet. Yep, time to build a Rx Test iGate!

 

Best regards,

Fred N7FMH

 

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Rob Giuliano via groups.io
Sent: Monday, August 16, 2021 8:53 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Telemetry mystery

 

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.

 

Rob KB8RCO

 

 

On Mon, Aug 16, 2021 at 18:06, Fred Hillhouse

“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: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Lynn Deffenbaugh
Sent: Monday, August 16, 2021 5:38 PM
To: APRSISCE@groups.io
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 groups.io wrote:

Lynn,

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

<snip>

_<sni<p>

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com