Options
System Testing
jjames
Posts: 2,908
How many of you create small programs to test all the interfaces of a job to verify hookups prior to loading the actual program? Something we're trying is creating a panel (super simple) and some code just to test the hookups for the techs so they can get out as quick as possible. i.e. a page for audio inputs and outputs, video inputs/outputs, power on/off for devices (TVs, DVD players, cable boxes, etc.)
Or do you just go there with the program, load it up, and let the techs know what doesn't work as you're testing the final system program & panel?
Or do you just go there with the program, load it up, and let the techs know what doesn't work as you're testing the final system program & panel?
0
Comments
For larger jobs I try to schedule a time with the installers as a handover, where we check everything is correct for me to implement. This often depends on whether the hardware has been in the workshop first tho.
but we assemble the entire system here in the shop and completely program the entire project. After it has been completely tested, the client comes to visit it and signs off.
Then it goes to installation at the premisis. I try to no programming at the client's house or business.
It works very well because she has an extreme attention to detail. She loads code to the master and tests every control port as well as making sure she can see every video source on every display and hear every audio source through every speaker. It means that by the time the programmer/engineer get out on site, we know everything works and just needs to be configured.
I'm convinced that on jobs where this whole process works, we work MUCH more efficiently, and things go much faster, and the client gets a better system in the end. We're still working out kinks in the system, but its great to know that when I go out to a site, it all . . . works.
J
Jeff - I see you're working for a new company. Congrats! Hope you're enjoying it!
J
I guess it depends on whether you are responsible for just the control system or the whole install - generally I have to act as the commissioning / handover engineer and so I have to ensure that the whole system operates correctly. The installers should test everything, but sometimes with big matrix switchers or distro systems you need to give them a tool to help - then your job on-site is much easier...
If anyone would like a case study on how NOT to do things, please come visit me in the EDU department. We seem to have the knack for doing a lousy job in the poorest, most inefficient way conceivable. I'd send a few pics of recent installs, but I'm really, truly embarrassed...
while I was at Nebraska University, there was the 'right' way, the 'wrong' way and the 'UNL' way. Large institutions are not bastiens of efficiency... That's for sure.
Now I work for a company with 25 or so people. We do things entirely differently. We have no organization and everyone wears 50 hats. I sometimes find myself longing for the comfort of 4 very strict walls around me.
I thinks it's the human condition. the grass is always greener on the other side of the fence.
Glad you're liking it. Getting to full time programmer status is definitely rewarding.
Be sure not to show us the President's house! That is an absolute mess!
In most cases we have to adjust the RS-232 commands to get the module working. So the code that we use in the main program is almost the same as any other program.
So, we only have to test the module if all the function's are working and adjust it where it must
Further I only go to a location if the software must be fine-tuned or if there a problems.