| Why doesn't my PC boot since I have installed the frame grabber?
|
 |
Please put the grabber once more into the same slot.
If the problem still exists try another PCI slot or another frame grabber if possible. |
|
|
| My PC boots after driver or software update, but why does it show a blue screen? |
 |
Did you get an error message at deinstallation?
If you did so, the driver probably hasn't been correctly deinstalled. Please pull out the frame grabber and reboot your system. Start the explorer and change into the directory "C: \ WINNT \ system32 \ drivers".
If there exists a file called menable3_0.sys, please delete it and deinstall also the microEnable frame grabber software by using "Start | Settings | Control Panel | Software". Shut off your PC, put the frame grabber into the slot and boot once again. After this you're able to install the software. |
|
|
|
| Why doesn't the system detect the grabber? |
 |
Please take a look at the device manager "Start | Settings | Control Panel | System | Hardware | Device Manager" whether there is an entry which is called "menable3_0".
If there isn't such an entry the driver has to be installed. |
 |
If the driver has already been installed and this device is red marked in the device manager take a look at the properties where the problem is described and an error number is named. Look at the driver informations in the registry or let us know about this error number. |
 |
Here is another hint: At boot some information are shown. Also there are some details about processors. Here the frame grabber should be displayed.
If this is the case please install the hardware manually.
If this is not the case it is possibly an EEPROM fault. Check whether the mainboard gets 3.3 V. If neccessary you could connect external power to the grabber. |
|
|
|
| The system doesn't detect the grabber and why can't I install the driver? |
 |
If there is another free PCI slot plug the grabber into it.
If this problem still exists probably the EEPROM of the frame grabber has been overwritten so that the board will have to be send to SILICONSOFTWARE or your distributor. It is possible to send another board to you in change. |
|
|
|
| The system doesn't detect the board although the driver has been installed. Why? |
 |
Please restart the system if it hasn't already been done. |
 |
If version of driver and version of software installation don't fit together, please install the correct version(s). |
 |
If an microEnable I Board has been installed before please take a look at "Registry informations" at the end of this FAQ list. |
|
|
|
| Board will be detected as PCI bridge or coprocessor and why can't I install the driver? |
 |
Probably the EEPROM of the frame grabber has been overwritten so please send this frame grabber to Silicon Software for repair. It is possible to send another board to you in change. |
|
|
|
| The system detects the grabber, but why can't I install the driver? |
 |
If the board is be detected as a coprocessor or PCI bridge please send the frame grabber back to Silicon Software.
Probably the EEPROM of the frame grabber has been overwritten. It is possible to send another board to you in change. |
|
|
|
| Board has been detected, but why can't I configure it? |
 |
Please install Service Pack 1 or higher under Windows XP if it hasn't already been done. |
 |
If you get the error message "Mainboard error, req64 resistor missing" or "Mainboard Error, req 64 Widerstand fehlt" at test run of diagnose tool, the microEnable III won't probably be detected because of a missing resistor on the mainboard / motherboard which lets the system not detect the board as a 64 bit board.
A counter on the mainboard / motherboard has overrun and has to be set back. Please try to turn off your PC over night. If the problem still exists after booting, please contact the mainboard / motherboard manufacturer.
The microEnable III hardware revision 4.0 can be retrofited with a 2k2 resistor.
PLEASE NOTE: Hereby microEnable III loses the general PCI compatibility and any guarantee. |
|
|
|
| My PC hangs at start of microDisplay / at loading an applet / at start of diagnostic tool and doesn't react on keyboard or mouse events. Can you help me? |
 |
If you have also a problem with a Raid Controller ("Start | Settings | Control Panel | System | Hardware | Device Manager"), please turn it off in your BIOS. |
|
|
|
| I get the following error: "dlError: (null) / dll / me_grab2 // foo / SingleAreaGray.so: cannot open shared object file: No such file or directory." What can I do? |
 |
It is neccessary to mount the shm file system. shm is a virtual disk which is able to use the shared memory (shm). This means that two separate processes are able to share the memory segment. Newer linux versions automatically mount this file system. You can also mount it manually as a command as follows:
- mount -t shm shmfs /dev/shm
|
|
|
|
| Why doesn't the system react on keyboard and mouse events anymore since I have chosen an applet? |
 |
Try to start the diagnose software and let us know about the results by sending the logging file to Silicon Software. You can find the log file within the directory "SiliconSoftware \ bin".
Probably the EEPROM of the frame grabber has been overwritten so that the board will have to be send to Silicon Software. It is possible to send another board to you in change. |
|
|
|
| Board doesn't communicate with my camera. Why? |
 |
If the camera can't be set to "Grabber controlled mode", please upgrade to version 2.4.0 or higher. |
|
|
|
| No image is shown. How do I get an image? |
 |
Please control whether your system has been correctly connected with corresponding components. |
 |
Check whether the diaphragm has been opened. |
 |
Please change cables, camera and frame grabber if possible. |
 |
Select another applet you haven't chosen before. |
 |
Check both ports. |
 |
Control your settings whether you chosed Single Tab. If you didn't, chose Single Tab if your camera allows it. |
 |
Check whether the camera runs in Free Running Mode. If it doesn't, change to it. |
|
|
|
| Images will be shown, but the diagnostic tool tells me that there are malfunctions. What's up with my frame grabber? |
 |
If you get also an error message that the frame grabber couldn't be initialized, please check another PCI slot for your frame grabber. |
 |
Please note that the hardware diagnostic tool checks only a general electronic reaction. Hereby a detailled hardware check doesn't take place. Because of this it is possible that supposed error messages are shown. However the microEnable III should be tested in running operation. Hereby a SDK example or microDisplay should be used. |
 |
This problem is solved with the software version 3.0.0. We developed the diagnosic tool completely new. It got a new look and feel and also the functionality has been completely revised. |
|
|
|
| In triggered mode no images or no whole image will be shown. How do I get the (whole) images? |
 |
If only black, white or half the image is shown please change the exposure polarity to "Low active" or "High active". |
|
|
|
| The status (red cross, green hook respectively) doesn't change after entering the license data. What shall I do? |
 |
Please control the entered data. |
 |
Check whether you used the correct license file for your grabber. The serial number has to be the same. |
 |
Before entering the license data it is neccessary that you load a free applet (green hook), e. g. SingleAreaGray. |
 |
Please note that you close and reopen microDisplay after entering the license data. |
 |
Check whether the diagnostic tool shows an error message. A correct installation is neccessary for a successful licensing. |
 |
Check the file properties "attributes" of the license file whether the status is NOT write protected. If this is the case please change this value. |
|
|
|
| Why won't the license code be accepted? |
 |
Please use the correct license file and code for your frame grabber. Check the serial number. |
 |
Before entering the license data it is neccessary that you load a free applet (green hook), e. g. SingleAreaGray. |
 |
Please note that you close and reopen microDisplay after entering the license data. |
 |
Please open the *.lic file with notepad e. g. Enter this code manually in microDisplay into the corresponding fields. If the code still won't be accepted, please let SILICONSOFTWARE or your distributor know and you will get the correct license code. |
|
|
|
| Registry informations |
 |
Please call the program "regedit": Klick "Start | Run", enter "regedit" and klick "OK". Change into the directory "HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services" and search "menable3_0" ("menable3_0" for the first board, "menable3_1" for the second etc.) in it. Check
- whether the board is active (The entry "Active" is set to 1.) and
- whether there is shown an error (The entry "Error" isn't set to 0.).
If an error is shown, please let SILICONSOFTWARE or your distributor know about it. |