Home› AMX User Forum› NetLinx Studio

System Testing

jjamesjjames Posts: 2,908
in NetLinx Studio
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?

Comments

  • Jimweir192Jimweir192 Posts: 502
    I've done small test programs with a command for each key function on a single page with feedback locked with a "clear last" and "Clear All" button. On site the installers can work through and see where they've got to or clear and start again.

    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.
  • ericmedleyericmedley Posts: 4,177
    I don't know if this answers the question or not...


    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.
  • JeffJeff Posts: 374
    We have an engineer on staff who reads/writes/executes both amx and its major competitor. She has her own jobs, but she also performs QC on every other job done within the company. She has an install tech permanently assigned to her and they go out to jobs after the installers and before the engineers.

    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
  • jjamesjjames Posts: 2,908
    Sounds good everyone! I'd love to have a "setup" like any of you have mentioned; what we do kinda works for us, it just feels like we run around like chickens with our heads cut off at times.

    Jeff - I see you're working for a new company. Congrats! Hope you're enjoying it!
  • jweatherjweather Posts: 320
    I've created some "installer pages" for projector setup and such, but nothing for functionality testing. Generally a particular device either works 0% or 100%, and that's generally due to wiring or baud rate issues. I frequently have a page that indicates the status of each device with 2-way feedback so installers don't call me and tell me the projector doesn't work before they actually get it wired and talking.
  • JeffJeff Posts: 374
    I'm loving it :) Yay for being a programmer full time and not a programmer part time and the Fn+F8 flunky the rest of the time.

    J
  • Jimweir192Jimweir192 Posts: 502
    jweather wrote: »
    I've created some "installer pages" for projector setup and such, but nothing for functionality testing. Generally a particular device either works 0% or 100%, and that's generally due to wiring or baud rate issues.

    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...
  • fogled@mizzoufogled@mizzou Posts: 549
    Unfortunately, I'm the programmer AND the install tester/QA/cleanup guy. I rarely get to put the system together in the shop and test it first (and boy am I jealous of an organization that really does this!). It's amazing how often I have to fire up the solder gun and swap pins 2-3 on serial devices, finish wiring myself, or worse, reverse-engineer an off-schematic wiring job. Not that anyone will actually help me do design or UI reviews in the first place.

    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...
  • ericmedleyericmedley Posts: 4,177
    fogled@mizzou wrote: »
    Unfortunately, I'm the programmer AND the install tester/QA/cleanup guy. I rarely get to put the system together in the shop and test it first (and boy am I jealous of an organization that really does this!). It's amazing how often I have to fire up the solder gun and swap pins 2-3 on serial devices, finish wiring myself, or worse, reverse-engineer an off-schematic wiring job. Not that anyone will actually help me do design or UI reviews in the first place.

    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...


    :D

    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.
  • jjamesjjames Posts: 2,908
    jweather wrote: »
    Generally a particular device either works 0% or 100%, and that's generally due to wiring or baud rate issues.
    Exactly. We're trying to find the hardware problems before our installers move on to the next job. Typically we'll have a few devices that might be wired wrong (null instead of straight through, etc.) and we want to test video routing, etc.
    Jeff wrote: »
    I'm loving it :) Yay for being a programmer full time and not a programmer part time and the Fn+F8 flunky the rest of the time.
    Glad you're liking it. Getting to full time programmer status is definitely rewarding.
    fogled@mizzou wrote: »
    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...
    Be sure not to show us the President's house! That is an absolute mess! :D
  • PetarPetar Posts: 14
    We are making modules for projectors, conference systems and camera control.

    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.
Sign In or Register to comment.