Sorry, but I don't quite get what you are trying to achieve. You only need server-side (e.g. Node.js) code if your application requires image processing in the back-end.

Drawing pixels on the canvas in the browser requires careful handling of different RGB types and endianness. Please see the Image.toImageData() function. I'd however recommend using <img> instead. The cookbook recipe you are referring to uses <canvas> and toImageData(). Please let me know if that solves your problem.

It seems you have received the Image object and it was decoded successfully. There is something on the canvas as well, but it is hard to say what it is. Maybe you tried to draw a color image as RGB or vice versa? It looks like that there is at least a row alignment issue there.

The easiest way to display an image on an HTML page is to use an <img> element:

<img id="img-id">
...
obj.$image.connect(image => image.toHtmlImage(document.getElementById('img-id')));

In principle, yes. But unfortunately nothing that would just work out of the box. To be able to use all features of the camera you need a proper camera driver. On Linux this means either V4L2 or GenTL. The former requires a kernel module, the latter takes no stance. It can in principle be implemented in user space e.g. through command-line tools. You can create a custom GenTL driver as outlined here: https://doc.visionappster.com/latest/cameras/drivers/ The process is however quite tedious unless you are familiar with the intricacies of GenICam.

Another option is to create a custom tool for the purpose of getting images from the camera. Currently, this is only possible in C or C++ (see https://doc.visionappster.com/latest/api/tool/c/), but the next release will come with Python support.

I see. The Docker image only contains the Engine. To run the Builder on Mac, your only option is to use a virtual machine and use either the Windows or the Linux binary.

The Builder (and the Engine) actually do run on Mac, but Apple's SDK licensing terms prohibit building native extensions on non-Mac hardware. Since such extensions are the whole point of our business, Mac users are crippled. It is a big bummer, but nothing we can change.

The "VisionAppster" software distribution contains the Builder. The installer will ask you if you want to install a local instance of the Engine as well. All installers are available at https://download.visionappster.com/.

The fact that you need to ask tells me that we need to improve our message. Thanks for the question!

-Topi-

Hi,

3.0-beta4 is out with an official ARM Docker image: https://hub.docker.com/r/visionappster/va-engine-linux-arm_32

Sorry, I forgot the port in my answer. I'm however a bit puzzled by the log. The camera ID remote:http://192.168.2.59:2015/ webcam:video0 seems correct to me, but the log indicates an connection attempt was made to an URL without the slash after ":2015".
To make sure that the hardware gave the name "video0" to your camera, enter the URL http://192.168.2.59:2015/cameras/webcam%3Avideo0/ to a browser. If that works (you should get a directory listing), try re-entering the value shown in the picture. It should work.

Thanks for the report! We were able to reproduce the issue. It is a regression related to a fix in encoding camera IDs for the web page. We'll include a fix in the next release.

Meanwhile, to work around it in the Builder, you may manually enter a non-encoded camera ID to Image Source. For example, remote:http://192.168.0.1 webcam:video0. That is, decode %3A to :. If the camera URL contains other encoded characters, undo percent decoding for them as well.

We currently have an official Docker image for x86_64 only. For ARM, there is a Raspberry Pi image.

We however internally build Arch Linux packages for 32-bit and 64-bit ARM. The plan is to publish these and other binary packages in AUR. We'll also provide official Docker images for ARM. They will be built out of the Arch packages and an Arch base image such as this.

The schedule is still a bit open. If everything goes well, the new binary packages will be included in the next release in May.

Hi! I have to say this was totally unexpected. The history came haunt me. But thanks for your kind words.

Unfortunately, Defect Guard died with the company that created it. There are still a couple of installations running, but we couldn't make it work financially. I bet the simulator can still be found in the net somewhere, but VisionAppster is not in the business of web inspection.

That said, if there is enough demand, somebody may some day put a similar product on sale at visionappster.com or publish the original source code. Stay tuned.

BR,
Topi