GEOSATpro Micro died last night

tekjunkie02 said:
FYI:
That's the same cable I had. And these problems sound very much like mine were.

Hopefully they learned something from my Micro that can help you.

Lol. Yup they must have built them wrong or missed labeled or something. Plus without the right wiring hood your going to spend a lot of time trying to get a good contact with the 4 pins.
 
Did you use the 5v pin and not the 3.3v? We did not test this design and do not know if it has any compatibility issues. Hearing from two buyers of the TTL/USB convertor that it did not work makes me suspect of the device.

Has anyone been successful with this design of the USB/TTL convertor?

I think NorthGeorgia did. You can check back on the old thread
 
Just received and tested the TTL/USB convertor cable samples manufactured by Wallyhts. Works great and nice workmanship!

The connector fits the header perfectly and the .abs and .udf files transfer perfectly! Great Product!

TTL_Cable_Connector.jpg
 
SatelliteAV said:
Just received and tested the TTL/USB convertor cable samples manufactured by Wallyhts. Works great and nice workmanship!

The connector fits the header perfectly and the .abs and .udf files transfer perfectly! Great Product!

<img src="http://www.satelliteguys.us/attachment.php?attachmentid=81299"/>

Yeah and I just got em in stock so if anybody needs one send me a pm

Sent from my DROID2 using SatelliteGuys
 
Got the cable today micro is working again.This is very easy fix with the help of the good folks at Satellite Guys.Plus a very good seller to send me the cable.Tried to send bad udf file but was refused by my email. THANKS EVERYONE
 
Got the cable today micro is working again.This is very easy fix with the help of the good folks at Satellite Guys.Plus a very good seller to send me the cable.Tried to send bad udf file but was refused by my email. THANKS EVERYONE

Great news!

zip or rar the .udf file. Your email probably thinks that it is a virus.
 
is this solution simply putting on a connector on a usb cable? if so i have the connectors, cables and a soldering iron...? charlie

No you have to have one that has the proper built in chip and circuitry.
 
I tried 2 different computers running Win7 and one running XP with the posted drivers that Prolific has available. Tested that mine has proper 5V output when measured. Verified proper com ports on the different machines and for proper pin fit and still no luck. Pretty much gave up and boxing everything thing to go back or sell. I haven't used it for nearly 2 weeks now anyway. I hate to be the only one here that doesn't like the micro but I think future units should have this device included the way the older receiver came with a serial cable. Sooner or later you'll need it.
 
I tried 2 different computers running Win7 and one running XP with the posted drivers that Prolific has available. Tested that mine has proper 5V output when measured. Verified proper com ports on the different machines and for proper pin fit and still no luck.
Would be happy to look at the unit and test for correct function with the cable. Call our support team and request an RMA. Send in the receiver and the convertor cable and we will test. We only ask that you cover shipping if it is not a defective microHD.


I think future units should have this device included the way the older receiver came with a serial cable. Sooner or later you'll need it.
Out of the thousands of microHD STBs sold, only a handful have required the cable for recovery. Doesn't make much sense to include with every unit if only needed by a few for recovery. Only the hack boxes came with the RS-232 cables.... to make theft of service easier....:eek:
 
Last edited:
After reading a post by northgeorgia earlier about the USB TTL device having the TX and RX terminals reversed I tried one last time with mine and was able to reflash the ABS file successfully and normal operation was restored. Thanks to everyone that has helped.
 
Well, as they say, everything happens for a reason. Not 100% what caused mine to go back into the "cycle of death" mode (I'm sure it had something to do with my .udf and my attempt last week to reload the 8/29 firmware), but the good thing is that I had to go through the whole procedure (and frustration) again, and in the process I could help you (and maybe others who are lurking) LOL :)

Welcome back to the club ;)
 

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)