![]() Before adding a new product use the "Search" tool on reviews Home page to determine if that product already exists in a category.Ĥ. The delay can vary from minutes to a day or more.ģ. The delay is for new review screening and approval. There's a delay before newly submitted reviews are Approved and posted in eHam's reviews. eHam's Product Reviews are a database of ham radio related products and services personal opinions.Ģ. And to top it all off, Don Agro's response time to my few technical email questions has been shockingly fast and on target every time. I do not want to be forced to run a Windows PC or Windows VM just to do Ham Radio logging, and it is a huge help to me that I can use MacLoggerDX natively on the MacOS. I really appreciate using the MacLoggerDX on an iPad while operating portable from my car. It is super helpful to me to be able to use MacLoggerDX on a MAC because all my main computers are Mac. I use Mac products and Windows PCs extensively, and for a multitude of reasons, I prefer to primarily use the MacOS and run Windows Virtual Machines using VMWare or Windows PCs as needed. The User Interface, breadth of options, and SQL database on MacLoggerDX put it in a class by itself among excellent competition. I am an automation controls engineer and use software of all types for my job. I am continually amazed at the features in MacLoggerDX. This can be usefull when working a remote radio through SmartLink since MacLoggerDX will not need a radio connection of it's own and will log the frequency and mode sent to it by dogparkSDR.Wow. If the Tune MLDX check box is enabled in the Radio prefs, MacLoggerDX will automatically track the active slice frequency and mode without being connected to the radio. Unlike dogparkSDR, MacLoggerDX does not support remote connection over SmartLink but you can use xCAT for remote connections or allow dogparkSDR to “ Tune” MacLoggerDX for logging. WSJT-X get’s the audio from the radio through dogparkSDR and LoopBack. In my setup WSJT-X controls MacLoggerDX and the Flex through the MacLoggerDX DXLab TCP server. If any client changes the state of a slice - that change is reflected in the other clients - including MacLoggerDX. MacLoggerDX tracks the selected and Transmit slice directly and within the limits of the slices it has access to, and can set the active and transmit slice as well as the frequencies and modes - independently of what other GUI clients are doing. If you set the radio to split through MacLoggerDX then MacLoggerDX will ask the radio for a second slice - if one is available. MacLoggerDX will show every slice it has access to in its VFO popup and you can select the active slice from it. (MacLoggerDX Radio prefs - SmartSDR Radio spots).īefore the Flex Radio server could store and forward spots to clients for display MacLoggerDX v6.19 developed the capability to feed spots directly to dogparkSDR in (MacLoggerDX Radio prefs - dogparkSDR spots) MacLoggerDX can however feed the Radio server Spots data. This was only possible because the Flex 6000 series was developed from the start to be a platform-agnostic client-server radio. I’m not positive but I think it was the first logger on any platform to do so. No other Flex client feeds MacLoggerDX data of any kind, MacLoggerDX connects directly to the Radio server over the LAN as a non-GUI client and has done so since MacLoggerDX Version 5.49 in 2013. Or between SmartSDR/Maestro feeding data to a Mac for use with MacLogger. I have cross-posted this to the MacLoggerDX Group. This is really a MacLoggerDX question since dogparkSDR, or Maestro, or SmartSDR Windows, or SmartSDR iOS aren’t involved directly in the CAT connection between the MacLoggerDX non-GUI client and the Flex Radio server. The MacLoggerDX Radio prefs include a popup list of GUI clients currently connected to the Radio server. They are independent clients to the radio server - but with the advent of multiFlex, each non-GUI client must be associated with a GUI client. I’m also not familiar with the degree of integration between DogParkSDR and MacLogger So I’m curious whether DogParkSDR can deal with the same concern- feeding the frequency information from the active slice to other programs such as MacLogger.ĭogparkSDR doesn’t have the same concern - MacLoggerDX gets the active slice frequency information directly from the Flex Radio server not dogparkSDR and has done so since before dogparkSDR was created. It connects directly to the Flex radio server as a non-GUI client and has always done so. MacLoggerDX does not connect to a com port or CI-V connection with the Flex. ![]() Don recently posted the below on the DogPark Forum, relating to the same question here
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |