LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Omnic activeX

I am running a commercial spectrometry software called Omnic using a LabView program a wrote. The program uses activeX to communicate with Omnic, but I have run into a problem that has left everyone I have talked to stumped.

 

When I attempt to set a background file for my spectra collection, Omnic only receives 32 characters of the filepath. The same thing occurs whenever I try to set any other filepath in the program of longer than 32 characters. However, when I execute a command to save a file, Omnic understands this just fine and I can save the files to whatever location I choose. 

 

I know that Omnic was originally set up to run via DDE, and I was wondering if the fact that I am using activeX instead could have something to do with the problem. Has anyone else run into an issue like this or do you have any suggestions on how to solve the problem?

 

I have attached a simplified version of my program.

0 Kudos
Message 1 of 5
(3,695 Views)

Hi Realcomfy

 

Do you know if this limitation is also present if you run Omnic via DDE?

 

Because if that is the case the problem would not be with LabVIEW or activex but whit Omnic.

 

Regards

Esteban R.

0 Kudos
Message 2 of 5
(3,655 Views)

If it works, is it a problem?

 

It's not an issue of an older activeX object not handling spaces in path, or built for old dos-names of 8.3 lengths?

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 3 of 5
(3,647 Views)

Omnic has it's own DDE program and the command works fine when sent that way. I haven't yet wrote program to test DDE via LabView because I would like to stick with activeX since everything else is run with these commands. The DDE just adds an additional, hopefully unneccessary level of complexity.

0 Kudos
Message 4 of 5
(3,640 Views)

Yamaeda, 

 

I guess I wasn't sufficiently clear. The activeX command doesn't work when I SET a file path, instead tuncating the string at 32 characters. Other parameters that use long string can be set via the EXECUTE command, but unfortunately this isn't an option for the particular filepath I am trying to set.

 

I have also ensured that there are no spaces in the filepath, and the program definitely accepts filepaths of longer than 32 characters if set manually. 

 

Thanks for the help so far. 

0 Kudos
Message 5 of 5
(3,639 Views)