Monday blues



  • The company I am doing work for has a contract to deliver a vision system to a client. I wasn't part of the team that met with the client and discussed the overall architecture of the system, but I have been tapped to do the back end bit fiddling to interface the vision system to the clients system. The team in question was the vision system expert and the project manager. After meeting with the client they produced a nice design spec detailing how they would use architecture "A" for the job and sent it off to me to estimate how much work it would take me etc.

    I looked at the design spec and said to myself "thats a crazy architecture" and went about coming up with a set of questions to try and fill the obvious gaps in the document, and to question some of the craziness. Some of which involved me having to deliver VB6 code for a vision system and a client system that both expose a nice set of .Net interfaces, and why they weren't using architecture "B" which we have used in the past and would be better suited to the job.

    Those questions prompted a conference call between me, the Vision guy and the project manager. The project manager was convinced that I had to deliver VB6 code (and he has a fixation with VB, even though I am delivering products with C#) and that Architecture "A" was the way to go. Then when the vision guy started to say that he thought the client wanted Architecture "B", the project manager smacked him down by insisting that the client had wanted "A". The end result of that conference was for me to call the client's technical lead up an clarify the technologies to use (VB6 vs .Net).

    So I call the client and find out that yes .Net technologies are the way to go. Then I started to ask about this Architecture "A" that he wanted. I didn't get too far into that when he came back with "Architecture "A"?? I didn't want that, I wanted Architecture "B" ". So I mentally slapped my forehead with a quiet D'oh. Politely finished up the call and then then called the project manager to tell him the news.

    This has resulted in the design spec being sent out to the client with a nice implied question of "this is what you wanted, isn't it????'.

    All of this for a fairly rush job that has to be delivered next week.



  •  OK, so... what does "vision system" mean? Something about computers seeing things? And is a Vision guy like a seeing eye dog, you know, blonde and wearing a harness? Enquiring minds want to know 🙂



  • @rosko said:

     OK, so... what does "vision system" mean?

    In general a vision system is a effectively a digital camera with a slew of image processing routines available in software - in the camera itself - that are typically used for inspection of parts in a production line. The camera is then a self contained system which you point at your production line and as each part falls under the camera it can tell you things from pass/fail to more complex things like counting the number of user defined features and providing a list of locations of those features. In addition that camera's software can do things like automatically compensate for the part being rotated/translated in its field of view - so you don't have to worry about orientation of the part you are inspecting

    We will be using Cognex systems in this particular job - which I believe is testing modules destined for a cars ABS unit. The application that will be programmed into the camera will inspect a part, count the number of holes in that part, test the holes for being within a certain tolerance, and that the holes are found where they are expected to be in the part

    A "vision guy" is a product specialist who knows the best way to program the camera to achieve the required results and - probably more importantly - knows how to set up the lighting in order to get a good image



  • @OzPeter said:

    count the number of holes in that part

    Does it include a laser for adding more holes as needed?



  • no, he just can't get vision systems with frikken laser beams.



  • @Carnildo said:

    @OzPeter said:
    count the number of holes in that part

    Does it include a laser for adding more holes as needed?
    And suture if there are too many?


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.