Author Topic: Keysight IO libraries and Borland C++  (Read 1244 times)

0 Members and 1 Guest are viewing this topic.

Offline DrirrTopic starter

  • Regular Contributor
  • *
  • Posts: 72
Keysight IO libraries and Borland C++
« on: April 03, 2021, 07:13:15 am »
Hi guys,
I am trying to create simple logging C++ app for communication with HP 34401A via GPIB. I installed "Keysight connection expert" and Keysight IO. I am able to find all my instruments using USB/GPIB

I tried to use Borland 5.5, linked all visa libraries, include and executable files.

My problem is that Iam not able to build any of code examples. Is there abything Iam doing wrong? Most of keysight links to useful information shows "404 no longer available"

May I ask you for  any simple code example of communication with HP 34401A or any similar tool via GPIB and Keysight connection expert + and Keysight IO?


--------------------Configuration: bcc5.5 - CUI Debug, Builder Type: Borland C++ Compiler--------------------

Checking file dependency...
Linking...
Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland
Error: Unresolved external 'viOpenDefaultRM' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viOpen' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viGetAttribute' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viSetAttribute' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external '_viPrintf' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external '_viScanf' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viClose' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ

Complete Make GettingStarted: 7 error(s), 0 warning(s)


 
 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Keysight IO libraries and Borland C++
« Reply #1 on: April 03, 2021, 07:42:41 am »
Bcc5.5 is nice tool for small DIY projects. If you want to use (modern) 3rd party libraries, compiler of previous century is not the best choice. Try Visual Studio https://visualstudio.microsoft.com/free-developer-offers/
 

Offline PKTKS

  • Super Contributor
  • ***
  • Posts: 1766
  • Country: br
Re: Keysight IO libraries and Borland C++
« Reply #2 on: April 03, 2021, 11:08:48 am »
Hi guys,
I am trying to create simple logging C++ app for communication with HP 34401A via GPIB. I installed "Keysight connection expert" and Keysight IO. I am able to find all my instruments using USB/GPIB

I tried to use Borland 5.5, linked all visa libraries, include and executable files.

My problem is that Iam not able to build any of code examples. Is there abything Iam doing wrong? Most of keysight links to useful information shows "404 no longer available"

May I ask you for  any simple code example of communication with HP 34401A or any similar tool via GPIB and Keysight connection expert + and Keysight IO?


--------------------Configuration: bcc5.5 - CUI Debug, Builder Type: Borland C++ Compiler--------------------

Checking file dependency...
Linking...
Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland
Error: Unresolved external 'viOpenDefaultRM' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viOpen' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viGetAttribute' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viSetAttribute' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external '_viPrintf' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external '_viScanf' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ
Error: Unresolved external 'viClose' referenced from C:\USERS\DAVID\DOCUMENTS\CPP_PROJECTS\GETTINGSTARTED.OBJ

Complete Make GettingStarted: 7 error(s), 0 warning(s)


It looks like you a have a very simple error of unresolved references
just because the *REQUIRED*  link libraries are not found on the path...

Just add the *REQUIRED* LIBS WHERE THESE CALLS ARE to the
path as in figure..  no matter if using console or GUI.. same thing..

BTW... the  OP has a very good point using Borland or WATCOM..

Any folk experienced with 16bit or early 32bit program know how
hard MS pushed to IMPLODE and extinguish both Borland and WATCOM.

Reason being as always is that MS products were never competitive
Borland has a far superior  widget set and LIBC implementation
and WATCOM is just the FASTEST numerical compiler for 16 and 32 bit aps
of these  CPUs.

So as usual MS IMPLODED them all (ala MFC) and banned almost
all competition... including DELPHI years later just because otherwise
it would have just detonated VB...

so from 2000 on MS achieved a vertical stack control even being a poor
bad crappy compiler set and tools..   AKA VisualShitStudio

Same they did on LOTUS late 80s including EXCEL on WORD as "OFFICE"

WHO in hell would buy a second expensive spreadsheet ?

So doomed LOTUS and years later same they did QuattroPro..

Decades of the technology they master - IMPLODE  better competitors..

IMHO?  Yes keep Borland or  WATCOM and ditch that shit MFC and MSStudio

Results are just order of mag. better.

From  2000s on GCC and MingW or CYGWIN are just the safer choice
Paul
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf