What seems to happen is that the FY unit does not respond to the 'a' message when it is on BT (this works on on cable). The mod to the code avoids the software thinking it is in error, but it is probably not recommended for wider implementation.
Hi Marco,
Thanks for keeping me posted.
The 'a' command is the only way I have found to check the connectivity, as the feeltech is supposed to answer by returning the model name. Perhaps the BT connexion does not support this two way communication.
As you said, it is probably not a good idea to remove/bypass connectivity check.
But, OK, if you are satisfied with the modification you have done, all is well that ends well.
I have the model FY6600 ,I did try it with your software but no luck , would it be possible to put the FY6600 serial command set into the software you created ?
Hello soundtec,
I would like to please you, but I do not think it would be reasonnable to try to adapt the software for a FY6600.
This has been wrote in a kind of quick and dirty way, just to cover my needs regarding the device I own.
FY32 and FY66 are quite different, so that's not only about replacing the serial commands. For instance, FY66 has the ability to sweep voltage and frequency while FY32 is limited to frequency sweep. So there is nothing in the GUI which I can recuperate to implement the extra commands needed for the FY66.
Another issue is that, due to the poorly documentation provided by the chineese manufacturer, a lot of programing requires discovering how it works by trial and error and/or reverse engineering (This said, the FY66 documentation looks better than those of the FY32). As a consequence, it is nearly mandatory to have a device available to develop/test; which is not my case.
But, who knows, perhaps I will buy one FY66 and develop a new software for it...
I see there is also another group on this blog which aim to improve the FY66. Perhaps you can find what you are looking for there :
Wish you the best.
Yves