Q: What is the difference between the WF 2007 and the WF 2008 dongles?
The WF 2008 are for targets running “standard” LabVIEW, i.e. LabVIEW for Windows, Mac and Linux.
Q: What items do I need to purchase and/or download to use the WireFlow dongles for protecting my LabVIEW application from being duplicated?
1. Download the WF Security dongle software package (Article no AE0011) from www.wireflow.se/download
a. LabVIEW Dongle Drivers.vipc. It provides VI’s that you shall embed in your application. (This software is free)
b. WF-DongleDeviceDriver. Install this on the Windows target PC’s if you use
WF 2008 dongles. (This software is free)
c. WF Security Suite Programming Application. Use this application to program your secret keys into the dongles.
(You need to buy a license to activate this application)
2. Buy a license for the WF Security Suite Programming Application
(Article no AE009) from WireFlow. You need one such license.
3. Buy some WF 2008 (Windows) or WF 2007 (RT), USB Security dongles from WireFlow. You will need one dongle for each system you want to deploy.
4. Read the document AC0045-003 WF Security Suite – Quick Guide. It gives
a short step by step instruction for how to create your security solution.
C Series modules
Q: Are the WireFlow C Series module usable in cDAQ-Systems from National Instrument.
Q: How is the WF 3144 Resistor Emulator Module designed?
Q: What kind of connector are used for the WF C Series modules?
A: The WF 3144 and WF 3154 modules uses a 10-Pos Plug. You should connect a Terminal Block for 10-Pos Plug to the module. This Terminal block is included together with the module when shipped from WireFlow.
The WF 3132 uses a standard 37-pin Dsub connector – type Plug. You should connect a 37-pin Dsub connector – type Receptacle to the module. This Receptacle is NOT included with the module when shipped from WireFlow.
Q: Why is the error code -64998 reported when I try to compile FPGA code for the NI 9144 Ethernet chassis when I use WireFlow C Series modules?
The plan is to fix this problem in the next release of EtherCAT (2.7). This is planned to be released in early 2014.
Until then there exist a work-around for the issue that is relatively simple:
- Copy the file resource.xml and overwrite the existing one in \Targets\NI\FPGA\ECat\NI 9144
- Exit LabVIEW and navigate to \Targets\NI\FPGA\bin
- Run lvfpga_make_resource_cache.exe