F1 Driver Camera
Tillie
compatibility issue encountered while I attempting to utilize an old frame grabber model, AS-PHX-D48CL-PE1, with the DCAM-API version 19.12.5902 for a Hamamatsu TDI line scan detector (12300-321). The system failed to recognize the frame grabber. As a potential solution, the request is made to obtain the DCAM-API version 15, which is believed to include the appropriate driver for the AS-PHX-D48CL-PE1 frame grabber. So please let me know if it is possible for you to share your DCAM-API v15 to driver my frame grabber?
I have a WIN7 64-bit system that I would like to use with two USB 3 Vision cameras (both are The Imaging Source DFK 24UJ003), one of which works fine with the IC Capture software. The other camera can be opened with IC Capture but will only show up with a frame rate of 1fps, no matter what size I set it to.
I can open them in Measurement and Automation Explorer, but they do not show up under NI-IMAQdx in the tree. When I click on Software in the MAX tree below, NI-IMAQdx does show up as being installed (14.5). The camera (and NI) instructions say to change the camera driver to one found in C:\Program Files\National Instruments\NI-IMAQdx\Staging\NI USB3 Vision, but my driver is located in C:\Program Files (x86)\National Instruments\NI-IMAQdx\Staging\NI USB3 Vision.
This makes it sound like the driver is in the wrong place or it is not made for a 64-bit OS. Any advice on how to switch them over from the TIS drivers to the NI-IMAQdx drivers and also how to increase the frame rate of the second camera would be very much appreciated.
The installer put the IMAQdx driver in the expected location for an x64-based system and it always puts the correct bitness of driver down for the system you installed. My hunch is that the camera is not exposing a USB3 Vision interface for the driver to bind to.
Thanks for your reply, I had not realized that not all USB 3.0 cameras are compatible with NI Vision products. I'll look out for that the next time I purchase cameras. In the meantime, I found that the issue with the frame rate was caused by a different problem, so it's fixed now.
Can someone clarify what is the recommended approach for adding additional camera support to TX2 NX besides the few IMX sensors that are built in the kernel? Specifically, should I use LKM, kernel overlay with or without jetson-io tool, full kernel build from source, patch files, etc.? I see many different approaches on the forums and documentation but no tutorials from beginning to end and I am missing something. This seems like a topic that would benefit many people as cameras are constantly changing and computer vision is fundamental to the reason the Jetson platform is so popular.
Managed to install and configure the IP Camera (fixed, with H264) Driver (dated 12/18/2014) and am able to get the rtsp stream displaying on Apple IOS Control4 UI for each camera My camera does not support Snapshot URL or HTTP MJPEG Stream - only support RTSP.
However when you use the UI to navigate from Security-->Camera there is a grid of all the cameras but all with a waiting circle spinning round and round. Is there anyway to configure this so that it uses the RTSP stream?
I'm using this generic IP driver for a Bosch Flexidome Camera at a client's house, and I've got the camera working fine, however the snapshot isn't working for the thumbnail when I'm in the cameras page. Any ideas on how to fix this? Or if it is possible? Thanks in advance.
Of course, right after posting this I tried a few more things and was able to get it working. For anyone having issues with the same thing, what I had to do was change the .jpeg snapshot URL to " :80/snap.jpg?"
While this used to function before, after a certain Beam.NG update, the camera fixture is not recognized.
I have not checked the last couple of weeks, as that might have been resolved in the meantime.
Looking at the website recently to see if there is an update for this driver, I cannot find that driver listed, only the ASCOM driver with a version 6.5.1.12. This is so different in version number from the one I am currently running - that I am concerned -- and not comfortable installing that driver.
Hello there. On the ZWO website under the software tab you will find two camera drivers available for download. The ASI Camera driver v3.17 is the native ZWO driver and is required if your software will natively operate the camera. This means you should see a choice in the software that says ZWO camera. The other camera driver ASI ASCOM v6.5.1.12 is for any software package that will run your ZWO camera using ASCOM. This is where you will see choices in the software that says ASI Camera1 and ASI Camera 2. Hope this helps.
Thanks jsmithsd!
So I'm assuming that if I have the ASI Camera ASCOM Driver 1.0.4.3 installed NOW that is what allows me to communicate with the ZWO Cameras via ASCOM - as I do from Sequence Generator Pro, I wound need to UNINSTALL the ASI Camera ASCOM Driver 1.0.4.3 before installing the ASI ASCOM DRIVER? or will that install do that for me?
If the operating system does not detect the camera, you must first make sure that the camera drivers are installed. In addition, do not forget that manufacturers of webcams strongly recommend installing the latest drivers. If you do not have the CD and installation files for your webcam, first of all, try to find them on the manufacturer's official website. If you could not find them there, do not hesitate to download free webcam drivers from our website.
My camera wasn't working with Zoom and showed up as a hidden device in Device Manager. I uninstalled the device for the TrueVision HD camera (big mistake) and restarted. Once restarted, in Device Manager the camera driver is now a generic Microsoft USB driver. The camera works, but with really bad quality. I had previously done a clean Windows install when I upgraded to an SSD drive, so I do not have the TrueVision software or any of the ancillary software that came with the laptop.
I want to use this for a semi-3D project with a lot of greenscreen cardboard cutouts and this means I can have everything automatically face whichever camera is active, and have some objects only visible for certian cameras. It means I can edit in scene, which is much better for the fast cutting style I want to go for.
my presario cq60 111em with built in webcam now has a problem when l launch youcam a message appears that the webcam is not reconised and I can not find it with the device manager, wondered if the driver is missing any ideas.
Sometimes - apparently - there is a BIOS update that fixes it. I'm not a fan of BIOS update unless it's indicated. You must be sure to update your bios with YOUR bios update. Get the BIOS update from your computer's website and not from someone else's link. If you do that, you will be fine. It may not fix your webcam, but at least you won't turn your computer into a fancy, expensive paper weight. We have some very good HP experts here on the forum that can (and do) recommend BIOS links and they can be trusted - my point is to not use a link meant for someone else's computer unles that computer matches your computer EXACTLY. If there is a BIOS update for your computer, it will be at your computer's website and you can track it down easily. Again, it may or may not fix the webcam.
The other thing that happens to these webcams is that they do sometimes just fail due to hardware. It is sometimes the little wires that come loose. If your notebook is no longer under warranty and you have the skill set to do it, you might consider taking apart the notebook and checking the wires. This is not your average DYI job - it is another way to make a fancy, expensive paper weight if you don't know what you are doing. On the other hand, it's not on the upper end of difficulty as repairs go. Some notebooks have very good online hardware manuals, and there are some very good YouTube how-to videos out there on repairs.
There is one story (here in the forum) about someone who swatted his webcam into submission. He doesn't recommend it and admits to anger management issues - it is a testament to the loose wire problem. I bought a dv7t last summer and had to send it back for repair: webcam came DOA out of the box. Sad.
Sometimes it is the WAY in which the driver is loaded. You might be able to trick it. Try installing it from the SWSetup (the way you did this time) and that kicks it. IF it's software, you might be able to NOW, delete it and then install the NEW one from the downloaded version. NOT the SWsetup one again, the one from the website - DELETE the one you have.
4a15465005