pavelmc / ft857d Goto Github PK

Some users needs to use the real serial port in arduino to debug purposes, and there is a chance to port this to sotware serial.

The example sketch is not showing, I'm investigating this issue.

The FT-8x7 series is capable of setting and reading frequencies with 10Hz resolution. I looks like the frequency is passed and read back with only 100Hz resolution(?), at least that's what I see when I print out the value of "freq" to an attached OLED display. If this is the case (and I'm not misinterpreting what I see) would it be possible to add an option, or modify the library, so that frequency is passed and read with 10Hz resolution.? I have looked at the library, but I have not yet figured out exactly what's happening and what might be changed to allow 10 Hz resolution.

If I set the initial value of "freq" with 10Hz resolution in the test program and read it back using my routine for the OLED display before any CAT commands are sent, I see the 10Hz resolution value, so I'm assuming it's the CAT library that's rounding things off (or truncating) to 100Hz.

Thanks in advance for any help with this.

I I try ft857d but not work.

I'm using ardunio nano, arduino IDE 1.8.16, OS linux Ubuntu 20.04.
The ft857d.ino pass by verification, and is upload ok.
I dont know , how to debug.
The test was done with flrig, fldigi.
Any hint will be good.

I had to modify lib ft857.h (line 107) prototype to:
void begin(long baudrate, SerialConfig mode); // custom baudrate and mode
and in ft857.cpp (line 55)
// Alternative initializer with a custom baudrate and mode
void ft857d::begin(long br, SerialConfig mode) {

Otherwise, compiler complains about int type not being type SerialConfig. This is only for the ESP8266. Not actually tested with a rig but at least now it will compile. I'm certain this has something to do with the esp8266 core because the original lib/example compiles for esp32 and UNO.

as a library, CustomSoftwareSerial should work without problems - https://github.com/ledongthuc/CustomSoftwareSerial

Forgive me if I'm missing something, but I can't see howto get the debug feature to work. As far as I can tell, the library is written using the on-board serial port. So communication from software running on the PC uses this Arduino port to talk with the simulator. That works just fine.

However if debugging is enables, the debug messages also try to use the same serial port to talk back with the Arduino IDE for display in the serial monitor window. If the software on the PC which is talking with the emulator has control of that port, then the Arduino IDE cant access it. Indeed if I enable debugging I get an error message "Error opening serial port 'COM19'. (Port busy)" showing the port is unavailable since it's in use.

If I want to use the serial monitor function in the Arduino IDE, it appears I would have to rewrite the library using, for example, the serial1, serial2 or serial3 ports of an Arduino Mega or a software defined port on a Uno. Alternatively I guess I could change the debug commands to use a different serial port and use some other terminal emulation software hooked up to that port.

Am I missing something here, or is this the way it works. Perhaps the program I have talking with the emulator is holding onto the serial port when it shouldn't? I'm not all that familiar with techniques for sharing a serial port between multiple programs (which I did not write!).