Aardvark Driver Download



Versatility for Emulation, Prototyping, and Programming. Latest download for Total Phase Aardvark I2C/SPI Host Adapter driver. Total Phase is committed to improving the Aardvark adapter and making these improvements available to our customers. Select the driver needed and press download.

Support for the Paylink Money Handling System is provided in these pages. From here you can access the latest Downloads, Frequently Asked Questions, or alternatively you can try our Support Forum.

  1. Distribution: Download The Aardvark LabVIEW Driver is a free and open-source LabVIEW Instrument Driver for the Aardvark I2C/SPI Host Adapter. This version supports LabVIEW 2017 and above. If you do not see the version/device driver you require, please submit a support request.
  2. Aardvark drivers are installed but Code 39 occurs Review by Cristina D. Rating Hey, i installed the Aardvark device on Windows 10 using drivers v2.16, but the Device Manager shows this device status: 'Windows cannot load the device driver for this hardware.

If you have a problem, please take the time out to look at our FAQ section here.

Advice on the purchase of suitable money handling peripherals and support for problems of a purely hardware nature, is provided by our manufacturing / marketing partner, Crane PI. You can contact their sales department with an enquiry from this page

Aardvark

If you have a problem of detailed software nature then the support forum might contain someone else’s similar experience. If you’re problem is a new one, then the best way to tell us about it is to create a new thread in that forum. In that way, you will benefit from the advice of other users. There is no quicker way to contact our support staff, but if your problem is of a confidential nature, you can contact them at support@aardvark.eu.com.
If the Paylink System fails to work with the software you have written, please take the time out to run the demo programs provided as part of the SDK. These are used by Aardvark staff to test the product during development.

If the failure is evident with these demo programs, then we will find it much easier to troubleshoot your problem. If the failure is not evident, then that will indicate that you are using the interface in a different way, and we will probably want to ask some quite detailed questions.

Development Platform
Although the Paylink System is fully supported on any Linux distribution, as well as Windows on a PC, the Aardvark Development team use Windows PCs to work on the Paylink software. This means that the distribution and debugging tools are slightly biased to this environment.

If you have access to a Windows PC, then we recommend that you use the released SDK (see below). If you only have access to a Linux based system, you will still be able to use the Paylink System without any problems by downloading the Linux release files below.

Product Updating
Normally the entire interaction with the external hardware is handled by firmware running on the Milan Interface unit. The software on your computer only requires updating if you are intending to use a new facility not supported by the version you have installed, or you are using USB connected peripherals. (This will be obvious because your application will refuse either to link or to load!)

There are some PC utilities to aid in fault finding. Copies of these form a part of the SDK on the Paylink Installer (see below) and some are available below.

These links will enable you to obtain the latest fully supported versions. Although some of the software downloads consist of a single executable, they are all saved as zip files, as the default (run) operation of the executable is unlikely to be useful!

The main release of the SDK is now as a standard Microsoft Installation file (.MSI) for Windows. If you download that and run it, it will extract the SDK into your specified folders, install the USB drivers and interface DLLs into the correct locations and if you wish run a WalkThrough program that will check that your system is ready to run Paylink Applications.

For most of the other technical files you can just extract the executables from the zip into a handy folder and run them. The upgrades for the Milan Interface unit firmware are distributed as a part of a program, or executable script, which will update the firmware on an installed unit when run. The PC version of this program has a number of features, which are described in full in the Utilities document.

Due to code space limitations on the Milan Interface unit, there are now Four different firmware loads for the Paylink system software. The firmware load that you will need for a given set of peripherals is detailed in the System Manual (on page 31.)

The Linux distributions are as tar.gz files, which can be unpacked and installed on a Linux system. Full details on this process are given in the Linux User Guide.

Aardvark Driver Download Pc

Software
Firmware Load 1 - Standard (All CPI peripherals)
Firmware Load 2 - InnEbd
Firmware Load 3 - Innov (All Innovative Peripherals)
Firmware Load 4 - MCD
Complete SDK (PC Windows Installation File)
Complete Linux Installation (Source Files)
Linux USB Peripheral Support. (To be used with above.)
Linux Firmware Update Package. (To be used with above.)
Coin / note table update (for MCL equipment) SDK
Documentation
Paylink System Description Manual
Full Programmers Reference
Linux Programmers Guide
Guide to the Dot Net Facilities
Guide to the Java Facilities
Coin / note table update (for MCL equipment) Reference
Extract of MCL Technical Manual
Release Descriptions
Milan 1.12.12 Release Note
Milan 1.12.11 Release Note
Milan 1.12.10 Release Note
Milan 1.12.9 Release Note
Milan 1.12.81 Release Note
Milan 1.12.72 Release Note
Milan 1.12.4 Release Note
Milan 1.11.8 Release Note

Other Downloads
In addition to the above downloads, you can also visit our complete download page here to obtain testing (Beta) versions of the utilities and firmware, and older versions versions of the firmware.

Frequently Asked Questions(FAQ)
The following list of common problems and their answers has been mainly extracted from our support forum, so please visit that if you can't find your problem here.

Frequently Asked Questions.
1
Q. What operating systems with the Milan / Paylink Interface run under?
The full package will install and run on all Windows or Linux Systems. If you are using Windows and wish to use C# (Dot Net), then class libraries and examples for Dot Net 4.0 and above are provided, ready to use, as a part of the standard installation.
We also provide full support for the standard Milan Interface unit (connected to Linux kernels 2.6 and later) which, as it is in source, can be installed on ARM processors such as the Raspberry Pi with no problem.
For USB connected peripherals, we support all Intel / PC Linux Distros. If you are planning on using USB perihperals from an ARM based (e.g. Raspberry Pi) system then please contact us for more details.
Q. What platform is required to run the Paylink System?
A. The standard Paylink System using the Milan Interface requires very few resources and will run on any Platform provided it has at least one USB port.
Q. What peripheral equipment does the Milan Interface part of the Paylink System support?
A. Please see the Technical Description page.
Q. When I run the driver program it does nothing but display the message:
Config: No 'Peripheral Name'
This is caused by your configuration file specifying 'peripheral name' and this is not supported by the loaded firmware. See page 31 in the System Manual for details on which peripheral is supported by which firmware load.
Q. Your money fields report in values in lowest denomination. What happens when I change to an acceptor that accepts smaller coins?
A. The lowest denomination we refer to, is that of the given currency (i.e. one penny, one cent) and is fixed for a given currency.
Q. I’ve connected up 12V and a cctalk coin acceptor and hopper, why doesn’t the interface report any peripherals? or
What does the diagnostic message
'cctalk: Data line frozen'
mean?
A. Although the Milan Interface unit cctalk connector includes 12v and 24v, only the 12v is fed through from the 2 pin JST connecter, the 24v is a 'pass through' from an external. power supply. If you haven’t provided a 24v supply, then the hopper will “freeze” the cctalk bus (short it to ground) a fault which Paylink firmware can recognise. If you remove the hopper, the acceptor should be found and the diagnostic stop.
.
Q. I want to use the coin routing facilities of my coin acceptor to feed the hopper until it is full, and divert coins to the cash box afterwards.
A. There are comprehensive facilities to enable you to easily achieve this. Although easy to implement, they are slightly difficult to understand; so please refer to the section entitled “Coin Routing” in the System Description Manual, which gives full details. If you are still confused, then the support forum has topics on this subject.
Q. My system stopped working and the driver / diagnostics reported error 4, and then error 2.
A. The electrical environment that the Milan Interface operates in is noisy and can cause noise on the USB line. We recomend using USB leads with ferrite noise reduction cores. Later model Paylink units are much less susceptible to this problem.
Q. I don’t want the equipment to accept money from my customer until I am ready. How do I arrange for this to happen?
A. When the Milan Interface powers up, it inhibits all the peripherals, in which state they will automatically reject any money. At this point you can call OpenInterface, Current Value, ReadAcceptorDetails and ReadDispenserDetails to find out where you’re starting from. You can pre-set individual inhibits (see next question) and then you call EnableInterface. EnableInterface is how you announce to the Milan / Paylink Interface that you're ready to go, until you call EnableInterface everything is disabled / inhibited, regardless of the AcceptorBlock setting. After you call it, they will correspond to the settings you have made. (They are all enabled by default.).
Q. How do I control which acceptors, coins and hoppers will be working at any given time?
A. You use ReadAcceptorDetails / WriteAcceptorDetails and ReadDispensorDetails / WriteDispenserDetails. These use interface blocks that are described in the Application Interface Manual. Specifically:
  • To inhibit / enable an acceptor set / clear the ACCEPTOR_INHIBIT bit in the AcceptorBlock.Status field and then write the details back
  • To inhibit / enable a specific coin, set / clear the Acceptor.Coin[CoinNumber].Inhibit field (to 1 / 0), and then write the details back.
  • To inhibit / enable a dispenser set / clear the DispenserBlock.Inhibit field (to 1 / 0) and then write the details back.
In all cases you find the correct block by performing a check along the lines of:
(xxxxBlock.Unit & DP_GENERIC_MASK)
DP_COIN_ACCEPT_DEVICE
or DP_NOTE_ACCEPT_DEVICE or DP_COIN_PAYOUT_DEVICE

The reception of bytes by the Aardvark slave, when it is configured as an I 2 C slave, is asynchronous with respect to the PC host software. However, logging to stdout and stderr is still supported. The Aardvark adapter is USB 1. Serial Clock — control line that is driven by the master and regulates the flow of the data bits. Two pins are connected to provide a solid ground path. This will require the ability to reconfigure the offending master device. Note that the last few bytes of the response may be corrupted as well.

Uploader:Sazragore
Date Added:24 March 2014
File Size:5.11 Mb
Operating Systems:Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:39150
Price:Free* [*Free Regsitration Required]

Hence any pending data in the operating systems incoming buffer will not be reported to the user usn the Aardvarks software queues have been fully serviced. This feature allows the Aardvark adapter, following a transaction as a master SPI device, aardvarrk be then reconnected to another SPI environment as a slave. The best throughput can be achieved for single transactions that transfer a large number of bytes at a time.

One can employ the following technique to guarantee that all pending asynchronous data have been captured during each service cycle: To confirm that the device was correctly installed, check that the device appears in the “Device Manager. As of version 5.

Total Phase and distributors have no obligation to provide maintenance, support, or updates. The Aardvark OEM adapters have a subset of these features.

Software Downloads – Total Phase

Write a stream of bytes to the I 2 C slave device with extended status information. The sequence of events are as follows:. SPI is a very simple communication protocol. The lines are effectively pulled up to 3.

Aardavrk there is no data already available, this function will check the operating systems receive buffer for the presence of asynchronous data. The data frame is described by two parameters: As an example, the integration for the C language bindings is described below. For hardware versions before 3. This is a constraint found with most I 2 C master devices used in a multi-master environment.

Control Center Serial Software

Zero bytes were requested from a slave. This is most likely a result of a communication error.

Life support devices or systems include, but are not limited to, surgical implants, medical systems, and other safety-critical systems in which failure of a Total Phase product could cause personal injury or loss of life. The Aardvark DLL is designed for single-threaded environments so as aadrvark allow for maximum cross-platform compatibility. Otherwise there will be a memory access violation in the program. While provided language bindings stubs are fully functional, it is possible to modify the code found within this file according to specific requirements imposed by the application designer.

USB Drivers – Windows

Aardvark Driver Download Free

Write a stream of bytes to the I 2 C slave device followed by a read from the same slave device. The messages will be held until the appropriate API function is called.

As such, if the SPI master sends a subsequent transaction in rapid succession to the Aardvark slave, the data received by the Aardvark slave may be corrupted. USB Drivers – Linux. The log stores information about the type of transaction, features used, and the message sent. Create, run, and save aardvrk batch scripts to automate tasks. A line’s bit position in the mask will be 0 if it is configured as an output or if it corresponds to a subsystem aardvaek is still active.

Serial Data line — the signal used to transfer data between the transmitter and the receiver.

The master should then release the bus. This can be inefficient in simple configurations and a direct-link interface such as SPI might be preferred. Only a link to the Total Phase download area can be provided on such public websites. If all of these versions are synchronized and there are still problems, please contact Total Phase support for assistance.

Aardvark Usb Driver

Last Drivers