Caution Regarding Validated Login

[PeteSL]

Because this code is read-only, I recommend removing the passcode requirement and use -1 for the passcode. Use of a valid passcode for read-only connections can cause a server to block the connected station's packets (this is part of the q algorithm loop prevention on the server) and prevent multiple connections from the user (from different devices for instance). Using -1 for the passcode loses no functionality for read-only connections and simplifies interface requirements for users.

Hope this helps.

Pete AE5PL

[PeteSL]

Is this code being maintained? No one should use anything other than -1 for a passcode with this code as it is receive only. I am seeing multiple configuration issues connecting to my server because people are trying to use a valid passcode. -1 is the universal receive-only passcode which does not interfere with normal APRS-IS operations.

[bennybubble]

Is there any one using this code? Cannot get it to work.. No APRS coming in, could it be the server ? I'm in Europe so should it be possible to select a local server?

Ben

[ampledata]

I use it everyday Ben, Mind sharing your flow?

On Thu, Mar 17, 2022 at 10:54 AM bennybubble @.***> wrote:

Is there any one using this code? Cannot get it to work.. No APRS coming in, could it be the server ? I'm in Europe so should it be possible to select a local server?

Ben

— Reply to this email directly, view it on GitHub https://github.com/ampledata/node-red-contrib-aprs/issues/1#issuecomment-1071150746, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAWIXWLMJEUYPVBNT76YPTVANWWDANCNFSM4LNI3ZGQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Greg Albrecht @.***> W2GMD EMT. Disaster & Emergency Information Communications Technology (ICT) Specialist. Mobile: 1-415-598-8226 https://ampledata.org/ http://ampledata.org/ https://twitter.com/ampledata http://twitter.com/ampledata https://github.com/ampledata

[bennybubble]

Sure, here it is :

[{"id":"f7a1a7a5a8b13c9f","type":"aprs rx","z":"955ce123e2f7e94b","name":"PA3BWE-5","aprs_config":"34bf1f1c16cc25dd","x":140,"y":460,"wires":[["e418100abf68602b"]]},{"id":"e418100abf68602b","type":"switch","z":"955ce123e2f7e94b","name":"Discard Server Messages","property":"payload.raw","propertyType":"msg","rules":[{"t":"cont","v":"javAPRSSrvr","vt":"str"},{"t":"nempty"}],"checkall":"false","repair":false,"outputs":2,"x":350,"y":460,"wires":[[],["865ddfc2fceef12a"]]},{"id":"865ddfc2fceef12a","type":"change","z":"955ce123e2f7e94b","name":"Change Lat/Lon Payload","rules":[{"t":"set","p":"payload.lat","pt":"msg","to":"payload.data.latitude","tot":"msg"},{"t":"set","p":"payload.lon","pt":"msg","to":"payload.data.longitude","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":430,"y":540,"wires":[["f528d383aa086cd9"]]},{"id":"f528d383aa086cd9","type":"debug","z":"955ce123e2f7e94b","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload.lat","targetType":"msg","statusVal":"","statusType":"auto","x":760,"y":480,"wires":[]},{"id":"34bf1f1c16cc25dd","type":"aprs config","filter":"p/pa3bwe","name":""}]

Just want to know my coordinates, that's all!

Debug window:

3/17/2022, 7:59:13 PM[node: f528d383aa086cd9] msg.payload.lat : undefined undefined

[PeteSL]

Currently you have 2 connections to the server and your filter is filter b/pa3bwe (any callsigns with pa3bwe as the first 6 characters). Try b/PA3BWE or p/PA3BWE as your filter. This also means you must have a station transmitting that is being seen on APRS-IS (for instance PA3BWE or PA3BWE-5) for your client to see packets. I have double checked the code for filters and the callsign -is- case-sensitive.

[bennybubble]

Correct, I disabled one connection and my filter is set to p/pa3bwe. Also on aprs.fi I see messages coming in from pa3bwe-5 (through app on my phone) but I can not get the lon/lat in nodered In debug window msg.payload.lat remains undefined !

[PeteSL]

Please re-read my response. Use upper case for the callsign.

[bennybubble]

Yes callsign is uppercase!

[bennybubble]

[bennybubble]

Pass can be code or -1 for read-only, tried both (with proper pass) but no luck

[PeteSL]

Callsign in your FILTER must be upper case!

[PeteSL]

Filter should be p/PA3BWE

[PeteSL]

This has nothing to do with your client callsign/passcode. It has to do with your filter.

[bennybubble]

great working now, uppercase in filter did the trick !