How to clone a Coolsat

gremlin411 · 10-21-2007, 07:50 AM

How to clone a Coolsat

Thanks go to Carpenter 1 for this post
--------------------------------------------------------------------------------

First, you'll need a null modem cable.

Then bring the box needing the software to a box that is connected to a TV. The box needing the software needs no connection to a TV or sat for the transfer process.

Connect the 2 boxes together with a null modem cable. Turn ON box that has the software to be copied, in the Menu, go to System Information (CS4000Pro), or System Setting > Data Transfer for the CS5000.

Press either FIRMWARE or Channel Data, and power ON the box receiving the data.

After the transfer is done, do check the Dish Settings menus when to "cloned" box is connected back to its TV for the proper sat settings.

jason019008 · 12-16-2007, 11:37 AM

not quite sure what this accomplishes... is this to upload files to a new receiver and get it going or is this a way to transform a dn receiver to an fta.
i know this question may seem laughable to some but you have to agree the post above is a little vague in that aspect.

aj_sheikh · 01-12-2008, 07:00 AM

if i am running the latest bin for my cs5000 can i do this with my 4000 conect it to my 5000 and clone my 4000 to 5000?

gremlin411 · 01-12-2008, 07:57 AM

Quote:

Originally Posted by aj_sheikh

if i am running the latest bin for my cs5000 can i do this with my 4000 conect it to my 5000 and clone my 4000 to 5000?

No the files are different for 5k & 4k . but if you had two 5k's or 4k's or even 6k's you would only have to hook one up to your computer the other you could clone.

tookitookibird · 01-17-2008, 11:35 AM

The null-mdm cable MUST have the full complement of signalling wires.

That means it is best that there are 8 wires in the cable jacket.

Simple null modem cables with shunted RTS DTS or DSR DTR are not good enough.

The coolsat developers were tricky in their use of the serial ports, using some of the serial hardware control wires to signal whether or not the receiving STB was properly ready for getting a firmware download.

Some simple null-mdm arrangements have the sending STB decide the other end is not ready, and in the menu system, instead of being off.

Another null modem arrangement I tried - with a serial diagnostic "patchbox" had switches that allowed two straight through cables to become a null-modem via the patchbox. Something about the patchbox did not emulate the cable assembly closely enough, and I had to resort to a complete, and simple wire-only cable.

This following diagram should help. If the X's don't line up, then try viewing the diagrams with a mono-spaced font.

DTE (9 pin) DTE (9 pin)

RD 2 ---------\ /------------- 2
TD 3 <--------/ \------------> 3
RTS 7 ---------\ /------------- 7
CTS 8 <--------/ \------------> 8
DSR 6 <---, ,----> 6
DCD 1 <---+----\ /-------+----> 1
DTR 4 ---------/ \------------- 4
SG 5 ------------------------- 5

Note:
2,3 are switched over, as are 7,8 and 1,4
Both connectors should have 6 shunted to 1
Only 5 is straight through. (Signal Ground)

Ideally developers should avoid using hardware features for purposes other than intended, and because of this, CS developers made the use of a serial cable break-out box (An important diagnostic tool) problematic.

If any future developers are reading this, then try to avoid this sort of tricky design jiggery. It compromises the implementation standards, in this case making the serial port fail to conform to IEEE rs232 standards. Good design engineers don't flaunt standards this way.