GEOSATpro ON/OFF Reboot Looping

[avenger]

Ulploaded the new Satellite channel list, forgot to do a hard reset after the upload, erased some channels and NOW the microHD is into the endless On/Off cycle/loop.

I do have the USB to TTL 4 pin cable, I believe that it is the right VCC +5 conversion cable needed. There is no room for connecting the four cable into the PC board plug had to remove the four black plastic covers, and wrapped them using scoth tape

The PC recognizes the new hardware, but for some reason won't install the USB/ Serial drive software. Got to figure out how to install the USB to TTL software.

My PC has four USB ports, and can't tell how to identify the COM ports as 1-4.

All of my microHD software downloads are installed and located in a USB (Stick) portable drive. I guess that the stick gets connected in the microHD USB port when trying to correct the blinking problem, while the USB to TTL cable is connected to one of the PC's USB port. Did not get pass step 10 of the " Firmware Update via Internet TTL, Serial connection" instructions.

Need some more information on how to do this Update.

Thanks

 

[Larry1]

Once you resolve the cable and driver problem, you need to run the ALiEditor and use that to transfer the software from the PC to the microHD. Be sure to download the current version of the microHD software as posted by Brian or from the link where to purchase the cable, as I recently had problems with the posted software. (Brian re-uploaded the ALiEditor yesterday). With the ALiEditor you need to edit the .ini file to show the correct path to your directory where the ALiEditor is. (check the other thread as I posted a pic of my ini file yesterday and edit your path to match your computer) Also check that the chip type is correct. Depending on what is corrupted in your box, you may only need to transfer the UserDatabase File (UDF file) or if that does not sole it then the firmware file. If you follow the link to purchase the cable, there is a video of how to restore your microHD. If having problems loading the USB driver on one computer, maybe try it on another computer. If you set a restore point BEFORE loading any driver or plugging in the cable, you can also go back to a fresh start.
Can't help in the USB cable as I made my own serial cable. The box pinouts for the cable are in one of the threads here if you are not sure where what pin goes where. When doing the restore with the cable, you do not plug anything into the microHD's USB port. All the data is sent from the PC over the serial cable to the microHD.
Good Luck

 

[avenger]

Thanks Larry1,

Connected the cable to the wife's computer and it did not recognize it. When doing the update, I had the USB to TTL 4 pin cable connected between the microHD plug and the PC, it did found a new hardware, but did not downloaded nor installed the serial driver. When I connected the USB to TTL cable to the wife's computer, the USB to TTL cable was not connected to the microHD, can the cable be tested by itself, or does it has to be connected to the microHD as well to make the complete loop.

I did followed the instructions but could not get pass the selecting Serial port part....Took the (FLU) Fortec Lifetime Ultra out of storage, and right now I am scanning for the KU satellites minus them HD channels, untill I get the Port and the cable Serial driver problem resolved.

Thanks.

 

[SatelliteAV]

The convertor should only be connected to athe PC USB port.
Use the PC device manager to select the device and install the driver.
Once the driver is installed, connect to the microHD.
Launch ALI Editor and select the correct port.

Was this cable purchased through Wallyhts or ke4est?

Is the driver compatible with your OS?

 

[jibaro29]

"forgot to do a hard reset after the upload"

I have been meaning to ask, How in the world can I do a hard reset when the micro does not respond to the remote commands? I too uploaded the new Satellite channel list via USB and had a similar problem. Thank god I have that USB/TTL with out it my receiver would be useless.

 

[SatelliteAV]

Do not recall any DVBS STB ever sold with a hard reset button. Recovery is by serial communication port.

 

[wallyhts]

Did two wires ever touch together? I have seen this before no matter what the driver will not install.

What driver are you using?
What cable do you have?

 

[avenger]

Had my son to use his computer and it seem to work up to the end, got to see all the prompts and loaded the latest update, however it did not fix the problem... It is still blinking Red and Green. COM port 3 was the one used. Still have not figured out why it wont work with my PC, as for the driver being compatible with the OS I am using windows XP. My son is using Windows 7. Will try again tomorrow.

The cable was bought at the time of the first occurance of this happened, and it came straight from CHINA. Will have to PM either Wallyhts or ke4est.

 

[SatelliteAV]

To correct a cycling reboot, typically would load an .udf file. It sounds like an .abs file was loaded.

 

[Larry1]

A working UDF file can be downloaded from one of the other threads if yours is corrupt or if you did not make a backup of a working database.

 

[SatelliteAV]

Also, an .udf can be extracted from a factory firmware .abs file. Select the User Database option when opening the .abs file then save.

 

[avenger]

Did two wires ever touch together? I have seen this before no matter what the driver will not install.

What driver are you using?
What cable do you have?

No two wires ever touched together, I used the black connector on the white wire, the green was bare, the red was scotched tape, the black wire was bare so all wires were isolated, the cable came from a vendor direct from China. I do not know what driver is used since it only recognized the hardware, never acknowledge the software.

 

[SatelliteAV]

Did the reseller provide a CD or link for the driver?

The device typically is not automatically recognized and the driver wouldn't be automatically installed. The international convertors that I tested needed the compatible driver to be manually installed.

 

[avenger]

To correct a cycling reboot, typically would load an .udf file. It sounds like an .abs file was loaded.

The chances of a .abs file being used are very possible. Will reload the newest Satellite file. When my son comes home from work, will try again. Still puzzled over not being able to install the Serial driver to my PC, it worked on my son's PC, go figure.

 

[avenger]

Did the reseller provide a CD or link for the driver?

The device typically is not automatically recognized and the driver wouldn't be automatically installed. The international convertors that I tested needed the compatible driver to be manually installed.

The seller did not provided a CD nor a link for the driver, came straight from China, LOL!!

 

[primestar31]

Here is a link to the drivers that should work for you: http://prolificusa.com/pl-2303hx-drivers/

Most every China cable of this sort uses the Prolific driver.

 

[wallyhts]

Here is a link to the software/driver I use.


http://38.80.2.6/usb.zip

 

[Corrado]

The issue I ran into initially was that my converter had the TX and RX wires reversed which prevented me from communicating with the receiver.

I used the Prolific drivers with mine.

 

[jibaro29]

I feel your pain Avenger. This receiver should not be that complicated. When I first got the microHD I used the USB to do an upgrade. That when I first experienced the dreaded on/off cycle. I didn't know, at the time, that ALL codes was not the right file to upgrade with. After texting Brian he was kind enough to fix my receiver. Once I got it back I tried the udf via USB and that dreaded cycle started all over again. I did not use the micro for about a month. It took me 3 weeks to get USB/TTL from China and another week to get the courage to tinter with it. Now is a piece cake to upgrade because I do not use the USB stick or via OTA I'm strickily using the USB/TTL.

 

[northgeorgia]

I used the same driver Primestar mentioned and also had the same situation as Corrado with the reversed labeled TX/RX nodes. Those wires drive me crazy because if they're not connected -just so-, there isn't any communication between the STB and the computer. The driver basically makes the computer recognize a USB port as an old COM port.