I have previously built native windows versions of grig using the DevCpp environment. The result was a limited success since the resulting application only worked with the dummy backend.
Phew… what a rush! I found and fixed bug after bug after bug after bug… the worst ones were in the rig-daemon, where the read values were overwritten by the last set values every time the specific set command was executed. This was the case for PTT, POWER and FREQ, and so the old display flicker problem has been solved, too.
I’ve decided to look at the FT-817 backend tonight. There are some TODOs concerning the check of the TX level readings. I couldn’t do them before because I had only batteries to power the FT-817, thus tuning with 5W wasn’t really possible.
Today I received a reply from Stephane concerning my problems with the new hamlib debug handler api.
I have now tried to use the new debug handler API in hamlib but without any success. Some time ago, Stephane added some code to hamlib, which allows frontend programs to register their own debug handler, which then will be called every time a debug message is sent. The API uses the same parameter structure as the old hamlib API meaning that the handler will receive the comlete variable argument list that was originally sent to the rig_debug function.
This article gathers my previously posted blog entries concerning the FT-817 CAT. The blog entries have now been archived and are not available anymore; however, all info should be present in this article.