February 2007

Sun Mon Tue Wed Thu Fri Sat
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28      
Blog powered by Typepad

« What's missing this year? | Main | PDC Downloads »

Comments

Michael Ashe

I wish we had an interface into assigning drivers in MAX for items like IEEE-1394 cameras. Recently we tried to use Firewire extension cables and/or hubs with Basler A601/2 cameras. We had to assign the NI 1394 driver to each camera. All was fine until power down or reboot, then the cameras were no longer recognized until we went into MAX and manually reassigned each to the NI driver. This is not something we could expect the customer to do. They need to turn the machine on and run. We were told that at this time and for the short term future no programmatic interface into MAX was possible.
Thanks,
Mike

Brian Tyler

I can't speak specifically on MAX or the team's workload, although you can be certain I'm talking to them about Monad. Unfortunately, Monad as a released product is still a ways out.

Johann

Sounds like a problem with the IEEE 1394 Camera driver and not the MAX interface. Can you continue this thread on the discussion forums (http://forums.ni.com/ni/board?board.id=200)? I believe resolution will come swiftly with more eyes (NI engineers, Alliance members, and customers) on the problem.

Michael Ashe

Plausible. We noticed the problem only when we used an extension cable or 1394 hub to connect the camera. When we went direct, with one standard 1394 cable we never had a problem.
At the time I did go to the NI Forums and Scott (of NI) told me of the issues and we traded posts and emails until it became apparant that we could not configure MAX to solve the problem. That was the motive behind my post to this blog. My point was, and remains, that whereever the problem lies, a programmatic interface into MAX for reconfiguration would have let me write a workaround or error handler that would fix the problem each time and move on. It turns out that there was a thread like this (http://forums.ni.com/ni/board/message?board.id=200&message.id=3568&view=by_threading&page=2)
recently enough that shows the 1394 driver 2.0 solves this problem. But I still want the API into MAX. It is a general need and has shown up on other projects. The tendency to only allow configuration with a graphical, neat tool like MAX is a problem. I had a project where the the customer wanted to use Fieldpoint and so did I. But after testing we found out that under certain conditions the configuration of the FP modules with the system got lost and the only solution was to manually go back into the nifty graphical tool. This was unacceptable to the customer and they went with Opto22 modules instead. I still got the software work, but lost the FP hardware sale and so did NI.
A Monad style interface into MAX would be great. Better, expose the API using standard application invoke/property nodes.

Johann

All aspects of camera configuration in the MAX provider happens through API calls in the camera driver. MAX is only a nifty frontend, but it is not required to work with the camera driver. We have other situations where some application replaces the functionality of MAX. Applications like Vision Assistant and Vision Builder for Automated Inspection.

The comments to this entry are closed.