It would be useful to have the possibility of separate settings for transverter offset for RIG1 and RIG2 (different offsets and on / off).
Example;
(RIG1) SHF radio and transverter offset ON.
(RIG2) HF radio, transverter offset OFF.
Thank you!

As mentioned in the other issues linked below, it seems that those not in GMT may have trouble getting CloudlogCAT to successfully sync with Cloudlog since this commit: magicbug/Cloudlog@b18e101

magicbug/Cloudlog#1240

magicbug/Cloudlog#1236

I've rolled back the Cat.php file to a previous version to regain that sync ability, but wanted to flag in case it was an easy client fix in CloudlogCAT.

Omnirig connected and works fine.
API Keay from website generated and entered.
URL also filled in.

Error message: Cloundlog Synced: Feiled, check URL/API

Cloudlog runs on a webserver with https and the main folder is htaccess protected with a password.

Installed omnirig and CloudlogCAT but noticed that CliudlogCAT is not passing through the frequency.
Omnirig is passing through the frequency in other applications so thare is not the problem.

I'm not sure what format the Cloudlog URL setting should take - it seems like it needs the "/api/auth/" portion of the API address to have a successful sync message?

Additionally, once I'm able to get the successful sync message, I'm not able to actually find the corresponding radio within Cloudlog. I may be missing something obvious!

Actually I seems like CloudlogCAT is not compatible with OmniRig V2.

There is a fork from W3AXL but maybe you could an implementation to the main repo?

Vy 73 de HB9HIL

Hi,

I noticed in the code and in operation that if OmniRig is reporting LSB or USB mode, then this only get's reported as 'SSB' due to the code here: https://github.com/magicbug/CloudlogCAT/blob/Omnirig/OmniRig_VB_DEMO/Form1.vb#L115-L118

Also noticed seems to be some artifacts left over in this file from merging?

If there isn't a reason for the mode mapping - i'm happy to do a PR?

Thanks,
Jordan