You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if it would be possible to implement a CAT interface via USB or UART (in such case via a MAX232 adapter) to pilot the radio from a PC.
I don't know if the Arduino while running the radio-code can also "listen" to the USB or to the UART and run some function, like on old microcomputers the UART I/O was triggering an interrupt that could be trapped.
Or maybe in the main loop we still have some milliseconds to spare?
Would that be technically feasible?
The text was updated successfully, but these errors were encountered:
Yes, it is technically feasible to implement a CAT interface via USB or UART to control the radio from a PC while using Arduino. The Arduino can run the radio code and also listen to the USB or UART for incoming commands. Arduino has two pins (0 and 1) that can be used as UART. You can have your Arduino code run in a main loop where it listens for incoming Serial commands and also manages the radio, for example with the SI4732. If you have a device that supports UART but not USB, you can indeed use a MAX232 adapter to interface it with the Arduino. The Arduino can then listen for incoming commands on its UART pins.
Thanks for your reply!
In such case I'll start working on adding a MAX232 to the Arduino nano of my ATS-20+, and write just enough code to read the frequency and write it to the UART...
My idea would be to re-implement a well known CAT protocol (e.g. Yaesu FT-857D?) so we can reuse tools like flrig without having to change much.
Hi guys,
I was wondering if it would be possible to implement a CAT interface via USB or UART (in such case via a MAX232 adapter) to pilot the radio from a PC.
I don't know if the Arduino while running the radio-code can also "listen" to the USB or to the UART and run some function, like on old microcomputers the UART I/O was triggering an interrupt that could be trapped.
Or maybe in the main loop we still have some milliseconds to spare?
Would that be technically feasible?
The text was updated successfully, but these errors were encountered: