Scott, Frank, K4FEG here, I do not know if this would applicable to your situation, but while I was having control issues with my Icom Ic-910H and SatPC32, I reached out to Erich (writer of SatPC32) about the issues and he told me that some of the cables and other interface modules (USB/Serial adapters) need to have the /*FTDI chip set*/ in them, /*I had to search for a specific type of USB/Serial adapter that had the FTDI chip set in it.*/
Once I got this adapter, and plugged it in on my Windows 8 and 7 PC's, both operating systems instantly recognized the device and loaded the proper driver to make the adapter work. /*Erich explained that the PROLIFIC chip set, which is common in North America seems to have an issue with his program.*/
Another note is that there may be a firmware update for you Kenwood. I have had others tell me that their TS-2000 would not properly control with SatPC and when they got the various firmware updates for their specific model radio, it helped to resolve their control issues.
I do not know if this information is of help or not but I thought that it might, you may post your question on my BB, Star-COM.net, if you like. My bb tries to cater more to real life situations and operations on the satellites and working with operators and rovers to facilitate working new grids on the "birds" you are most welcome to come visit there if you wish. 73 & best regards, Frank K4FEG
I second Frank's comments about FTDI chips. They are about as bullet proof as you will find.
One of the reasons for problems with the Prolific chips is that they are widely cloned. Prolific started adding code to their drivers to identify cloned units, and not work with them even though they will install. A good indication is if your device requires its own proprietary drivers, or old Prolific drivers. In either case, they are likely to have problems under the strain of moving large amounts of data bidirectionally. I have 2 GPS units and a Baofeng programming cable, all cheap ones from China, which will not work with anything later than 2007 drivers. Because these are low demand applications, they work fine.
Another solution, and my preferred one for desktops, is to install PCI serial ports. They are as cheap or cheaper than a good FTDI USB, and they just work.
73s,
Alan WA4SCA
The problem with using a cable with a "Prolific" chipset, is that many of these cables have counterfeit chips in them. What happens is you get them set up with the included drivers, the cable and program work properly, and then Windows Update replaces the driver with a newer version, and the cable stops working.
Prolific has changed their drivers to include some checking steps, and if the driver software detects a non-genuine "Prolific" chipset, it won't load, causing the cable to not work.
AFAIK, FTDI chipsets have not been counterfeited, and will continue to work after Windows Update makes changes in your system.
73, Jim KQ6EA
On 01/18/2014 08:56 PM, K4FEG wrote:
Scott, Frank, K4FEG here, I do not know if this would applicable to your situation, but while I was having control issues with my Icom Ic-910H and SatPC32, I reached out to Erich (writer of SatPC32) about the issues and he told me that some of the cables and other interface modules (USB/Serial adapters) need to have the /*FTDI chip set*/ in them, /*I had to search for a specific type of USB/Serial adapter that had the FTDI chip set in it.*/
Once I got this adapter, and plugged it in on my Windows 8 and 7 PC's, both operating systems instantly recognized the device and loaded the proper driver to make the adapter work. /*Erich explained that the PROLIFIC chip set, which is common in North America seems to have an issue with his program.*/
Another note is that there may be a firmware update for you Kenwood. I have had others tell me that their TS-2000 would not properly control with SatPC and when they got the various firmware updates for their specific model radio, it helped to resolve their control issues.
I do not know if this information is of help or not but I thought that it might, you may post your question on my BB, Star-COM.net, if you like. My bb tries to cater more to real life situations and operations on the satellites and working with operators and rovers to facilitate working new grids on the "birds" you are most welcome to come visit there if you wish. 73 & best regards, Frank K4FEG _______________________________________________ Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
During FO-29 passes near the USA west coast I've noticed a 9600 baud data signal in the downlink. Today I finally got a decode and the OnLineKissPlus file shows:
À 2014-01-21 17:56:35.490 UTCÀÀž¦†jhlÛÜŽ¦°nhr ðThis is another Trailblazer Repeater test` À
The uplink would be about 145.945 MHz.
Anyone have an ID?
73, Ken, W7KKE CN75xa
participants (4)
-
Alan -
Jim Jerzycke -
K4FEG -
Ken Swaggart