The FTDI driver enables Windows to assign the USB coordinator a “virtual COM port” when first inserted in your PC. You can verify this from the Windows Device Manager on your PC. You specify that COM port when you use the New Jennic Wireless Adapter tool to configure the USB coordinator.
Installing the FTDI driver
Look in the Windows Device Manager to see what Ports (COM & LPT) already exist.
Access the Device Manager quickly from the command prompt, or from the -> command by entering: devmgmt.msc
Expand the Ports node and note existing COMn
numbers.
Open the Sedona Framework distribution in Windows Explorer, and navigate to the FTDI
folder.
Open the FTDI subfolder that matches your OS, and double-click the executable file.
For example: CDM 2.08.02.exe
The FTDI install briefly opens a command prompt window, during which the driver is installed.
Verifying the FTDI driver
Insert the USB coordinator into an available USB 2.0 port.
You should see a “Hardware found” alert or similar message(s) in the system tray of your PC. The LED on the USB coordinator should be blinking about twice a second.
Look in the Windows Device Manager to see what new COM port was created. (Expand the Ports node and note the new COM
n
port.)
It should be listed similar to: USB Serial Port (COM7)
If you have the Sedona Framework Developer Board Kit, you also have a “USB to RS-232” serial cable that uses the FTDI driver.
In this case only (otherwise skip to Step 3):
Insert the “USB to RS-232” serial cable into another available USB 2.0 port.
Again, you should see a “Hardware found” alert or similar message(s) in the system tray of your PC.
Look again in the Windows Device Manager to see what new COM port was created.
It should be listed similar to: USB Serial Port (COM8)
Your COM port assignment(s) will likely differ. Make a note of these new COM port assignments—you will need to identify or use them in the related Jennic Serial Port Tool view in Workbench.
If the “Niagara AX Serial Tunneling” client application was previously installed on your PC, be aware of a possible COM port
conflict with the “virtual COM port” defined by that application. By default, installation of Niagara AX Serial Tunneling
creates a virtual port with COM6 assignment. You cannot see this port from the Windows Device Manager; however, it can be
seen as an unknown port from the Workbench view that manages Jennic serial port access.To prevent conflict with the FTDI devices
used with Workbench and the Sedona Framework, open up the “Niagara AX Serial Tunneling” applet in the Windows Control Panel,
and verify the “Serial Port” shown (top field) does not duplicate one of the COM ports created and shown in the Windows Device
Manager for the FTDI devices (USB coordinator, and if applicable, the “USB to RS-232” adapter cable). Select another unused
virtual COM port if it does. Otherwise, you will see a “port in use by Windows” error when attempting to use that port in
Workbench.If you do not see a “Niagara AX Serial Tunneling” applet in your Windows Control Panel, this does not apply to your
installation.
Copyright © 2000-2014 Tridium Inc. All rights reserved.