开云体育

Do you mean: 1. Report _from_ your station _to_ APRS-IS, or 2. Report _from_ APRS-IS to your Internet client? Where "your station" is UIView32 or Direwolf. I know from experience that I-gate

Hi Andrew, but why does the station reports with uiview-32 sucessful, but with direwolf under openwebrx not? Alone because of the running time? I'm confused Original Message processed by

Uh, are we back with the misunderstanding and false assumption that APRS-IS can be used for propagation analysis? Remember, the APRS-IS _always_ discards all but the first-received (by the APRS-IS

But the received traffic can be seen in the screenshot of the console in the previous post? Original Message processed by david? Re: Fw: Re-4: [direwolf] Reporting to aprs-is shows no

Are you sure you have your sound card settings correct? Perhaps you have it set to an input you are not wired for? Have you also checked your cabling? Could be that you are not feeding AF to the

Hey all, New to Direwolf and APRS and for some reason I can't find out why my digipeater is not receiving packets. I am beaconing just fine and can see my position on aprs.fi (Callsign KE2ATV-10) and

I don't know what to say here other than aprs.fi is not showing any real heard traffic from your station. I would assume this is a levels issue with your SDR or an I/O issue between the SDR software

Nothing but mobile stations are reported to aprs-is. https://aprs.fi/info/a/DB0DAN Sry, but, what can I do?

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

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

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

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

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