No send aprs data 路 Issue #3 路 g4klx/ircDDBGateway 路 GitHub 您所在的位置:网站首页 iz1mlt No send aprs data 路 Issue #3 路 g4klx/ircDDBGateway 路 GitHub

No send aprs data 路 Issue #3 路 g4klx/ircDDBGateway 路 GitHub

2024-05-31 16:57| 来源: 网络整理| 查看: 265

I have been having the same issue for quite a time. I thought it was because of the lack of a password. Now, with the new aprsPassword=[aprs-is] the same issue keeps happening: very very few positions are reported.

I have checked the logs and I get a positive login:

M: 2018-07-02 21:28:00: Starting the APRS Writer thread M: 2018-07-02 21:28:00: Received login banner : # aprsc 2.1.4-g408ed49 M: 2018-07-02 21:28:00: Response from APRS server: # logresp M0IEI-G verified, server T2FFL M: 2018-07-02 21:28:00: Connected to the APRS server

But the position reports do not appear in aprs.fi

Could the position reports to the aprs server and the response be logged? Just to be sure whether the problems comes from the server or the ircddbgateway side.

And by the way, it would be nice to have some switch to be passed to the daemon so that it do not log all the IRC announcements but only the daemon events.

---Update---- I have gathered more details... I have inserted logging traps in APRSCollector.cpp to see what was wrong and I got this:

M: 2018-07-03 22:04:45: Registered with dns.xreflector.net using callsign M0IEI M: 2018-07-03 22:04:45: Loaded 30 DCS reflectors from dns.xreflector.net M: 2018-07-03 22:04:47: CCS: M0IEI C connected to server ccs704.xreflector.net M: 2018-07-03 22:05:29: $GPRMC Valid M: 2018-07-03 22:05:29: M0IEI>APDPRS,DSTAR*:!5224.40N\015.152EK M: 2018-07-03 22:05:31: $GPRMC Valid M: 2018-07-03 22:05:57: $$CRC Bad checksum M: 2018-07-03 22:05:58: $$CRC Bad checksum M: 2018-07-03 22:06:25: $$CRC Bad checksum

22:05:29 was using NMEA(DV-G) sending RMC, GGA, GLL and VTG sentences

Then I switched to D-PRS(DV-A) with Timestamp=off, Altitude=Off and Data Extension=off and I got all those CRC Bad Checksum.

So now we now know what it is not working OK with ID-51 plus 2: the positions are no accepted by ircDDBGateway.

I have also tried to see what happens setting to ON the AutoTX position (with both DV-G and DV-A) and... nothing, nada, rien de rien. No Valid nor Bad CRC entires. IrcDDBGateway does not decode at all those position bursts. However, if you press the PTT for a bit, then you start to get the expected Valid positions or Bad CRCs. I finally understand why none of my bicycle strolls were recorded!

How great it would be if you could fix this, Jonathan!

73 de Pedro

----Update 2--- If you manually enter a position in the talkie, it does not send the longitude with all de required zeroes: Raw packets from aprs.fi:

2018-07-03 23:22:53 BST: M0IEI>APDPRS,DSTAR*,qAR,M0IEI-C:!5224.41N\00015.15EK117/000/A=000075 2018-07-03 23:47:53 BST: M0IEI>APDPRS,DSTAR*,qAR,M0IEI-C:!5224.40N\015.152EK [Unsupported packet format]

The same packets from the log traps...

M: 2018-07-03 22:22:46: $GPRMC Valid M: 2018-07-03 22:22:46: M0IEI>APDPRS,DSTAR*:!5224.41N\00015.15EK M: 2018-07-03 22:47:51: $GPRMC Valid M: 2018-07-03 22:47:51: M0IEI>APDPRS,DSTAR*:!5224.40N\015.152EK

The first one was generated with the position from the internal GPS and the second one came from the manual set position.

Could it be that the DV-A is dropping those zeroes so the Checksum gets messed?



【本文地址】

公司简介

联系我们

今日新闻

    推荐新闻

    专题文章
      CopyRight 2018-2019 实验室设备网 版权所有