Rig Control with Ten Tec Jupiter?

[N2LEA]

Hi....I've been trying to get the rig control portion of the software working without success. The Ten Tec Jupiter seems to be supported only by Hamlib, so I chose that option. The CAT settings were configured, as was the Communicator Services. Both Log4OM icons appear in the windows taskbar as the manual described, and both of the comm "lights" at the bottom of the program window are indicating green, yet I am unable to get any data in from the radio. The cabling, etc, all works as I have tried it with other programs as a test and haven't had issues. I've matched the settings for stop bits, etc, and have not had any success.

Has anyone out there successfully used a Jupiter with Log4OM? Did you have to do anything unusual?

Thank you, in advance, for any help.....

Doug Maset
N2LEA
Newburgh, NY USA

[G4POP]

Try Omnirig I understand it works fine with the Jupitor

[N2LEA]

Progress !

Thank you, Teryy, for suggesting that I try OmniRig. I downloaded the files and when I looked at the rig definitions available, I was pleasantly surprised to see one for the Jupiter, even though their list of supported rigs (on their website) did not list it. I installed the program, and tested the control functions using the Client software and everything worked.

I went into Log4OM and configured it for Omnirig. I checked to make certain that the paramaters were the same as when I tested using the Client software, and they all matched. Everything seems to work now, except for the frequency field, which always remains at 0. For example, If I click on a callsign in the Cluster display, the rig changes band and mode properly, and is set to the correct frequency, but the frequency display in the log window still is not updated.

THings are so close to fully working that I suspect that I am missing some simple setting. Any thoughts would be greatly appreciated!!

Thank you,

Doug
N2LEA

[G4POP]

Hi Doug,

There are a few places that there could be an issue as follows

1. Have you got the latest firmware update installed for the Jupiter?
2. Have you tried a slower Baud rate?
3. Have you set Omnirig to Data bits 8, Parity None, Stop bits 1, RTS High, DTR High, Poll int. 500 & Timeout 4000?
4. Are you using a USB to serial cable and if so have you downloaded the latest driver?
5. Did you ensure that the rig is not set to Pegasus emulation mode?
6. Have you had a successful connection using the same cable and rig with any other CAT control program?
7. Have you tried a factory reset of the rig.

In an earlier post you said that you had problems using Hamlib with the Jupiter which makes me suspect a rig or cable issue!

There are no settings in Log4OM that would cause this issue but of course it is always possible that the Omnirig ini file is at fault, you could check out the Omnirig and Ten Tec forums about that.

[N2LEA]

Hello all,

Still trying to get everything working, with the Jupiter. All cables, drivers, etc., are fine. Rig also is fine, I have no issues when running other rig control programs. I'm not sure what is left to do but enter frequencies manually.

If anyone has had success with their Jupiter, please let me know.....I'd love to know how you set it up. Thanks.

Doug

[G4POP]

Doug,
It's a process of elimination so to help you I need specific and definitive answers to my questions before we can proceed

[N2LEA]

Hi, Terry,

I'm not sure of which things you would really need to know, but what I can try is to list out what I do know. The rig and cabling, drivers, etc, are all working and updated. Omnirig itself appears to be working based upon their "client" program which allows you to test the rig to computer communication; the settings it loads (which are duplicated in Log4OM) showed all the VFO or operating mode changes that I make at the radio to be shown real time in the client control panel. The client tracks and displays the rigs VFO frequencies perfectly, as does my old logging program. I think the hardware is all working properly.

As best I can tell, I think the software is configured properly. The CAT settings are set for Omnirig. The top 4 checkboxes are checked; the last one for Digital, is not checked, as shown in the manual. Communication services are set to auto start. The Cat Connection tab which brings up the Settings box for Omnirig matches the same configuration which worked in the Omnirig testing client. Even so, I tried every combination to see if I could find one that worked. I even tried slowing the baud rate down to 9600 without success. Both Comm Services "Lights" are lit green at the bottom of the screen.

The rig seems to accept frequency and mode commands from Log4OM.....I base that on the fact that when I click on a DX Spot the rig immediately jumps to the Frequency and Mode. The Frequency box in the logging box, however, always remains at 0.000. It doesn't appear that the Log4OM can read the VFO info from the rig.

Is there something else that you are looking for that I can check?

Thank you for the help, Terry....I'm really hoping that I can get this working since I really like what I've seen so far!

Doug
N2LEA

[G4POP]

1. Have you got the latest firmware update installed for the Jupiter?

3. Have you set Omnirig to Data bits 8, Parity None, Stop bits 1, RTS High, DTR High, Poll int. 500 & Timeout 4000?

5. Did you ensure that the rig is not set to Pegasus emulation mode?
6. Have you had a successful connection using the same cable and rig with any other CAT control program? - NOT THE CLIENT SOFTWARE

7. Have you tried a factory reset of the rig.

That still leaves five of my questions unanswered as above!

Like all troubleshooting we need a base to start from, it may be when I have the requested answers that I need to communicate with you or your computer direct by Skype or Teamviewer.

[N2LEA]

Terry,

I actually did answer most of those, but not in a direct way, so here goes..

1. Yes, latest firmware on Jupiter
3. Yes, set Omnirig to Data bits 8, Parity None, Stop bits 1, RTS High, DTR High, Poll int. 500 & Timeout 4000
5. Yes, the rig is running in Jupiter mode, not Pegasus mode
6. Yes, the setup works perfectly when running HRD. my (hopefully ) previous logging/control software
7. I have loaded and tried running Log4OM with both available options for the latest firmware for the Jupiter, the normal mode and the CW reader option. Both yield the same results. (I am assuming that loading and booting into the different versions of the latest OS is essentially the same as a factory reset...?)

If we have to do a Skype I will need some time to install and configure the program.....let me know.

Again, thank you, Terry, for your assistance....

Doug

[G4POP]

Doug,
No loading and booting into the different versions is not the same as a factory reset! You should reset the rig first and then update the firmware to ensure that you start from the correct situation.

Please do the reset and reload of firmware as above, then install two programs below:

1. Skype install on the computer where you have Log4OM installed with just a microphone and speakers connected - We do not require a webcam.

2. The free version of Teamviewer, again on the same computer that Log4OM is installed

When you have done the above email me using the email address shown on QRZ.com.