开云体育

You both are just wealths of knowledge here. I will be apologizing at multiple points for what I see as very 'noob' questions. I am just so grateful to have someone know what I'm talking about. The?

Hi Cassie (and David) The 9100 effectively has a sound card and 2 serial port UARTS on the end of its USB hub, so only the USB A-B cable is needed. Re the audio, I think it worthwhile for initial

Hello Cassie, A great way to learn and you've come to the right place. Lots of very smart users, developers, etc. are here on this list. I would say that once you start direwolf and start decoding

Thank you both for the reply. I inherited this project (with of course zero knowledge of any of this) and am trying to make sense out of what they had started (granted none of their set up was working

Hello Cdres, I agree with VK2YQA that if your radios have built-in sound devices, you should use those and NOT use anything external like a RigBlaster. Yes, they can be made to work but it only will

I quite happily use direwolf on my IC-9100 HF/30m without issue. I am however using the USB port connection rather than the Aux2 port. Indeed it may be worthwhile removing the rigblaster from your

Hello, I am currently trying to get our ic-9100 radios connected via direwolf and a rigblaster plug and play to our ubuntu computers. I have successfully gotten the config files set up and have

Yes I am hearing positions from the digi itself as it transmits (rfonly) its own position every 30 minutes. I built the digi on the mountain top and I have a test installation where I test changes,

Per chance, have you ever heard a position report from the digipeater itself, about the digipeater itself? There is a concept in APRS called vicinity plotting, where the location of a station that

Gentlemen, This is interesting because I noticed when using Direwolf with Xastir on Linux Mint, if I use DW 1.8 with the AGWPE interface, I see the "<0x00>" (the ASCII NUL character) at the end of my

Ahh. I had missed that part of the spec. I've learned something new. To your original question. It appears the answer is yes, there was a time when the message id could get the '{' overwritten by a

The mountain-top digis are running development version 1.7B from Nov 21.? According to 1.7 release information: * Packet filtering now skips over any third party header before classifying packet

Is this request going anywhere? I want to differentiate between messages and objects within third party packets received by a mountain-top digi, which I could do using budlists if the test applied to

Yes, I am intimately familiar with the APRS message packet format.? The question was if anyone recalls what IGate software had a buggy version that was replacing the open curly brace with a null

Lynn, I don't think any of those are in a valid APRS message form. Someone chime in if I'm mistaken. The format of the sequence number should be {XXXXX An open curly bracket followed by 1-5

I don't remember where I read about it, but there was somewhere a mention of software that was nulling out the { on message identifiers on gated packets.?? There is a discussion on the QTHapp google

Thanks John for reminding me of the reason for the high priority transmissions. My local scene is that my tx igate constantly hears 6-7 mountain-top digis from up to 200 km away of which 4-5 are older

In this context, the priority is based on whether the packet is being digipeated or not. Please take a look in https://github.com/wb2osz/aprsspec and read section 5.2 of APRS-Digipeater-Algorithm. 73,

It doesn't seem appropriate that messages are generally considered high priority yet messages from the igate to the radio are sent to the low priority transmit queue. (TQ_PRIO_1_LO in igate.c at line

I did not include any HDLC.