AnsweredAssumed Answered

Help modifying definition file (to use FTDI device)

Question asked by jpittock on Mar 16, 2020
Latest reply on Mar 18, 2020 by jpittock

Like • Show 0 Likes0
Comment • 4

Hi,

I've been trying to import a definition (.h) and DLL file in order to use an FTDI device with VEE but unfortunately I've been getting an invalid expression error when I import the file:

I've tried modifying the header file in accordance with the Advanced Programmers guide, but it would appear my grasp of programming fundamentals isn't sufficient. I was unable to find an equivalent for 'BOOL' so substituted 'INT' for the data type as I read in one of the Keysight manuals that boolean is of type INT.

I'd be grateful if someone would be able to point out where I've gone wrong in editing the header file, and suggest what I need to change in order to get it to work. Attached is the original unedited file (ftd2xx_original.h) and my edited version (ftd2xx.h).

Any assistance greatly received (otherwise I might have to use Labview )

Thanks

Jon

Attachments

ftd2xx_original.h.zip8.0 KB
ftd2xx.h.zip7.9 KB

No one else has this question

Outcomes

Stan Bischof Mar 17, 2020 3:18 PM

I'd suggest boiling that header down to just the function definitions that you need. VEE only needs the function def's themselves, not all the rest of the stuff that a compiler wants. Check the application docs to see which functions will be needed and then grab just those pieces. Note that you can't have enums (as you found out) or structs in the final definitions.

Then after discarding all the rest you'll likely be more successful with the definitions that you need.

If you still strike out, and noone here in the forum helps, try VRF.

Stan

Actions

Stan Bischof @ Stan Bischof on Mar 17, 2020 6:09 PM

Hi Jon

I was curious so I poked around a little over at the Future Tech site (www.ftdichip.com/FTDrivers.htm) and found that they have two types of drivers: Virtual COM Port (VCP) drivers and direct (D2XX) drivers. While the direct drivers would be higher performance and more flexible, they work by importing a DLL. As you are finding out the hard part of this approach is getting the def file right.

HOWEVER YOU ARE IN LUCK- I'd suggest dropping the direct quest and go with the VCP driver since that's an option.

The VCP driver should create a COM port on your system that looks like any other COM port. VEE can natively talk to COM ports so after installing the driver you would just point VEE to the resulting COM port and use directIO as with any other COM port. No DLL import, no def file, likely no hassle. The underlying SPI interface is taken care of by the VCP driver so you don't have to deal with it.

At that point you're just down to the instrument commands.

Stan

Actions

jpittock @ Stan Bischof on Mar 18, 2020 12:43 AM

Hi Stan

Thanks ever so much for your feedback, and the comments to my other post on stripping out the headers.

Reading round I got the impression I *had* to use the D2xx drivers, but I will take a look at the VCP drivers to see if that makes things easier.

Much appreciated and stay well.

Jon

Actions

jpittock Mar 18, 2020 2:18 AM

Brief update. Using the VCP and sending a byte to the serial port using a direct I/O transaction I can see data coming out of the FTDI cable using an oscilloscope. Different problem now - data is appearing on the 'SCLK' pin and there is no SCLK on any of the other pins. I wonder if I have a duff device.

Anyway now in the realms of hardware. Thanks for your help. Will publish an update to what I find.

many thanks

Jon

Actions

4 Replies

Stan Bischof Mar 17, 2020 3:18 PM
Mark Correct
Correct Answer
I'd suggest boiling that header down to just the function definitions that you need. VEE only needs the function def's themselves, not all the rest of the stuff that a compiler wants. Check the application docs to see which functions will be needed and then grab just those pieces. Note that you can't have enums (as you found out) or structs in the final definitions.

Then after discarding all the rest you'll likely be more successful with the definitions that you need.

If you still strike out, and noone here in the forum helps, try VRF.

Stan
Like • Show 0 Likes0
Actions
- Stan Bischof @ Stan Bischof on Mar 17, 2020 6:09 PM
  Mark Correct
  Correct Answer
  Hi Jon
  
  I was curious so I poked around a little over at the Future Tech site (www.ftdichip.com/FTDrivers.htm) and found that they have two types of drivers: Virtual COM Port (VCP) drivers and direct (D2XX) drivers. While the direct drivers would be higher performance and more flexible, they work by importing a DLL. As you are finding out the hard part of this approach is getting the def file right.
  
  HOWEVER YOU ARE IN LUCK- I'd suggest dropping the direct quest and go with the VCP driver since that's an option.
  
  The VCP driver should create a COM port on your system that looks like any other COM port. VEE can natively talk to COM ports so after installing the driver you would just point VEE to the resulting COM port and use directIO as with any other COM port. No DLL import, no def file, likely no hassle. The underlying SPI interface is taken care of by the VCP driver so you don't have to deal with it.
  
  At that point you're just down to the instrument commands.
  
  Stan
  Like • Show 0 Likes0
  Actions
  - jpittock @ Stan Bischof on Mar 18, 2020 12:43 AM
    Mark Correct
    Correct Answer
    Hi Stan
    
    Thanks ever so much for your feedback, and the comments to my other post on stripping out the headers.
    Reading round I got the impression I *had* to use the D2xx drivers, but I will take a look at the VCP drivers to see if that makes things easier.
    
    Much appreciated and stay well.
    
    Jon
    Like • Show 0 Likes0
    Actions
jpittock Mar 18, 2020 2:18 AM
Mark Correct
Correct Answer
Brief update. Using the VCP and sending a byte to the serial port using a direct I/O transaction I can see data coming out of the FTDI cable using an oscilloscope. Different problem now - data is appearing on the 'SCLK' pin and there is no SCLK on any of the other pins. I wonder if I have a duff device.

Anyway now in the realms of hardware. Thanks for your help. Will publish an update to what I find.

many thanks

Jon
Like • Show 0 Likes0
Actions

Help modifying definition file (to use FTDI device)

Attachments

Outcomes

Related Content

Recommended Content