![]() I selected OK and the CAT indicator on the rig flashed 8 times before going out. You should then connect to it as an existing instance. You’re about to start hamlib as a standalone process. ![]() I selected the button and a pop-up window appeared. This is accessed from Connect / CAT/ Show CAT interface and is the same as the one accessed through settings / program configuration / CAT interface but with the addition of a button marked “Open hamlib standalone” and to the side of it a green tick in another button. I came across a YouTube video last night that guided me to another configuration window for hamlib in Log4OM2. Sorry for the long post but I wanted to provide as much information as possible. I cannot find any information on the hamlib version incorporated in Log4OM2. I have now run out of ideas and I am hoping someone might be able to suggest why the hamlib 4.1 version communicates with the rig but the version used in Log4OM2 does not. ![]() I tried this with and without the –port=4532 parameter used in the Generated paramater string as I could not find any details on what this parameter does.Įither way the results were the same as with the original generated parameter string, the CAT light on the rig flashes twice and then goes off with just OFFLinE displayed.īetween tests of different software I rebooted the PC to ensure no stray bits of software were running and grabbing the serial port. Software versions were Fldigi 4.1.23, Hamlib 4.1Īfter doing a bit of research on rigctl I next modified the Log4OM2 Hamlib Used Parameter string to incorporate some of the additional parameters used in the hamlib 4.1 version used in FLDigi as below. Suprisingly this setup worked and the frequency and mode data were displayed and were controllable, but the response was slower than commander. Rig Yaesu FT767GX Stable, Port COM5, Baud 4800, 2 Stop bits, Polling interval 250ms, Timeout 3000ms, write delay 50ms, Post write delay 5 ms I noticed that in FLDigi different parameters are exposed to the user so I proceeded to setup Hamlib and test it. At this point I noted that Fldigi also supported HAMLib so I decided to look at the setup there. Next step was to install FLDigi to see if RIGCat would communicate but then discovered that RIGCat does not support the FT767GX. No frequency or other data is displayed just OFFLinE During this time the CAT indicator in LOG4OM2 stays solid green and then turns off. I then selected Connect / CAT/ Start CAT and the CAT light on the rig flashes twice and then goes off. This results in a Generated paramater string :. Rig Model Yaesu FT767GX Stable, Port COM5, Baud 4800, 2 Stop bits, DCD None, Polling delay 2000 I noted that OmniRig does not support the FT767GX so selected to use Hamlib. Having confirmed that the cable and comms work I proceeded to download and install LOG4OM 2 ver 2.26.0.0 This configuration works fine and I can control the frequency / mode etc from commander and it will read back the values if I change the controls or frequency on the rig directly.ĭuring operation the CAT light on the rig flashes at a rate of about 750ms I downloaded and installed DXLab Suite Commander and configured the comms as follows.ĬOM5 (the port used by the FT-Cable -3 indicated in device manager)īaud 4800, No Parity, 2 stop bits, DTR off, RTS TX, Command interval 200ms, scan dwell 1 I purchased a FT-Cable-3-USB from XGGcomms and connected it to my computer running Windows 10 I watched a series of youtube videos by CT2JKO where he serviced a FT767GX and finished off testing the CAT interface with DXLab Suite Commander so I decided this was a good place to start. I am trying to connect my Yaesu FT767GX to Log4OM2 in order to access the frequencency etc but I have not managed to get communications working and wondered if anyone can offer any advice.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |