CloudlogCAT / Interface to UDP-Messages #2786
Replies: 6 comments 13 replies
-
This should better be placed in https://github.com/rmc47/CloudlogCAT repo?! |
Beta Was this translation helpful? Give feedback.
-
But why do you need Omnirig? WSJT-X can directly CAT control your TRX. And there is WSJT-X improved which includes a patch by me to directly log to Cloudlog. See https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.7.1/. |
Beta Was this translation helpful? Give feedback.
-
Wonderful, thanks for this hint. I just installed 2.7.1. devel, added URL and API key. The API-test worked well and showed a green confirmation. |
Beta Was this translation helpful? Give feedback.
-
I just did exact what is described in the links, adding URL and API-Key, checking station-id. It fits. |
Beta Was this translation helpful? Give feedback.
-
Sorry, but... Test API key in WSJTX-271-dev is green, so i assume, that the data arrives at cloudlog. But Hardware-Interfaces doesn't list anything else than the "old" OmniRig1 and 2. Is there a chance to see or check, what cloudlog receives? [add] I deleted the old OmniRig1 and 2 to prevent showing old entries will hide new entries... but "No CAT Interfaced radios found." [add2] I restarted CloudlogCAT and when clicking on Hardware interfaces in Cloudlog the OmniRig1 appears after 1 sec., so connection between Windows client and linux server works properly. [add3] Just installed wsjtx271-dev on my Linux standalone and tried to get it working in cloudlog on remote-linux on my raspberry/BananaPi. But it showed the same error or better non-function. No hardware interface in cloudlog found :-( [add4] TCPdump on my linux-system logged a whole bunch of data, coming from my Windows-PC. Grepping for cloudlog a list of GET-requests will be shown, send from Windows to linux. So it seems, that wsjtx271dev works properly, but cloudlog couldn't handle the requests. shortened and cleanedup this is approaching my linux box (id changed to ....... for security issues and ip-address replaced by 192.168.x.xx.) |
Beta Was this translation helpful? Give feedback.
-
Ok, automatic loggig from WSJTX2.7.1.dev works. When logging QSO in WSJTX in the seperate window, a second later it's in cloudlog, when refreshing the screen. But having data an band, frequency, lsb/usb and so on is still missing, because no hardware interface is found in cloudlog. |
Beta Was this translation helpful? Give feedback.
-
Currently i've got the problem in running wsjtx (2.6.1.) and CloudlogCAT on a local windows client and Cloudlog on a remote linux-system.
When starting CloudlogCAT in local windows 10, it sets its communication via OmniRig to COM8 and interacts with my Icom 7300, with the correct API it pushes the data to cloudlog. So far so good.
BUT: Wsjtx also tries to use COM8 to communicate with the rig. Depending on what program starts first, either WSJTX or CloudlogCAT reports an error, that COM8 is occupied.
WSJTX has the possibility to get its data from device "Hamlib NET rigctl" via ip:4532 .
Otherwise WSJTX can also push the current information, received from the rig via USB, to port 4532.
So it would be great, if CloudlogCAT gets the possibility to connect to Port 4532 and listens to the data for beaming it to cloudlog without connecting via OmniRig on COM8 or so.
Or do i have a thinking problem in finding a solution to get these three programms running with data exchange between WSJTX, Cloudlog and - if necessary - CloudlogCAT?
Beta Was this translation helpful? Give feedback.
All reactions