Can Scorpion log data to files?

Read more – Scorpion Data Logging

With the release of Scorpion Vision Version X we have added a very good and easy to use module to provide dynamic data logging of calculated values and values measured from other input devices.

All functions are provided without any programming or scripting.

Click to check the Scorpion Data Logger Status Panel

Do we support QRCodes?

With Scorpion Vision 10.1 we support QRCodes with the updated STC-0006-Barcode 1.0.0.8 and the new STC-0070-ZBar 1.0.0.3

Supporting QRCodes

Do you have a 3D Stereo Vision Lens Calculator?

Scorpion 3D Stinger Camera

To support our Scorpion 3D Stinger Camera we have created this new 3D lens calculator.

This calculator estimates the 3D FOV width, height  and the corresponding  pixel resolution at given minimum and maximum distance based on the following input

• The cameras CCD size,
• The image resolution,
• The lens size (focal length),
• The baseline distance between cameras,
• The minimum distance,
• The maximum distance.

Click to use the 3D Lens Calculator

Do you have a 2D Lens Calculator?

We have a nice 2D Lens Calculator – it is located at Scorpion Support Web.

Click to use the 2D Lens Calculator

Can I connect an AVT GigE camera to Scorpion Vision?

Yes – please follow this procedure:

1. Read the description of the camera driver
   • http://scorpion.tordivel.no/help/Camera%20Support/2D%20Area%20Scan/Prosilica/Default.htm
2. Change Scorpion camera driver to PvGrab.dll
3. Download the AVT PvApi driver from AVT
   • http://www.alliedvisiontec.com/us/products/software/windows/avt-pvapi-sdk.html
4. Configure your network card correctly

Good luck !

 

Autologon on Windows-8

This is still possible

– http://www.ghacks.net/2011/09/16/windows-8-how-to-automatically-log-on/

Do we support IP-Cameras and GigE Cameras?

Yes we do 🙂

The latest additions are implemented through the DirectShow driver firegrab.dll

• More about Scorpion Camera Drivers

The DirectShow driver supports basically all firewire cameras and usb cameras with a vdm-driver. Many ip-cameras and gige cameras can also be supported using the same Scorpion Camera Driver – firegrab.dll

The latest firegrab.dll versions 3.0.0.43 and 3.0.0.44 is updated to support:

• All Imaging Source cameras including GigE cameras through their WDM-driver
• All IP-Cameras supported by Azcendant IP-Camera filter
• Active GigE WDM-driver from A&B Software

Release notes and actual FireGrab.dll Scorpion Camera Driver.

3.0.0.44 – 27jun2012, min Scorpion Vision Software version: 7.x.x.x – DirectX 7.0

• improved driver initialization
  • Tested with Imaging Source WDM-driver
  • Tested with ActiveGige driver with PixelLink GigE
  • some GigE cameras caused application lock

3.0.0.43 – 07jun2012, min Scorpion Vision Software version: 7.x.x.x – DirectX 7.0

• added configurable timeout on camera opening (configurable in inifile)
  • suited for IP camera drivers

What to do when Scorpion throws an exception shutting down?

This is not very likely – but this will work in many cases. The root cause of this is due to a weakness when hosting .net 2.0 in an application like Scorpion Vision Software.

3. Hint – Exit Code Exception

If you receive unhandled exceptions on Scorpion exit add code to Central Stop to stop event solvers:

# manually call application domain shutdown
import clr
import System
tp = System.Type.GetType(‘Microsoft.Win32.SystemEvents, System, Version=2.0.0.0, Culture=neutral, PublicKyToken=b77a5c561934e089’)
mi = tp.GetMethod(‘Shutdown’, System.Reflection.BindingFlags.NonPublic | System.Reflection.BindingFlags.Static, None, [], [])
mi.Invoke(None, [])

Read more…

Note: This is only needed if you use .Net in your Scorpion Vision System

Why and when continous triggering?

The continuous triggering in Scorpion was designed to make it possible to captures 10 – 200 images/second. The initial and simple image aquisition model defined by this pattern:

1. Issue the Grab command
2. Wait for all ImageComplete events
3. Issue the Inspect to process the aquired images
4. Use the AfterInspection event to do IO
5. Goto 1 or Stop the inspection cycle

Read the details explanation about the event-driven model in Scorpion – http://scorpion.tordivel.no/help/UsersGuide/Service/Actions/Default.htm

The simple model has a drawback when the camera is free-running or the system is hardware triggered if you want to run fast. The Grab command takes time and can be eliminated. This changes the basic models from:

1. Issue the Grab command
2. Wait for all ImageComplete events
3. Goto 1

to the continous model

1. Wait for all ImageComplete events
2. Goto 1

The difference is the Grab command is implicit and not explicit in the continous model. The continous model is supported by most Scorpion Camera Drivers.

The implicit Grab command saves milliseconds which is important when running fast 20-100 images / second with a cycle time of 10 – 50 ms. It is more important the faster it goes.

The drawback with the continuous model is that Scorpion Vision might the pushed to hard – too many images might flow into the system and what we call “cpu-starvation” might occur. This may happen if images are pushed to hard into Scorpion or maybe the is noise on the hardware trigger input.

Important Rule of thumb:  The basic image capture model is the best if you do not need the speed of the continuous model.

How to read a RS-232 port from python?

Check the python example in the on-line help.

http://scorpion.tordivel.no/help/Python/Examples/Example_13.htm