Zoltan, If you plan to use a decoder assembled according to the scheme from the firmware package in the ATS120 receiver, then before installing the decoder in the receiver, change the following lines in the setting.ini file (just delete //)
Then download the receiver file.
After restarting the receiver, the reading mode will be enabled on the specified ESP32 pins.
The decoder circuit was designed by Antonino Russo. If you have any questions about it, you can ask them in the Facebook group: https://www.facebook.com/groups/532613604253401
The term 'pin' stands for GPIO pin, not actual physical pin on the ESP32 module, right?
Because say Pin32 on the module corresponds to GPIO07, which does not have an ADC.
Conversely, GPIO32 is Pin12 on the ESP module, which has an ADC channel listed.
Is the audio signal on a Vcc/2 offset? i.e. 0 and Vcc/2 are treated as negative, and Vcc/2 to Vcc are treated as positive?
Are you exclusively relying on the LM556 to decode digital signals and just using the audio for spectrum display?
Zoltan, Yes, indeed, all PIN numbers are indicated in relation to the GPIO and not to the pin number of the microcontroller. As I said earlier, you can get answers to questions about the operation of the decoder circuit from the author of the circuit in a Facebook group. I can only say that when the ADC is running, values from 0 to 3.3 volts are used. A frequency detector is assembled on the LM567 chip, which helps to decode some types of digital signals, as well as Morse code. Audio data is also used in decoding, not just for spectrum mapping.
Hi #Binns,
I dont have enough skills to add another pcb into the receiver and make the recommended connections.
Do you think I will face problems if I upgrade to the latest software? if yes, how to bypass the popup on the opening screen.
My receiver is ATS25 X1.
EreM, Every next update is fully compatible with the hardware. If there are no modules used by the firmware in your receiver, then these functions will simply not be involved. And do not forget that the updates not only contain new features, but also correct the errors found, as well as expand the functionality and improve the work without the need to modify the receiver. Therefore, installing updates is strictly recommended.
dear developers, could you in future versions of the firmware for the ATS -120 receiver, implement the operation of the s-meter in SSB mode on kV bands, at the moment it only works in fm, and also use a virtual encoder, and instead of demonstrating the frequency in sleep mode, in the screenserver, place the clock,
Potan писал(а): ↑21 авг 2023, 13:10
dear developers, could you in future versions of the firmware for the ATS -120 receiver, implement the operation of the s-meter in SSB mode on kV bands, at the moment it only works in fm, and also use a virtual encoder, and instead of demonstrating the frequency in sleep mode, in the screenserver, place the clock,
Please explain which S-meter SSB we are talking about? And what does it mean: only works in fm.
The virtual encoder works on all devices with the H-RADIO firmware installed. Calling the virtual encoder by swipe up from the bottom of the screen.
The screensaver displays the clock and frequency alternately, only if the time data is received via RDS or the Internet.
When receiving amateur stations on HF bands, in ssb s mode, the meter shows only the noise level, and does not respond to the difference in signal strength of amateur radio stations. When receiving FM stations, the readings change depending on the signal strength. As for the virtual encoder, it is impossible to activate it in the way you described, although this really happens in the video of firmware 4.15. I have firmware 4.16.
Potan писал(а): ↑21 авг 2023, 17:58
When receiving amateur stations on HF bands, in ssb s mode, the meter shows only the noise level, and does not respond to the difference in signal strength of amateur radio stations. When receiving FM stations, the readings change depending on the signal strength. As for the virtual encoder, it is impossible to activate it in the way you described, although this really happens in the video of firmware 4.15. I have firmware 4.16.
Binns, thanks, I figured it out, everything works, I just have a thick protective film on the display because of this, the sensor sensitivity is worse than on other buttons.
