FirePackage error codes

The following list provides an overview of FirePackage error codes and possible solutions. For details, refer to the corresponding User Guide or Manual.

  • HALER_NORESOURCES 9
    The number of available DMA channels exceeded when trying to allocate ISO resources. Simultaneous grabbing with multiple cameras at the same bus occupies one DMA channel for ISO transfer for each camera. Common 1394 cards have 4 DMA channels, only some LSI chips offer up to 8 DMA channels.
  • HALER_NOACK 11
    Asynchronous register access fails at the current speed, no acknowledge received. In most cases, the 1394 cable is damaged or too long. As a workaround, reduce the speed to S100.
  • HALER_NOBUSRESET 13
    A bus reset is incomplete or happens continuously. To find the cause, try to change the 1394 card, cable, hub, or other components.

  • HALER_NOLICENSE 14
    The license file is either installed in the wrong path, missing, or has a wrong content. The default file allows grabbing 5000 frames even with a non-licensed camera. More information:
    www.alliedvision.com/fileadmin/content/documents/products/cameras/various/appnote/1394/1394_camera_license_errors_troubleshooting.pdf

  • HALER_RCODEOTHER 15
    Response code of the requested register access is not ok. This register is not available, wrong address.

  • HALER_NOBUSRESOURCES 28
    Isochronous bandwidth is exceeded, for example, if multiple cameras share the same bus. At ISO speed S400, the PacketSize is limited to 4096 byte to be transferred in each bus cycle. In fact, PacketSize is specified up to 4915 and twice as much for S800. To avoid exceeding the bandwidth, reduce fps or PacketSize.

  • FCE_DRVVERSION 1016
    A wrong driver version is used. The version of the driver FireDrv.sys and the called DLL (for example, FGCamera.dll, FCTLMAIN.dll) has to match at the first two digits. Install the current driver and delete older DLLs.

  • HALERF_GRFOVERFLOW 0x00400000, HALERF_ISORXACK 0x00000100
    Corrupted data on the IEEE 1394 port are commonly caused by too much latency in the C3 power state in the case of a low CPU load, which causes buffer underruns. To find a solution, refer to:
    www.alliedvision.com/fileadmin/content/documents/products/cameras/various/appnote/1394/1394_corrupted_images_and_power_saving_issues.pdf




Zurück zur Übersicht