www.avnetwork.com: As we build our “future-proof” classrooms of tomorrow, a few mysteries remain. Somehow, the amount of equipment utilized in classrooms and boardrooms has shrunk, and yet, we are capable of doing more than ever before. We’re frequently seeing analog routers and switchers with all the RGBHV wire and distribution being replaced with newer products with single, point-to-point connectivity over Cat5.
6 comments:
I would've thought most of these were common sense things, but I guess it's a good reminder. I've worked A/V in a variety of situations, some where the setup was clearly labeled and easy to parse, and some that were just jumbles of dusty wire, some of which (I found out) weren't even plugged in on either end. At my summer job, we used a security camera system to have video evidence on all the robots at all times, but when that system went down, it was nearly impossible to fix. Between all the cameras and the network switch was at least a million wires, and we wasted so much time tracking each one because they weren't well labeled and there were spare wires everywhere. I make it a point these days to label every wire that I run in almost every sound and lighting system. I find that the extra few minutes it takes for everyone to scramble for gaff tape and a sharpie is well worth it when somehting breaks down.
The ideas and tips in this article seem to be general trouble shooting tips rather then specific to AV control systems in classrooms. Although the examples are a little more specific. I don't know what sort of classrooms this guy is setting up, but they don't look much like the classrooms I've been in. Here at CMU many classrooms have a projector, computer, touch screen system. But they aren't nearly as complex as the ones that this guy trouble shoots. And yet, we still have problems using our set up. I suspect that there are always going to be far more problems that come from users not knowing how to use the system and very little from the system breaking or being set up wrong. I would have liked a few tips on how to deal with the users when things go wrong. How do we tell people what we did to fix the system and how they can do the same thing in the future? How can we get people to describe the problems they are having in a more helpful way? The article talks about what is ideal when in comes to working with the end users, but it doesn't tell us how to get there.
In middle school I spent a good amount of time fixing computers and projectors and other tech in classrooms. I found that the organization and processes tips that this article talks about were very useful and really the only way to make trouble shooting run fast and smooth.
I think that this article is more catered to the AV technician in a large corporation where you may want to integrate several screens, board rooms, and a building PA. A system where the integration may involve several inputs and servers being run throughout the building. I can even imagine some of the systems being integrated with video chatting through the network. In this sense I believe that this article is designed for a person who is in this type of situation. Other than that I agree with Akiva in saying that a lot of the tips provided in this article can help with smooth troubleshooting in any size system.
This is a good list of things for people to keep in mind, but as Ruben pointed out they are also things that should really be common sense to anyone who has ever worked in an IT, AV, or any other troubleshooting position. All the same, it is a good mindset for everyone who has to deal with installations of things to keep in mind, as it extends to more than just these fields.
I suppose a lot of this is common sense, but it's doesn't hurt to hear it again. The advice about not changing more than one thing at a time is especially important. After taking three years of computer science in high school, I can most certainly attest to the fact that the troubleshooting process was only slowed down by making too many leaps at a time. It was important to parse information and change systems methodically. I definitely can see how this troubleshooting tactic carries over into control systems and AV setups.
This article is a good review for troubleshooting in general, but it is primarily targeted to the technician that deals with big conference rooms, lecture halls, etc... It is interesting to think about all the goes into making these rooms work, but in all honesty, I think about this stuff all the time since it is something I had to do at my high schools IT department, just not this advanced. I also just enjoy thinking about this sort of stuff and how to make it work/improve it.
Post a Comment