开云体育

The command line options could be explained better.? This has been added to the list for future enhancements. How could the user guide be organized better?? Helpful suggestions are always welcome.

You can use the decode_aprs utility, included with direwolf, to interpret the meaning. Example: echo 'KR5LM-14>APX219,WIDE2-2:=2948.47N/09533.42Wx' | decode_aprs Position, xAPRS (Unix), Xastir N 29

One problem may that you are not using plain ASCII double-quotes (Unicode character \u0022). Note that your config file text below shows Unicode characters \u201c (left-leaning quote) and \u201d

I didn’t have a spacing problem but I did have a quoting problem combined with a syntax problem. I can now tell the world at least the macOS 13+ world that to configure a iMic you have at least two

I will indeed go read that however I am NOT using OSX I am using macOS Ventura 13.2.1 a much newer OS than the old OSX versions. I’ll check the device names link you suggested and see if that helps.

Hello Keith, There was a very similar discussion about OSX and sound device names vs. capitalizaTION issues. Give this a read: /g/direwolf/topic/96051727 --David KI6ZHD

HI David and thanks for responding. The thing is I added the '-' stuff as an additional test, which we now know failed. Usually I attempt to start DW with "keithkaiser@dulcinea ~ % direwolf -c

Hello Keith, Your issue stems from the "-" (dash) character on the command line just after the timestamp parameter. Please see the Direwolf User Guide section 9.1.4 (

I’m feeding the output of my IC-7000 to a iMic, the MacBook Air sees the device and I can see the VU meter responding to APRS signals. I’m attempting to launch direwolf like this;

Hello Geoffrey, Oh, ok.. I had understood that all compressed packets used the MIC-E format but I guess I'm wrong. Thank you for the correction. I'll openly admit that the use of "WIDE1-1" only vs.

David, 1) You are mixing up Mic-E and compressed position. In mic-e the destination field is used to convey part of the position data and looks like random letters. In compressed position reports the

Patrick, I did to get the time stamp addition, and after reviewing the User Guide, and --help, found the screen color settings which were also helpful. Can't say much for how the user guide is

Use upper case letters for this command. Patrick (N3TSZ)

Thank you, sir. This was the part I was 'missing' and your example has been helpful. I also found the '-t' option for terminal colors, I cannot see things on the white background easily, so switched

To add on to the good responses Thomas and Rob already covered, three more things: 1) since you can read the "APX219" packet destination in clear text, that means the packet is a non-compressed APRS

This is covered in the Direwolf User Guide but when you start Direwolf from the command line, try adding this: -T "%H:%M:%S" --David KI6ZHD

Excellent software, just having a 'minor' issue, and probably just missing it in the docs somewhere: Is there a way to turn on a timestamp in the console feed? When I run direwolf I get the following

To add a little detail on what it means, check out the APRS101.pdf document: http://www.aprs.org/doc/APRS101.PDF Anyone using APRS should have a copy handy. The only part that isn't in there is the

Hi Randy, This means your station (KR5LM-14) transmitted on Channel 0 (first channel) with Low priority an APRS packet to APX219 via WIDE2-2 followed by the coordinates for the geographic location of

[Received this code when I started up direwolf 0L] KR5LM-14>APX219,WIDE2-2:=2948.47N/09533.42Wx What does it mean? 73's Randy