开云体育

Hi Rob/David Actually for the 9100 it always presents them in the right sequence. ie the first is always the C-IV port. Other USB devices may of course get in the way of numbering if they are

Of course Rob is right here.. though there is a simpler way if the cabling on the host never changes: /dev/serial/by-id . For example, I can see the various serial ports on my host: ls -la

It's good to know I'm getting closer. again, you all are much appreciated. So new window with rigctld -m2? and then f to get the freq yeilds: thinking I may have been connected to the wrong USB, I

Since it appears the radio provides 2 USB devices (USB0 and USB1), the operating system may not "ALWAYS" present them in the same order. This will cause no end to interfacing headaches. If you are

Perfect.. that's what you should see from an idle daemon "running". Just make sure you're running it on the right USB serial port be it USB0 or USB1. At that point, you need to open up a new window

hi Bob, So I went ahead and removed gpsd, renamed the modem manager, and double checked all of the perms for dialout and tty. I removed the ampersand, and the extra v's and rebooted- checking the

It must be that the D710 is internal to the ISS hull which is radiation/rf-protective, and no external GPS antenna was interfaced to the radio. Thank you.

But that would void the warranty.? If damaged during the mod, shipping cost back to Kenwood would be enormous <grin> Robert Giuliano KB8RCO

One would not expect instrumentation on the ISS to be limited to the 60,000 ft. max GPS elevation restriction of many civilian units. Even a TinyTrak-3 has provided high-altitude balloon elevations >

Hi, If this is the internal GPS receiver inside the Kenwood D710 keep in mind that most such terrestrial GPS receivers are intentionally limited at which altitude and velocity they are operating (to

Greetings, I'm wondering why the ISS PBEACON always indicates ~0.0 lat/lon. Is GPS disabled due to rf electrical or security concerns? From direwolf 1.8D: ...

Oh and forgot to mention. Be wary using the 9100 monitor, as the TX audio then comes back into the DW RX. I have no idea if that can cause a problem beyond just displaying on the terminal and log, but

Hi David Well my setup is Pulseaudio so very different; (DONT USE THESE CASSIE) #ADEVICE ACHANNELS 2 RATE 48000 CHANNEL 0 MODEM 300 B+ PTT RIG 2 localhost:4532 CHANNEL 1 MODEM 1200 #No PTT so

Hey Cassie, It's great to see Bob's real world experience with the IC-9100 and what you need to consider when working with that radio. One thing that wasn't clear to me from Bob's message is which

Hi Cassie It looks like David has answered all. I am on the other side of the world so some sleeping delay involved. Some notes; One trap you might fall into later and should just keep in mind is that

How are you starting rigctld? Manually? Via some script? I would recommend to do this manually until you prove things are working at the basic levels. This seems to me that you have multiple rigctld

I did make sure the user is on the dialout list, immediately after the command, it first shows: and then followed by a continuous time out list, and after several minutes, It did update with this at

Beyond just the timeouts, did rigctld say anything else when it first started? Did you fix the permissions of of the serial ports as I mentioned?

Ok, so I found info on hamlib, was able to download libhamlib_utils and ran rigctl -l using grep to locate 9100 to make it easier, and now I see where the 3068 number came from. So now, running:

Hello Cassie, You're welcome and there are many other people here on the list who can help, offer other unique insights, etc. Sounds like that was a student but the instructor forgot to mandate that