-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection with Omnirig V2 to Xiegu G90 not working proper #479
Comments
It looks that it is the same issue as #473 |
But with Hamlib I habe an similar problem. So I try it with Hamlib an Experiment with it |
Besides the QLog poll interval, Hamlib also has own poll interval. Additionally, it may take some time to retrieve information from the radio. As I observed, there are many bugs in the G90 implementation in Hamlib. Unfortunately, due to Hamlib's release policy, I don't believe that these fixes will be included to the stable version in the near future I will have to think about what to do with this because Hamlib is not going to release a new stable release. |
我用FLRIG和QLOG配合良好 并且让N1MM支持FLRIG的需求已经提交 This method also applies to G90This method also applies to G90 I used FLRIG to work well with QLOG and the requirement for N1MM to support FLRIG has been submitted |
Hello, I want to connect QLog v0.39.0 with Omnirig v2.1 to my Xiegu G90.
Operation System is Windows 10.
I started Omnirig before QLog, as you mentioned in another Issue.
I can change the mode as intended.
But the Frequency is not updated, QLog shows
OOB
(see screenshots).I tried several diffrent settings in Omnirig and QLog but I can`t get it working.
I also tried it with Omnirig v1, but there is the same issue. I also verified, that the COM-Port is the correct one.
Or did I anything wrong?
If you need further infos, just let me know.
The Rig works fine with N1MM+ or the Winlink Client (both on Windows 10).
I also attached Screenshots with my settings.
The text was updated successfully, but these errors were encountered: