Kalypso Panel Freeze
- Login to post comments
This past weekend, I was on a Kalypso doing a full day of high school basketball. In the middle of the last game, the panel's buttons would not follow my punches, but whatever I punched would would work in the frame. The buttons would not light up as I would punch them. I got through the rest of the show ok, it was just a little nerve-racking that I couldn's see what I was punching on the panel.
Has this happened to anyone else? Our engineer told me that if we re-booted the panel, it would take about two minutes to come back up (which our breaks were only a minute). Is there a faster way to fix this?
This discussion seems to get down to the OSI Networking Layer 1 (physical). One of the present copper wire limitations is bandwidth. Too much data for different object oriented apps on the same wire, switch, router or hub (yikes!) is going to cause, at the least, latency. Too many servers, clients, hosts, etc., on a single physical layer makes the crowd much larger with everybody talking on Layer 4 (tcp/udp/etc.).
If the control panel actually locked up, I have seen that happen on a Kalypso when the control panel internal processor bit the big one on a newer switcher.
Of course the physical layer has other problems too. Including plain ol' AC 60cycle hum. That probably caused the lockup of a Sony switcher on a live show. Using the same power source for both control panels and switcher guts would not have that problem.
The same goes for other physical layers also such as RS-422 machine control.
- Login to post comments
I have had that happen in the past. The culprit at the time was that the Kalypso system was not isolated...it was on the same ethernet system as the house IP system. This meant that the Kalypso was trying to communicate between the panel & frame at the same time that other people were sending e-mails or web-surfing. This caused the Kalypso to slow down - pressing Cam 1's button might not initiate a change for anywhere from a few frames to a few seconds. Check to verify that the IP system of the Kalypso is isolated from any other ethernet system. This includes any laptops that may be tied into the Kalypso (such as the TD's or EIC's computer that may be hard-wired and running the Kalypso's panel emulator but may also be connected to a wireless ethernet source for Internet surfing)...this can cause ethernet conflicts & slow down the system.
A panel reboot can be quickly performed from the panel by simultaneously holding down the Shift / Unshift / Near / Far buttons for a few seconds & then choosing EXIT from the choices displayed on the panel. As I recall, the panel reboot time is pretty quick (I would guess under a minute - but you may want to check this during ESU just to be sure), although the menu takes longer. But you don't need the menu to recall effects and switch live.
Bob Ennis