New MD2017/RT-82 Beta 2024 12 15

[VK3KYY]

Because the larger font size, added in the last Beta, was not universally liked, a new Beta is now available.

• This adds the "Text size" option to the Display Options. 1= normal size , 2 = larger size (double height), in for the Channel name, VFO Rx frequency and other parts of the firmware.
  The text size will default to the original / normal size.
• The Info setting has also been defaulted back to its original setting of "Off", as this was changed to "Both" in the previous Beta and possibly some users didn't want this to change.
• This version also has a fix for the intermittent button and keypad key problem experienced by a few users. Thanks to HB9GNB for his investigations into this problem.
• Add ability to store current GPS position in channel's Lat/Lon.
  - On GPS featured devices, editing the Channel details Lat or Lon, longpress the STAR key will store current GPS position (if GPS is on, and fix acquired).
• Add an option to disable any channel change (on Flash).
  - see "Locked: Off/On" in General options. When it's on, SK2 + Green don't write the changes to the flash.
• Fix APRS position conversion.
  - In some case, the conversion to minutes goes wrong, and ambiguity can make it worse.
• Fix DMTF entering and more:
  - it was impossible to enter DTMF sequences on MD-UV390/MD-2017/MD-9600.
  - A/B/C/D was unavailable in the numerical input.
  - Many problem while txing
  - it was impossible on most platform to navigate the contact (DMR/DTMF), from within Channel/VFO screen (no effect from Up/Down keys).
  - On MD-9600, While using the numerical input (DTMF), long press 'A' permits to exit that screen

downloads/MD2017/Firmware/dfb01ca3f824e ... 81bb04d63f

downloads/MD2017/Firmware/Latest

Most changes were developered by Daniel F1RMB

[CT7ARF]

After setup a fortnight ago it's working without a glitch. Including the screensaver...

Excellent work, as usual. Congratulations to you all, and THANK YOU!

Best regards and 73,

Antonio Cochicho
(CT7ARF)

[YO3IDG]

APRS position not updating.

Tried PTT, Auto and Smart modes, I can see the update on APRS.fi but the position is always the same (the one which was manually entered in the device).

It should use the GPS position(as per setting) but it does not.

UPDATE: tried on an DM1701 with openGD77 and it behaves similar (no GPS on that one), noticed it will only take the boot time "position".

[F1RMB]

Check your APRS configuration, maybe you defined a position there.
Also, the GPS position is sent only when a valid position fix is acquired.
Finally, does your transceiver has a GPS (the DM-1701 doesn't), and it's turned on.

EDIT:
I just checked your frames on APRS.fi, you're moving, a bit too fast

Code: Select all

2025-01-15 22:00:56 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:03:31 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!SS!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:05:40 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:13:24 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet?
2025-01-15 22:15:35 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:16:23 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet?
2025-01-15 22:20:02 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/5wI_U\]W[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:21:04 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/5wI_U\]W[  !Are we there yet?
2025-01-15 22:31:44 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]

[YO3IDG]

Check your APRS configuration, maybe you defined a position there.
Also, the GPS position is sent only when a valid position fix is acquired.
Finally, does your transceiver has a GPS (the DM-1701 doesn't), and it's turned on.

EDIT:
I just checked your frames on APRS.fi, you're moving, a bit too fast

Code: Select all

2025-01-15 22:00:56 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:03:31 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!SS!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:05:40 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:13:24 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet?
2025-01-15 22:15:35 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:16:23 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet?
2025-01-15 22:20:02 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/5wI_U\]W[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:21:04 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/5wI_U\]W[  !Are we there yet?
2025-01-15 22:31:44 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]

Yes, I've checked if a position is defined in the CPS (was the first thing I've fixed).

Even so, only the fixed position captured at boot is sent, with or without GPS.

I tried it on MD2017 and DM1701. On the 2017 I enabled GPS and drove around for a couple of hours, the position was never updated even if the packets were received and GPS had a lock.

The fast movements were obtained after I manually changed the position on the device and rebooted it.

[F1RMB]

Check your APRS configuration, maybe you defined a position there.
Also, the GPS position is sent only when a valid position fix is acquired.
Finally, does your transceiver has a GPS (the DM-1701 doesn't), and it's turned on.

EDIT:
I just checked your frames on APRS.fi, you're moving, a bit too fast

Code: Select all

2025-01-15 22:00:56 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:03:31 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!SS!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:05:40 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:13:24 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet?
2025-01-15 22:15:35 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:16:23 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet?
2025-01-15 22:20:02 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/5wI_U\]W[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:21:04 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/5wI_U\]W[  !Are we there yet?
2025-01-15 22:31:44 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]

Yes, I've checked if a position is defined in the CPS (was the first thing I've fixed).

Even so, only the fixed position captured at boot is sent, with or without GPS.

I tried it on MD2017 and DM1701. On the 2017 I enabled GPS and drove around for a couple of hours, the position was never updated even if the packets were received and GPS had a lock.

The fast movements were obtained after I manually changed the position on the device and rebooted it.

The "position at boot time" is the last one that was valid before turning off the GPS or the radio itself.
What are your APRS settings ?
Can you share your codeplug, and telling us the channel you're using for APRS beaconing ?
Also, are you sure to be heard by a Digipeater/iGate while driving ?

BTW, are you running the firmware version from the first post on this thread ?

[YO3IDG]

Check your APRS configuration, maybe you defined a position there.
Also, the GPS position is sent only when a valid position fix is acquired.
Finally, does your transceiver has a GPS (the DM-1701 doesn't), and it's turned on.

EDIT:
I just checked your frames on APRS.fi, you're moving, a bit too fast

Code: Select all

2025-01-15 22:00:56 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:03:31 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!SS!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:05:40 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/::!!T=!![  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:13:24 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/::!!T=!![  !Are we there yet?
2025-01-15 22:15:35 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:16:23 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/9et4U)m:[  !Are we there yet?
2025-01-15 22:20:02 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/5wI_U\]W[  !Are we there yet? [Location changes too fast (adaptive limit)]
2025-01-15 22:21:04 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,BIF1-1:!/5wI_U\]W[  !Are we there yet?
2025-01-15 22:31:44 CET: YO3IDG-10>APOG77,YO3KXL-10*,WIDE2-1,qAR,YO3GWM-11:!/9et4U)m:[  !Are we there yet? [Location changes too fast (adaptive limit)]

Yes, I've checked if a position is defined in the CPS (was the first thing I've fixed).

Even so, only the fixed position captured at boot is sent, with or without GPS.

I tried it on MD2017 and DM1701. On the 2017 I enabled GPS and drove around for a couple of hours, the position was never updated even if the packets were received and GPS had a lock.

The fast movements were obtained after I manually changed the position on the device and rebooted it.

The "position at boot time" is the last one that was valid before turning off the GPS or the radio itself.
What are your APRS settings ?
Can you share your codeplug, and telling us the channel you're using for APRS beaconing ?
Also, are you sure to be heard by a Digipeater/iGate while driving ?

BTW, are you running the firmware version from the first post on this thread ?

Yes I am running the fw version from the first post on this thread.
APRS settings in device are : PTT, Auto, Smart (cycling through them).

Yes the digipeater hears me, I can see the updates by comparing the last position field on APRS.fi.

Unfortunately, I only have one device with GPS.

UPDATE:
- after about 24 hours since last packet it seems to work, but...
- The location sent to APRS is different than the one reported in the device (both GPS and Status screens) about 100m different (approximated)
- in Auto and Smart mode APRS stops sending after about 3 minutes (rate set to 1 minute) is it listening to something, because reception is not always the greatest (this does not happen when I am close to the digipeater)

[F1RMB]

Yes, I've checked if a position is defined in the CPS (was the first thing I've fixed).

Even so, only the fixed position captured at boot is sent, with or without GPS.

I tried it on MD2017 and DM1701. On the 2017 I enabled GPS and drove around for a couple of hours, the position was never updated even if the packets were received and GPS had a lock.

The fast movements were obtained after I manually changed the position on the device and rebooted it.

The "position at boot time" is the last one that was valid before turning off the GPS or the radio itself.
What are your APRS settings ?
Can you share your codeplug, and telling us the channel you're using for APRS beaconing ?
Also, are you sure to be heard by a Digipeater/iGate while driving ?

BTW, are you running the firmware version from the first post on this thread ?

Yes I am running the fw version from the first post on this thread.
APRS settings in device are : PTT, Auto, Smart (cycling through them).

Yes the digipeater hears me, I can see the updates by comparing the last position field on APRS.fi.

Unfortunately, I only have one device with GPS.

UPDATE:
- after about 24 hours since last packet it seems to work, but...
- The location sent to APRS is different than the one reported in the device (both GPS and Status screens) about 100m different (approximated)
- in Auto and Smart mode APRS stops sending after about 3 minutes (rate set to 1 minute) is it listening to something, because reception is not always the greatest (this does not happen when I am close to the digipeater)

Hmmm, I asked you about many details, but you only gave a fraction of answers.
I won't waste my time asking, over and over, for details if you're not inclined to give them.
Also, I think you don't know how SmartBeaconing works, hence I suggest you to document yourself about it, and read the OpenGD77 user manual too.

[F1RMB]

I tested APRS with my MD-2017 this morning, it works as expected:
https://aprs.fi/#!z=11&call=a%2FF1RMB-7 ... &tail=3600

[TA5TX]

I have a problem with APRS. Even though I tried all kinds of options, I could not send the location. It sent neither the location at a fixed location nor the location on GPS. Can you tell me what I should do?

Ekran görüntüsü 2025-01-19 044653.png (9.72 KiB) Viewed 106 times

IMG_20250119_045039 (2).jpg (34.25 KiB) Viewed 106 times