bug version 2.10 frequencies

[ea8ee]

He installed the latest version of FreeDV 2.1.0 while the frequencies were predefined and the error appeared in the numbers and frequencies for the band

Enviado con Mailsuite  ·  Darse de baja

22/11/25, 07:25:45

[Walter Holmes]

I’m sorry, but I don’t think I quite understand what the error is here.

 

Do you happen to have a picture of what it looks like?

 

What type of radio is being used, and is this Windows, or some other operating system?

 

Thanks,,

 

Walter/K5WH

--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/CADJ3RdTRLiC-zv0CDRwKP73Y1dSQ6RzT_fV_H-tcFBZ7eyy-BA%40mail.gmail.com.

[ea8ee]

Hi Walter,

Thanks for the reply.

The issue appears after installing FreeDV 2.1.0 and using the predefined band frequencies. On the station that reported the problem, several of the predefined frequencies show incorrect numbers in the band list.

uso ft-991 with the previous versions works perfectly with the 2.1.0 I.ve mistake  included in the freedv reporter web the reading of the frequency is not correct
73

Jose

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/012e01dc5b95%24a65fe770%24f31fb650%24%40k5wh.net.

[ea8ee]

[Walter Holmes]

Many thanks for the picture there, with the NEW 2.1.0 software,

 

If I understand you right, your friend no longer has CAT or rig control.  Meaning, he can’t select a frequency from the pull down list, and have the radio change to that?

 

If the CAT control is set to the correct com port and the baud rate matches, then it could be an issue with the latest Hamlib set that is being used today. We have seen that before when that has been changed.

 

And this is an FT-991, NOT an FT-991A, correct?

 

Perhaps we can find someone else also that has this radio type to verify that it’s a Hamlib problem, and take action on that. As I know it’s a popular radio, so there should be others having this problem as well.

 

 

Thanks,

Walter/K5WH

--

You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/CADJ3RdTRLiC-zv0CDRwKP73Y1dSQ6RzT_fV_H-tcFBZ7eyy-BA%40mail.gmail.com.

[Babis Charalabopoulos]

I have the same problem, and I am using Vox. The paradox is that the older version was working fine without these issues.

Babis sv1uh

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/000001dc5bc0%2458af1570%240a0d4050%24%40k5wh.net.

[ea8ee]

Hi Walter,

Thanks for the reply.

Yes, it is an FT-991, not the FT-991A.

The problem we see is with the predefined band frequencies and the value sent to the FreeDV Reporter web page after installing 2.1.0. The numbers shown in the band list and in the reporter are not correct.

I use omnirig with the same result

Jose

[Mooneer Salem]

I think I missed it in previous emails, but what version are you guys upgrading from? 

-Mooneer K6AQ 

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/CADJ3RdSbOo8i0cvyNsZR_W901%2BQTuybr7YrYexrgC8Tr4_1XWg%40mail.gmail.com.

[Walter Holmes]

This I very good feedback, as it does seem to point to a possible issue with the latest Hamlib controls, as those get changed every few months as they add in newer radios.

 

Some have has success with changing to a different radio model, of the similar age from Yaesu.

 

I wonder if he could try a couple different radios to see if one would work. Then we could report that to the group that manages the Hamlib libraries.

 

Tnx.

Walter/K5WH

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/CABA5UfZ_Y26%2Bo7kqBdusAUjc9z2caZyPMCU5KU%3DmrzDtVdSYnw%40mail.gmail.com.

[Mooneer Salem]

I looked at the changelog and Hamlib was last updated for version 2.0.2 (to version 4.6.5). Before that, 2.0.1 had version 4.6.3. It would be good to know what version was being upgraded from so we can do more testing and confirm it's not something with FreeDV itself.

-Mooneer K6AQ

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/008d01dc5be7%24158d7f80%2440a87e80%24%40k5wh.net.

[Axel Schünemann]

Hello everyone, I'm having trouble with frequency selection from version 2.1.0 onwards with both the Yaesu FTDX10 and the FT818.

It doesn't matter whether I use Hamlib or OmniRig. However, I've found a workaround: I set the input to kHz and simply enter the

frequency into the selection field. 73 de Axel

[Text with Google Translator ;-)]

[Jose Eugenio Maison]

Hola José Manuel lo único que tienes que hacer es colocar correctamente la frecuencia en el apartado de frecuencia lees la cantidad de megaciclos una coma los después los ciclos y un cero al final o sea si es 14, 236 0 y debiera aparecer en el en todos lados inclusive en el en el cat

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/a711e2c4-396f-46a5-94a0-84b800e8fc70n%40googlegroups.com.

[Mooneer Salem]

Hi Axel,

Can you try resetting your configuration to defaults (Tools->Restore defaults) and letting me know if that helps at all?

Thanks,

-Mooneer K6AQ

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/a711e2c4-396f-46a5-94a0-84b800e8fc70n%40googlegroups.com.

[Axel Schünemann]

Hi Moneer,

thanks for the feedback.

I tried it and it looked good (Screenshot 01). Then I adjusted the audio settings (Screenshot 02). So far, so good. PTT settings (HAMLIB, FTDX10) OK. FreeDV Reporter activated, also OK (Screenshot 03). Then I adjusted the settings options (Call, Locator) and clicking "Apply" changed the frequency list (Screenshot 04).

I hope this helps with troubleshooting.

73 de Axel (DL8BBK)

[Axel Schünemann]

Hi Moneer,

thanks for the test version 2.2.0. It has the exact same problem. I reinstalled version 2.0.2 and it works perfectly.

If you enter a frequency in the options menu and press the "Apply" button several times, you can clearly see the

frequency entries changing, even though no further input is made.

73 de Axel (DL8BBK)