|
PureBytes Links
Trading Reference Links
|
Dear Bill:
Your problem sounds very much like one i had 2 years ago. Perhaps recounting
my experience might help you. At the time, no one at DBC, TS, MS or Gateway
Tech Support could figure out what was wrong. After 3 mos of stumbling, i
finally found the answer.
The Signal ROS is a software system that has an automatic feature to try to
insure that the cable box is feeding data. When data input stops {for i think
15 minutes}, the Signal ROS automatically reloads its ROS into the TS Signal
Server. During this reload, TS STOPS receiving new data {a killer if you are
trading RT}--it needs to square its data requirements with the Signal box
first. To the user, it looks like a TS crash. Unfortunately, there is no
switch to turn off this auto reload in the ROS. The Signal software guys {as
opposed to tech support} are aware of this problem. DBC, however, made a
business decision to puts its resources into developing the new eSignal internet
product, and had {as of 2 years ago} no plans to upgrade its ROS and solve this
problem.
Fortunately, this ROS reload appears to be a rare occurrence according to the TS
tech support record. When it does happen, however, the problem is persistent.
The only real solution is to switch to a different means of receiving the data,
or to a different data vendor. BMI {which is now owned by DBC}, for ex, has a
cable box that uses a hardware solution to the ROS. Therefore, the BMI cable
box never has to reload its ROS. i switched from Signal to BMI and have had no
problems in 2 years. If you rely on and prefer cable, this is a practical way
to go.
{Of course, if you have history on lots of contracts, you may have some
problems--or lots of work--in renaming contracts to convert from the Signal to
the BMI data format. Neither Signal nor BMI provide data converters.}
Good luck!
Brad Yoneoka
TradeWynne@xxxxxxx wrote:
> Just had my signal box spontaneously reload ROS. System said: "receiver time
> is late" and started to reload ROS. Anyone else? Any known solutions? This
> has happened before just after the 6:00 hour PST: i.e. 6:12AM or 12:12 Noon
> PST.
> Obviously I rebooted, but how do you fix it?
>
> Thanks,
>
> Bill Wynne
|