New bug fix Beta 2023 09 04

[ve2wkr]

Daniel,
my location is in qrz , but aprs.fi has it as well most days.
I use an app on the phone which is within 2 min of the web site you sent me. For example , today sunset is at 19:22 according to the web site, my app says 7:24pm. I will pay attention to the radio , but I expect it to go dark by 17:22.
I will post results later tonight.
Thanks.
Luca

EDIT:
at my location putting in a time of 18:00 makes the radio switch to night mode. ( 17:59 ir day, 18:00 is night)
sunset is at 19:22, Last light after sunset is at 19:52

[F1RMB]

I ran after your location, but since we need to share accurate position, etc, better off doing this my email.


Cheers.
---
Daniel

[F1RMB]

I need to double check if something is not broken again with this...


Cheers.
---
Daniel

[VK3KYY]

It doesnt save code space, but just dopping characters doesn't give the same level of granularity

Possibly only 4 levels of ganularity is OK.

If you'd like it to function as many other radios and software packages do, then yes it is ok I haven't personally seen anyone use settings beyond 1 or 2.

I can't imagine its worth reporting with masking of worse than 1 deg of accuracy. 1 deg is 111km , at the equator.

Also using values as powers of 10 of a degree gives roughly steps of 100m 500, 1km , 5km etc

Whereas dropping characters gives valus of accuracy like +- 66m or +-660m I'm not sure how this translates into miles

I think 660m is a bit less than half a mile.

Yep your method certainly allows more flexibility. It just has no way to indicate to other stations that the position is ambiguous/masked. Deleting characters is the standard that things understand. Perhaps offer both options if it isn't a significant cost in code space? I'm also very comfortable with metric measurements so no need to worry about how it translates. I prefer metric as it is just easier math.

In my opinion I doubt anyone is going to set the ambiguity to higher then a single deleted digit for a handheld radio like this. I've attached a screen shot showing what that looks like from aprs.fi and you can also see your algorithm set to 0.0005 deg which is showing an odd track line because aprs.fi thinks it is a precise position. Neither position is actually where I am located, but my location is in the square.

I think if you offered the standard position ambiguity setting at level 1 and 2 it would satisfy the vast majority of people that want to use the setting. You are right that level 3 and 4 are just crazy large and only really make sense for someone trying to mask a digipeater location for some reason.

Sounds like this is different from the position masking and would need to be added as a separate feature

At the moment I don't know what the vast majority of people want because no one else commented about this

[kf4hzu]

Sounds like this is different from the position masking and would need to be added as a separate feature

At the moment I don't know what the vast majority of people want because no one else commented about this

Yes that's correct, it is the position ambiguity that deletes digits. I don't see any reason to rush to try and add it. Just renaming the current feature should solve any confusion.

As for what people want, is there a way to put up a poll?

On another note, I did some more testing and it looks like the RT3S AFSK modulation is about 15% lower then the lowest station which I can directly hear in my area. It is about 20% lower then the average. I still haven't gotten ahold of another radio but I wanted to provide this information for you. Would it be difficult to make the level user-configurable?

[VK3KYY]

Sounds like this is different from the position masking and would need to be added as a separate feature

At the moment I don't know what the vast majority of people want because no one else commented about this

Yes that's correct, it is the position ambiguity that deletes digits. I don't see any reason to rush to try and add it. Just renaming the current feature should solve any confusion.

As for what people want, is there a way to put up a poll?

On another note, I did some more testing and it looks like the RT3S AFSK modulation is about 15% lower then the lowest station which I can directly hear in my area. It is about 20% lower then the average. I still haven't gotten ahold of another radio but I wanted to provide this information for you. Would it be difficult to make the level user-configurable?

I already renamed it in the latest CPS to "Position masking"

viewtopic.php?f=12&t=3260

[VK3KYY]

Would it be difficult to make the level user-configurable?

Depends how you define difficult. Nothing is easy to when programming on small microcontrollers.

We would need a lot more data to validate whether its only your radio, or all radios etc, before even contemplating making changes

[kf4hzu]

Depends how you define difficult. Nothing is easy to when programming on small microcontrollers.

We would need a lot more data to validate whether its only your radio, or all radios etc, before even contemplating making changes

I'm happy to make the changes myself and do more testing if you can share the latest build environment or link to the repo.

[DG5YHS]

noticed error: If you swipe over the LED point in the settings, the device freezes completely (only battery out). After that, all settings are completely gone. The night and day change of topic does not work. I'm switching back to the old firmware August, September doesn't work at all.
Ich hoffe auf ein besseres Update. 74 DG5YHS

[VK3KYY]

noticed error: If you swipe over the LED point in the settings, the device freezes completely (only battery out). After that, all settings are completely gone. The night and day change of topic does not work. I'm switching back to the old firmware August, September doesn't work at all.
Ich hoffe auf ein besseres Update. 74 DG5YHS

Please explain more.

Which setting do you mean?

e.g. Options -> Display options -> ???

What do you mean "swipe" the radio does not have a touch screen.