1. Rocky Logic Usb Devices Drivers
2. Rockylogic USB Devices Driver
3. Rocky Logic Usb Devices Driver Download
4. Rocky Logic Usb Devices Driver Update

• August 22, 2019 2.9.8

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.8	Released August 22, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added several internal interfaces for particular sensors (J003).

• January 25, 2019 2.9.6

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.6	Released January 25, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added missing Tonemapping Auto property.

• May 4, 2018 2.9.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.5	Released May 4, 2018	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.

• November 21, 2017 2.9.4

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.4	Released November 21, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Repaired not working J003 mono sensor pattern fix on particular video formats. This driver version is the last that works in Windows XP.

• January 9, 2017 2.9.3

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.3	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added a pattern fix for J003 mono sensors.

• January 9, 2017 2.9.1

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.1	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.

• January 15, 2016 2.8.9

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.9	Released January 15, 2016	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Changed certificates so that the driver can also be installed in Vista.

• November 9, 2015 2.8.7

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.7	Released November 9, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed an error which can appear when using sharpness on older CPUs.

• October 20, 2015 2.8.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.5	Released October 20, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed a bug which can appear on LivePause call.

• July 15, 2015 2.8.0

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.0	Released July 15, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support of DFK ECU010-L34 with serial number property. Added tone mapping.

• February 17, 2015 2.7.33

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.33	Released February 17, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.

• February 5, 2015 2.7.32

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.32	Released February 5, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.

• January 14, 2015 2.7.31

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.31	Released January 14, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support for IMX236 based cameras. Support for RGB64 color formats. Several performance improvements.

• June 6, 2014 2.7.9.1152

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.9.1152	Released June 6, 2014	Type ZIP	Filesize 2.1MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast. Added new property: Highlight reduction. Added new property: White balance temperature controls. Pixelfix for Y16 cameras now works as expected. VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.

• January 1, 2014 2.6.5.1014

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.6.5.1014	Released January 1, 2014	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed missing auto-gain for DFK AFU130. Fixed focus when start value is out of auto_focus_range. Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong. Fixed auto focus ROI not working for 21*UC cameras. Fixed crash on load/connect with certain cameras 22/72xUC. Fixed previous exposure settings not being loaded on reconnect. Complete reworking of internal property system. Fixed Windows XP driver load crash. Fixed drop counter to be accessible from DirectShow. Fixed Windows 8 problem with certain video formats needing converters with standard DirectShow filters (e.g. Y800, capturing to an Y800 avi file was not possible). Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.

• February 26, 2013 2.4.14.851

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.4.14.851	Released February 26, 2013	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog WHQL certification.

you are here: home > support > product notices

Thanks for the info, however, I had already tried everything. The apple device driver was never on my computer, however, I was able to install it after installing a program called 'Driver Update' for some reason when I downloaded the 'Apple mobile device driver' it did not install, but after downloading the driver update program, there was no problem and the file installed without a hitch. When an Ant8 is plugged into a Windows XP system the device manager comes up with Install software for 'USB Serial Port', which cannot be found in the ant8/driver sub-directory. Unplug the Ant8. Go to the control panel. Use add/remove programs to remove the FTDI VCP drivers. Disconnect from the internet.

This page has Product Notices applying to the Ant8 and Ant16 logicanalyzers.

PN0103.1 Ant8 and Windows XP

Ant8 units shipped before the middle of 01/03 use a genericProduct ID in their USB interface. This can cause problems when workingwith Windows XP.Units shipped after this date use a product-specific Product ID anddo not manifest the problem.The problem only applies to systems using Windows XP.

Symptoms

When an Ant8 is plugged into a Windows XP system the devicemanager comes up with Install software for 'USB Serial Port',which cannot be found in the ant8/driver sub-directory.

Rectification

1. Unplug the Ant8.
2. Go to the control panel. Use add/remove programs to removethe FTDI VCP drivers.
3. Disconnect from the internet. (XP can silently search the web fordrivers)
4. Plug the Ant8 back in.
5. Use the option Install from a Specific Location (Advanced)and browse to the location of the D2XX drivers on your system.

PN0403.1 Ant8 Input Pulldowns

Certain Ant8 units shipped between 2/03 and 4/03 may have incorrectpulldown resistors on the eight signal input circuits.

Symptoms

Weak driving circuits are unable to overcome the pulldowns.The user can easily check the values of the pulldowns as follows:

1. Unplug the Ant8.
2. Measure a pulldown resistance by measuring the resistance betweena red signal grabber and the black ground grabber.The measured value should be 100Kohm to 1Mohm.Repeat this measurement for all eight channels.

Rectification

Either replace the pulldowns with the correct values (100Kohm to 1Mohm)or remove the pulldown resistors. This is a job for a skilledtechnician and the small component sizes dictate the use of magnification.

Factory Rectification

If you believe your Ant8 has this problem, send an email describingthe problem and including the product serial number and approximatedate of purchase tosupport@rockylogic.com.

PN0403.2 Ant8 Input Circuit Frequency Response

Certain Ant8 units shipped between 12/02 and 4/03 may have incorrectbypass capacitors in the eight signal input circuits.

Symptoms

The Ant8 fails to respond accurately to slow signal edges (bothslow-rising and slow-falling). It also inaccurately measurespulses which are short in relation to the rising/falling times.

Rectification

The eight input bypass capacitors should be replaces by 220pFcapacitors (50V rated, 0402 size). This is a job for a skilledtechnician and the small component sizes dictate the use of magnification.

Factory Rectification

If you believe your Ant8 has this problem, send an email describingthe problem and including the product serial number and approximatedate of purchase tosupport@rockylogic.com.

PN0703.1 Ant16 Overheating

Some early Ant16 units, shipped in 6/03 or early 7/03, may havean incorrectly mounted tantalum capacitor.

Symptoms

The Ant16 works for a while, then fails to respond to the software.Typically the software then report the Ant16 as not present.

Rectification

The potentially reversed tantalum capacitor is on the PCB sidewhich does not have the LEDs. The cap should be mounted with thepolarity stripe towards the big flat pack - this can be checkedthrough the translucent plastic cover.The capacitor can be reversed by opening up the case(see Opening up),and unsoldering, reversing, resoldering the capacitor.Ideally the capacitor should be replaced with a new part(tantalum, case size A, approximately 3.3muF, 10V).

Factory Rectification

If you believe your Ant16 has this problem, send an email describingthe problem and including the product serial number and approximatedate of purchase tosupport@rockylogic.com.

PN0408.1 64-bit Vista Drivers

The 64-bit version of Windows Vista does not permit installationof the Ant drivers.

Rocky Logic Usb Devices Drivers

Symptoms

Windows refuses to install the Ant drivers because they are unsigned.

This only applies to users running the 64-bit version of Windows Vista,also known as the AMD64 version.It does not apply to 32-bit Windows Vista or to Windows XP.

Background

Every USB device is identified by a Vendor ID (VID) and a Product ID (PID).Our instruments use FTDI USB chips, and they use the FTDI VID, which is 0403.Standard FTDI chips have a PID of 6001; we reprogram the chips to ourown PID, which is F918.Since the FTDI chips are widely used in a variety of products, having ourown non-standard PID helps to avoid driver conflicts and to avoid the problemslisted in PN0103.1

We use standard FTDI binary drivers.However, the standard FTDI driver package is digitally signed to the 6001 PID,which does not match our F918 PID.Under Windows XP and Windows Vista 32, the effect of the non-match is a simple warningmessage when the drivers are installed.

Windows Vista 64 will not install a driver if the PID does not match thedriver digital signature.

Rectification

Change the PID back to the FTDI standard value of 6001.The driver digital signature will then match the PID and the driver will install.This is the procedure:

1. Plug the Ant into a Windows XP system.
2. Download and install the FTDI MPROG program:MProg3.0_Setup.exe.This program will reflash the PID.
3. Download and unzip the latest FTDI drivers:here.
4. Download the 6001 template for MPROG:rocky6001.eptYou may also wish to download the template for reverting the Ant to an F918 PID:rockyf918.ept
5. Run MPROG. Use File|Open to load the template, then Device|Program toreflash the Ant.
6. Exit MPROG. Unplug and replug the Ant to switch to the new PID.

The Ant will now report a standard FTDI VID/PID pair and the FTDI drivers will installon Vista 64.

Opening up an Ant8 or Ant16

Rockylogic USB Devices Driver

Opening up

Start where the plastic comes together round thecable. Carefully separate with a small screwdriver,then separate the rest of the casing.

Reassembling

Place the Ant8 or Ant16 in the plastic half whichdoes not have holes for the LEDs. Put the cable in place,taking care to position the small hole in thetranslucent cable gland over the small spike on the plastic.

Rocky Logic Usb Devices Driver Download

Rocky Logic Usb Devices Driver Update

Position the other half of the plastic enclosure sothat it also has its small spike engaged with ahole in the translucent cable gland. Bring the twoplastic halves together, starting with the locatingpegs nearest the cable and finishing with thelocating pegs nearest the clips connector.