![]() If your User Access Control Service (UAC) is enabled then you will have to accept of the driver and run the setup with administrative rights. Run the driver setup file from a Windows account with administrative rights.This is the download link for the driver version 3.0.2.664 released on. Download the driver setup file for Native Instruments Traktor Kontrol F1 DFU driver from the link below.Native Instruments Traktor Kontrol F1 DFU - install the driver manually Traktor Kontrol F1 DFU is a USB Universal Serial Bus device. This driver was developed by Native Instruments. In order to make sure you are downloading the exact right driver the hardware id is usb/vid_17cc&pid_1122.ġ. In the next post in this series, I’ll describe how to write Arduino sketches to translate between MIDI and F1 HID Report data.Native Instruments Traktor Kontrol F1 DFU driver download and installation The key thing to understand here is that those 22 bytes will be sent by an Arduino sketch! When 22 bytes are received (the size of the F1 HID Report), the loop then writes it to the USB port as an HID Report. This loop uses the LUFA Library serial library at lufa/LUFA/Drivers/Peripheral/Serial.h to receive data from the Atmega16U2’s serial port (which is connected to the serial output of the ATmega328 on the Uno. If (USB_DeviceState != DEVICE_STATE_Configured)Įndpoint_Write_Stream_LE(&ReportData, sizeof(ReportData), NULL) once ReportData is full, send it out the USB port to the computer ![]() receive 22 bytes from the serial port (this will be from the sketch) The key part from SerialToF1.c is here: int main(void) The final set of files, SerialToF1.h and SerialToF1.c, contain the code that converts the data from the Arduino sketch into an F1 HID report. ![]() The DFU endpoints (for upgrading the firmware in a real F1) may not be necessary either, but I included them when prototyping.A real serial number was not necessary (I used “00000000”).If you compare the versions of these files with those in the LUFA example, the changes and additions are fairly self-explanatory. Essentially, you want the Arduino descriptors to match the USB dump found here in “Native Instruments F1 Controller Descriptor Dump.html”. The chances in descriptors.c and descriptors.h are much more extensive, but essentially this the part that makes the Arduino appear to be an F1. In Config/LUFAConfig.h I also changed the endpoint size to be the smallest size of the available options – 8, 16, 32, 64 – that is greater than the report size. Next I edited Config/AppConfig.h to reflect the side of the F1 HID report: #define F1_REPORT_SIZE 22 SRC = $(TARGET).c Descriptors.c $(LUFA_SRC_USB) $(LUFA_SRC_USBCLASS)ĬC_FLAGS = -DUSE_LUFA_CONFIG_HEADER -IConfig/ I started by editing the makefile to reflect the target board and the location of the LUFA Library: MCU = atmega16u2 The LUFA Library includes a number of examples (including makefiles) designed to programme Atmel AVRs to emulate a wide variety of of USB devices. In our case, the F1 is a custom HID device, so I chose the GenericHID Class Driver example as the template- in the lufa distribution it can be found at lufa/Demos/Device/ClassDriver/GenericHID. Our starting point was the excellent LUFA Library (Lightweight USB Framework for AVRs) by Dean Camera. Now we get to the juicy bits – the actual firmware that will make the Arduino Uno appear to your computer (and to Traktor) to be a Native Instruments Traktor Kontrol F1. ![]() In Part 2 of this series I described how to setup the hardware and software environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |