回复： Photometrics/Roper Scientific

[kehander]

When you imported pvcam32.dll, did you create a temporary .h file from pvcam.h and master.h, like I described in my previous post?  Otherwise, your Call Library Function Nodes might not be passing the pointers properly.

You should find out if those other previously-mentioned drivers ( http://code.google.com/p/pvcamlabviewdriver/ ) are available rather than trying to make something from scratch - evidently it is difficult even for people with much more experience with LabVIEW to get things to work that way.

Message Edited by kehander on 12-03-2008 10:59 AM

[B_Kiddo]

Dear mzu and kehander, thanx for your answers.

C0_CAM_NAME_OUT_OF_RNG error code gives pl_cam_get_name function - without it working I can not proceed. pl_cam_get_total does not work as well. 

We run already our camera, but we used mathlab. The C file was already created with the PVCAM functions and with the additional functions that the mathlab can understand. It worked and we are currently using it. Hence, RSConfig and the drivers are alright.

To kehander. I did exactly as you described above -I created a temporary .h file from pvcam.h and master.h

I am wondering if I do not have a problem with the pointers in Labview and if it is not better to create the C file modified for the Labview and to compile it -to create dll's other way round. What you may suggest me?

Best Regards 

[B_Kiddo]

Another point, kehander, that above you mentioned about #define PARAM_PREMASK ((CLASS2<<16) + TYPE_UNS16<<24) + 53) in the header file

I have char_ptr variable in my function. In the header file I found 

#define PARAM_DD_INFO               ((CLASS0<<16) + (TYPE_CHAR_PTR<<24) + 5)

PARAM_DD_INFO "returns the information message for each device".  What does it mean exactly ((CLASS0<<16) + (TYPE_CHAR_PTR<<24) + 5)? May be that is my problem...

Unfortunately, the absence of the programmimg knowledge does not help...

Greetings 

[kehander]

As described in that earlier post, you'll need to find the corresponding integer values for CLASS0 and TYPE_CHAR_PTR in the .h file and use the Bitwise Shift operator.   In any case, you won't be able to use any functions that can access parameters like PARAM_DD_INFO if you can't get pl_cam_open to run first!

Upon consullting the example code in the PVCAM documentation ( http://www.roperscientific.com/manuals/pvcam26_57-062-00.pdf ), I seem to recall that you need to run pl_pvcam_init before you cam run pl_cam_get_name .

[B_Kiddo]

"As described in that earlier post, you'll need to find the corresponding integer values for CLASS0 and TYPE_CHAR_PTR in the .h file and use the Bitwise Shift operator.   In any case, you won't be able to use any functions that can access parameters like PARAM_DD_INFO if you can't get pl_cam_open to run first!" - I already understood that

"Upon consullting the example code in the PVCAM documentation ( http://www.roperscientific.com/manuals/pvcam26_57-062-00.pdf ), I seem to recall that you need to run pl_pvcam_init before you cam run pl_cam_get_name"

 I know that as well.  pl_pvcam_init  runs fine -library is initialized withot any problems. Problems still only with the pl_cam_get_name. For now I did now found out why...

[ronke]

Scientific Imaging ToolKit

http://rcubedsw.com/download/Setup_SITKLV_30100_Advanced.exe

[kehander]

Are you sure that link is supposed to be public knowledge?  (Seems like awfully lax security for a package that's normally supposed to cost thousands of dollars.  Or maybe I've been mistaken about that all this time..?)

[ronke]

this is only a demo software,if you want to use it need to order and get a lic file from Rcub.

[wowden]

Hello,

I am currently programming a Roper CCD with labview using ActiveX to control winspec. The company I work for has the SITK, but when i open example VI's they are missing most, if not all of the sub VI's. Is this normal? Is the user suppose to write and implement the sub vi's themselves? Does anyone have any experience controlling Winspec with activeX?

Thanks,

William

[ronke]

Our lab also plan to build OMA test system,perhaps the attached file can help you.