You can download the software from our Developer Resources. Then, all you need is your Sales Order (SO) number. You may refer to question number 8 for more details about the sales order.
If you want to learn more, please visit our website HBVCAM.
Please follow the below instruction.
Here's a step-by-step instruction to register and download the files from our Developer Website.
e-con Systems will provide basic support on the evaluation for all the customers who have purchased the camera. We will help in choosing the best compatible camera based on the application use case of the customer. This will help the customer to choose the right product for their system. e-con Systems will also provide hardware/software/firmware customizations like form factor, interface type, IP rating, and lens mount based on your requirements.
If you purchase any of our camera products in the online web store, we will ship them as per the lead time of the particular camera. As we use FedEx/UPS/DHL for shipping, it will take additional 3-4 business days to reach your place from the date of shipment.
A Sales Order (SO) number is a numeric code assigned to a particular request to buy our camera products. You can download the required files and software from our Developer Website using the SO number of your purchase of our camera products. Refer to question 1 for step-by-step instructions to register and download the files from our Developer Website.
Yes, e-con Systems' cameras in mass production are NDAA-compliant. We prioritize security and regulatory compliance in our camera solutions, ensuring they meet the standards outlined in the National Defense Authorization Act (NDAA). For more information, please refer to our blog post. If you have further questions or need assistance, feel free to reach out to us at .
By default, the camera is in auto exposure mode. When the scene has low-light conditions, the auto exposure algorithm will increase the exposure time, thus reducing the frame rate. You can set the maximum exposure limit using exposure compensation in the Extension Control menu or choose manual exposure to get desired frame rates. specific to the frame rate (to get 60fps, the maximum exposure time must be 1/60 => 16.66 milliseconds).
Our USB cameras are UVC-compliant and do not require any special camera drivers to be installed on the host PC. It's just a plug-and-play device. For Windows, by default, the MJPEC codec will be installed when installing e-CAMView. However, the codec might have failed to install in some cases, resulting in an MJPG stream preview. You need to install the MJPEG codec to camera streaming MJPG format. Please go to the e-CAMView installed directory "C:\Program Files (x86)\e-con Systems\e-CAMView" and install the "MJPEGCodec_RETAIL". Refer to the below image for your reference and then check the MJEPG.
Also, camera-related documents can be downloaded from our Developer Website, as mentioned in question 1.
This may be due to bandwidth limitations in the USB host. It can occur when multiple cameras are connected to a single USB host or in USB hosts of less powerful embedded boards. Read this blog for more information on USB practical bandwidths. For MJPEG, reducing the Q-Factor will improve the FPS and stability in case of any issues. If still required, reduce the frame rates.
Our USB camera has some additional controls and features, and these are not quite common controls. Hence they are not included in the standard UVC controls but are listed as UVC Extension controls. We have provided the extension unit SDK package to access the Extension Unit controls. The extension unit SDK package and API document can be downloaded from Developer Resources, as answered in question 1.
We have developed an OpenCV-based sample application v4.5.5 - OpenCVCam, a command line application for streaming and image capture, along with the support for standard UVC controls of e-con Systems' cameras in Windows and Linux.
https://github.com/econsystems/opencv
Please refer to the installation manual to install the OpenCVCam application from here: https://github.com/econsystems/opencv/tree/master/Documents
Yes. Our USB cameras are UVC-compliant and do not require any special camera drivers to be installed on the host PC. It's just a plug-and-play device. The native UVC drivers of Linux Operating Systems shall be compatible with this camera. It should work with any direct show and V4L2 application. For more details, please refer to this blog.
In Linux, the firmware version can be obtained by using our QtCAM application. Please go to the Extension Setting tab and click on the Firmware version. In Windows, the firmware version can be obtained using our e-CAMView application. Please go to the UVC Extension menu and click on the Firmware version.
Yes. All our USB color cameras have an inbuilt ISP (Image Signal Processor). Our color camera has an onboard ISP to perform major image processing functions like debayering, WB control, Color correction and other image quality improvement features, reducing the processing load in the host platform. You could use any direct show and V4L2-based applications to access our camera.
Sorry if this is a repeat question, I did not see it in this forum yet however. I am a relatively new user and I just got PrusaLink set up today.
I see that USB webcam is supported on the current rc2, does this mean a pi camera module is also supported such as Arducam conneted to the CSI interface on the pi zero 2? Or is this already supported is some other fashion?
Thanks!
Posted : 02/01/ 8:55 pmThe CSI-connected camera support was in place in some form in RC2 briefly but didn't work for me. Soon after, they have pulled and then re-released RC2 without the support (USB cams only) due to some problems. I hope those are just temporary and we'll see full CSI-cam support soon but let's wait for @tojik to comment.
Posted : 03/01/ 12:01 pmYup, I tried to get RC2 out but i stopped short after creating the tag. I had no release notes yet. I pulled the PiCamera support attempt after realising that literally only the RPi Camera V2 module worked. Now getting up to speed with the forum and stuff, then it's RPi Camera time again.
Posted : 03/01/ 4:32 pmHmm... I have RPi Camera V2, although the "NoIR" version (this one: https://www.raspberrypi.com/products/pi-noir-camera-v2/) and it wasn't working for me. It was getting to the point where it was seeing the camera and offering to configure it (don't remember the exact wording) but then nothing was happening after I clicked this.
Posted : 03/01/ 5:01 pm Topic starter answered:Ahh gotcha, thanks for the replies. Good luck with the progress, I'm happy to help test with my RPi camera (Arducam IMX219) if you get it up and running.
I have a USB Arducam ( https://www.amazon.com/gp/product/BKK7BC/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1) on the way, should this one work since its USB?
Posted : 03/01/ 5:17 pmI hope it will. I tested over 10 different webcams, so if this one behaves like a webcam, it should show up.
Posted : 03/01/ 5:24 pmI tried connected my an old webcam to the RPI Zero 2 W usb port and I was unable to see it. Where should I be looking for it Prusa Link screen?
For more USB Camera Moduleinformation, please contact us. We will provide professional answers.
Posted : 05/01/ 9:03 pmFor camera support you'll need the 0.7.0 RC2. You can download it here:  https://github.com/prusa3d/Prusa-Link/releases/download/0.7.0rc2/PrusaLink-0.7.0rc2.img.gz 
You should see your cameras in PrusaLink local web interface. In there, you can link the cameras to Connect, so you'll see your images in there too.
Can that be upgraded from the Prusa Link interface or do I need to remove the uSD card and reimage it?
By default ssh is disabled so I can't ssh into it.
Posted : 05/01/ 10:25 pmSorry, it cannot be upgraded in place, you'll need to re-flash the image. You can backup most of your printer settings in connect under settings -> Lan settings
Posted : 05/01/ 10:28 pmThis might be a feature to add in the future. Having to remove the RPI from the printer and remove and re-image the card is kind of a big deal.
It would be nice if the standard Debian apt or apt-get was able to update the OctoPrint/PrusaLink server.
The installation documentation says to not enable SSH or create a login. Is there a specific reason for this or is it just to avoid unnecessary complications on the setup process?
Most of my Raspberry Pi based systems have a sudo apt update and then a sudo apt upgrade running as a daily cron job.
Posted : 05/01/ 11:13 pmYup, that would be convenient. So far, we're modifying the image too much inbetween versions, so you'd end up without some image specific features like automatic config copying from the boot partition (broken for prusa_printer_settings.ini in 0.7.0 RC2 tho :/ fixed it yesterday). We know we need an updater, but the focus is still cameras. Pi cameras specifically.
Posted : 05/01/ 11:23 pmI was going to order a pi camera for just that purpose I just haven't selected one yet. And then I need to select a mount for it.
That is why I am planning on using an old webcam I have laying around for now.
Thank you for your efforts.
Posted : 05/01/ 11:34 pmCurrently using a Zero 2w 7.0r2 with Arducam Pi Camera connected to the pi.. just waiting to find out when to push the trigger to update as ssh pi wont let me in saying the password is wrong when I know the default >:(
Posted : 06/01/ 4:44 amWe changed the defaults and probably did not tell anybody, the official guide is still being made. The default user is now "jo" and we are working towards not having a default password. Not there yet. So it's still the default
Posted : 06/01/ 10:15 amDo i understand correctly that in the current 0.7.0rc2 only the official Pi Camera V2 is working over CSI?
That would explain why my MakerHawk IR CSI camera is not working on my Pi Zero 2W.
Best regards,
Mark 
Hi, no CSI cameras work in 0.7.0 RC2, I had one solution ready and that turned out to be very unreliable
Posted : 09/01/ 12:47 pmAh, okay, thank you! Then i will wait for a future release to setup my camera!
Posted : 09/01/ 12:48 pmTojik,
Thank you for your help. I installed the file you pointed me to. Connected my generic WinBook USB Wifi camera to the Pi Zero 2 W and everything is working perfectly.
I have a couple of questions:
1. When the camera is set to manual trigger mode how do I trigger it?
2. Is they any way to either stream live video or increase the trigger speed to something faster than 10 seconds. I would recommend a setting of live and then instead of having 10, 30 or 60 seconds just let the user set the trigger time in 100mS increments from 100mS up to some maximum based of the size of your counter. If you use a 16 bit counter its like 109 minutes, if you use a 32 bit counter it's so high that it's not worth mentioning.
Thanks again,
Mike
Posted : 09/01/ 5:37 pmThe setting UI is not the problem and PrusaLink is written in python so we are not limited by data types either. We however need to upload the photos in a reasonable interval, because each photo costs money. More photos - more money lost. We are thinking about only shooting when the printer is actually doing something like moving or printing to save even more bandwidth. The local video preview would be probably nice, but it's a different and harder thing to code compared to photos and we'd have to disable it on the original zero. Maybe it'll get re-visited someday.
The easiest way to let you see what's happening would be to add a manual refresh button tho.
The manual trigger scheme allows you to trigger the camera using the web API, but so far, it is not used.
The company is the world’s best USB Global Shutter Camera Module supplier. We are your one-stop shop for all needs. Our staff are highly-specialized and will help you find the product you need.
Posted : 09/01/ 6:32 pm Page 1 / 2 Next
Comments
Please Join Us to post.
0