Keyboard Shortcuts
Likes
Search
Direwolf Command Line Options
Hello... Since updating to the newest version (1.4d), ?i have been getting telemetry error messages on decodes. ?Starting it like this: ?[steve@localhost ~]$ direwolf -p -qd Here is an example... Digipeater VE1JOT-5 audio level = 33(14/13) ? [NONE] ? _||||__ [0.2] EI2GYB-3>MBX,VE1JOT-5*:Mail for: W6OAV VA3HRA KO4OP UZ7HO [0L] KB9PVH-7>LINBPQ,VE1JOT-5,EI2GYB-7:Temp:10.4F<0x0d>Wind:SSE @ 4 mph ?<0x0d>UV: ? N/A W/m2 - Rain:0.00 in<0x0d><0x0a> Digipeater VE1JOT-5 audio level = 31(15/14) ? [NONE] ? _||||__ [0.2] KB9PVH-7>LINBPQ,VE1JOT-5*,EI2GYB-7:Temp:10.4F<0x0d>Wind:SSE @ 4 mph ?<0x0d>UV: ? N/A W/m2 - Rain:0.00 in<0x0d><0x0a> Error: Information part of telemetry packet must begin with "#" VE1JOT-7 audio level = 32(14/13) ? [NONE] ? _|||||_ [0.3] VE1JOT-7>ID:NS105:VE1JOT-7 FN74pb I am using this with LinBPQ and the data is a simple text weather beacon from generated from my weather station here. ?It does not seem to be creating any problems, but i did not have the issue with the earlier version of 1.3... 73, ? --steve,kb9pvh-- p.s. ?It seems to be working fine otherwise.... |
David Ranch
开云体育Hmmm... this VE1JOT-5 station is gating non-APRS traffic which Direwolf is complaining about: ? #It didn't complain about this packet for some reason but this is not an APRS formatted packet ? [0.2] EI2GYB-3>MBX,VE1JOT-5*:Mail for: W6OAV VA3HRA KO4OP UZ7HO Maybe Direwolf 1.4 is more strict about non-APRS formatted packets that v1.3 because of it's enhanced telemetry support.? Curious, are you using any FIX_BITS settings??? If you are, there is an option to train the bit level repairs around APRS formatted strings.? If you like to see these On 12/16/2016 06:40 AM, steve phelps
kb9pvh@... [direwolf_packet] wrote:
? |
开云体育Here is another one: KB7ITU audio level = 30(15/14)?? [NONE]?? _|||||| It only seems to be my station and this one..?? wonder if it has something to do with the letter T at the beginning of the data line maybe ???
73,?? --steve,kb9pvh-- =============================================== On 12/16/2016 08:40 AM, steve phelps
kb9pvh@... [direwolf_packet] wrote:
? |
Short answer: The fix is now in the "dev" branch. ?Just ignore the error message until you get a newer version. ?It doesn't hurt anything. Explanation: When using APRS, the first character of the information part of the field is called the "data type indicator." ? "T" indicates telemetry. ?In this case the following character should be "#". ?This message would be appropriate when using APRS. ? However, it looks like you are using traditional packet radio. ?Here the UI frames (broadcasts, not to a particular station) can have any text without any formatting rules. |
Indeed...? that makes sense.? Yes, i am using the direwolf modem
in a traditional packet enviroment.? It has been performing extremely well on hf.?? Tnx for the explanation and fix... 73,? --steve,kb9pvh--
Sent from
On Dec 17, 2016, at 8:20 AM, "wb2osz@... [direwolf_packet]" <direwolf_packet@...> wrote: ? |
开云体育Howdy David.. It is not gating aprs traffic because i am not using it on APRS here..?? Using it as a traditional packet station on Net105 for 300 baud hf with LinBPQ.? A fix was issued, which is working great as well.?? Tnx for the response though.... 73,? --steve,kb9pvh-- Packet: 14.105 (LSB) ARDOP: 7101 (USB) On 12/16/2016 10:50 AM, David Ranch
dranch@... [direwolf_packet] wrote:
? |