Production Switchers

I just about had a heart attack tonight.

So, I wanted to experiment with my own switcher set, and decided that saving over a default with the ALL setting would be safest. So, I did. I then saved ALL to a new switcher set, and then made some new custom controls, and then saved those out as well, again using the ALL setting.

Afterward, I wanted to make sure I could get the board back to our station's default setting, and loaded up the set I saved it to, and loaded ALL settings. That was when the board crashed, and I had to reset the board from the CPU. Powering off just the board was not enough. So, when the board came back online, and I loaded ALL once again, it worked that time, and got things back to working order.

I am now nervous about loading and saving settings, but I'm thinking it was the ALL setting that may have done the harm, causing a lock up when (perhaps) the INST settings were recalled.

All I am really wanting to do is save my own MEMS and CUST settings, and I'm thinking if I were to try it again just saving using these options that I wouldn't cause a crash again.

We are also using software version 6.2.0.7650, and am wondering if a software upgrade would help. Also, our IT person wanted to make sure if we did upgrade the software, if there were any possibility of making anything connected to the board incompatible, or any other concerns we need to know about, before making such an upgrade.

...and by "crash" I mean that the board locks up and is UN-responsive. You can't select any source, no buttons will do anything, etc. Yet, I could still FTP to the board.

#Carbonite

Hi Steve,

Running the All is fine -- I do it all the time. I will say that under the hood there is a linux kernel and that there are occasions where there is going to be some kind of an operating system mishap.

It is way, way less than you would ever find with Windows ;) based systems. Now I would always recommend doing an upgrade (it is on our website) and everything will be just fine and it will all just continue to operate as before. You will get a couple new features and of course bug fixes.

The physical panel by the way is controlled be the frame so rebooting the panel is just turning on and off the modules the actual process is being run in the frame. Sounds like you could have had a hung panel application but the Frame application was still running since you could do other function like FTP. Curious if DashBaord was still working.

Since you were able to load the setup after the reboot just fine I would assume that there was not a corrupt file on the drive causing you an issue.

Sorry I can't be more helpful as we have not seen this exact example of steps to produce a crash before.

Les

#Carbonite

I have just been loading and saving the MEMS and CUST settings to a couple of sets, and haven't had the crash again. Now, however, when I try and load CUST from a set, it says, "Load: Failed." I thought perhaps the files become corrupted, so I modified the custom controls to our default setting (deleting my custom controls I added), and then saved them to "set 9", and then tried to load them again from "set 9". This also produces the "Load: Failed."

I do plan on updating the software, and hopefully this has been a bug already addressed, and perhaps an update will fix the issue. I'm going to have to wait until people are back from holiday vacations, but wanted to add to this issue while these issues are occurring to journal them. Once the bugs have been worked out of loading and saving sets of the MEMS and CUST settings, our directors will use them quite often.

#Carbonite

Hi Steve,

Can you please contact Tech Support with this issue so that they can track it properly and work with you to resolve it?

They can be reached at 613-652-4886.

Les

#Carbonite

Will do. I've been waiting until after the holidays so I can make sure everyone is in the office here.

Thanks!

~ Steve

#Carbonite