Rx Sync problem between Old Hub and Newer RCST

good day,

a client of mine has a Linkstar DVB-S1 hub that's working fine with several remotes. We just purchased a used RCST that was decommissioned from a different network and when we enter the parameters for our network, the RCST loses Rx Sync in less than 2 minutes.

When first plugged in, the Rx syncs with a good BER but in a couple of seconds, the BER becomes really high and the RCST shows some message about the RNCC possibly kicking it. It then goes on to try another bootconf which of course does not work.  

Versions on new RCST
0x239A7 SW rcst4s-2.3.0101.term.exe (PE)  ()
0x239A7 FW rcst4.16190707L.xilinx.dat () rcst4.15250706L.xilinx.dat (PE)

Version on other RCSTs connected to the Hub fine is
SW: rcst4-1.0.8.17p2.term.exe
FW: rcst4.16100106L.xilinx.dat

I have two questions:

1. how can we downgrade the firmware and software directly i.e. via the ethernet interface rather than over-the-air
2. what is the correct procedure for adding a previously used RCST to a linkstar hub? (my client inherited the network with little documentation so i can't really be sure he is doing the right thing)

thank you for your anticip.ated help.

Dewole

Have the customer/installer perform the command rcstlockinfo through a telnet session.
I the output says something like "...locked through telnet session" then you would need to contact the previous provider for the pincode to unlock the rcst.
Are the bootparameters also in sync with the Hub settings?