Francois Normandin

QUOTE (ASTDan @ Feb 23 2009, 05:06 PM) It did on my system, but if you change the font size and add a roman letter to the same text strip (say phi + f), you'll mess it up (XP, 8.6) and get something similar to pdc's odd characters. If you don't need to change it programmatically, I would suggest you use a picture of Phi instead of string... I've fought with them in LV7 and gave up.

QUOTE (menghuihantang @ Feb 12 2009, 04:00 PM) You might need to call other functions to fill in some data in memory first and then call your DeskWinReset function with the pointers to those values. ComPort, TC and Mode are not data by themselves. Pointer being a reference to an existing data in memory, if DeskWinReset expects to find a certain data structure at pointer value ComPort but what it finds is random 0's and 1's, then you will most probably get an unexpected result. For example, on Windows systems, there is a call to retreive the last error code. There is an other function to generate in memory a string for this error code. The output of this second function is a pointer that needs to be passed to a third function to display the message. You don't give the whole message as input for this last function, just the pointer to the string in memory. If the memory block is not initialized, you'll get an error. I think you should check what's the structure of data at ComPort's pointer location. Is it a pointer to a string, a boolean, an integer, a cluster structure? Some functions can be tested by inputing null values instead of actual pointer values. A null is generally represented by "0" for integers (not always). Have you tried 0's? Do you get the same 205 return value? EDIT: I see you input I32's. Does it work with U8? (It probably makes no difference, but Byte is U8...)

QUOTE (Vende @ Feb 12 2009, 10:31 AM) In my experience, I always saw the pixelink cameras in MAX, I just needed to change drivers. Have you installed IMAQ? I'm not sure you can see the cameras in MAX without IMAQ installed.

QUOTE (Vende @ Feb 12 2009, 09:21 AM) In MAX, you have to change drivers. Pixelink cameras automatically install with the factory drivers and MAX doesn't recognize it. Change the settings in MAX and you'll be able to detect it.

I would suggest you take a look at the L298HN chip. It's cheap and it's a dual H-Bridge configuration. You can control a stepper motor (4,6 or 8 wires) with 2 DO (A and B) or 4 DO (A, /A, B, /B) for full-step and half-step modes. There are examples on the web on how to do this. (I don't have time to give you a link, but just google it. )

QUOTE (Vende @ Feb 12 2009, 04:47 AM) It's a firewire camera, isn't it? You can use IMAQdx. It's all LabVIEW, but I wouldn't call it "free"...

QUOTE (menghuihantang @ Feb 11 2009, 03:26 PM) Ragglefrock is dead on: it is a 8-bit unsigned integer. See this http://msdn.microsoft.com/en-us/library/system.byte.aspx' rel='nofollow' target="_blank">link.

Hi Jim, you can download the driver from NI's site. Your problem is likely a configuration issue. I have no personal experience with this equipment. good luck. PS: May I suggest you start a new thread if you want help with programming for a network analyzer?

QUOTE (Vende @ Feb 10 2009, 12:47 PM) You can buy it. It's not free. I got it from Edmund Optics.

QUOTE (Vende @ Feb 10 2009, 09:56 AM) Pixelink SDK contains LabVIEW drivers. The learning curve is steep if you want to customize but once you get it, I found it efficient. (I used it with A742) The driver comes with a grabber program that you can use almost out of the box.

I ran into the same problem this morning and I investigated the "Get Last Event" Method for the image control. I need to poll repeatedly to get the last event fired (but at 25Hz I don't think I'll have a problem for user clicking too fast!). I monitor the "Draw Event". The method returns the tool used (rectangle, circle, etc.) and the coordinates. If you don't use it to actually allow the user to DRAW something, then I think it could work for you.

QUOTE (rom76 @ Feb 10 2009, 09:33 AM) I'd simply build a cluster with two elements: time stamp and message string. Your VIs could always communicate with this structure where the time would be filled in by the VI that sends the message. The receiver would thus know when the message was sent. Then, what you do with this information (display, log to file, ...) is application specific.

QUOTE (Vende @ Feb 5 2009, 09:50 AM) On your IMAQ Create VI, you've selected Image Type = Grayscale (SGL). Change it to Grayscale (U8) or RGB (U32).

Your front panel is set to lock until an event as finished. Uncheck the box at the bottom of your Event edition page. This is a useful feature when you want to prevent the user to perform any tasks while one completes, but in your case it's the reason why your panel is locked. But I agree with Mark that you should rethink your program to have only one event case. I'd suggest three loops: 1- Event case for UI, 2- Camera and 3 - Motor. This way you can act on your motor and camera via Queues or any other means of communicating between loops that you see fit. Your UI event case would thus be perfectly fit to be locked while you react to a user command, and your motor/camera will be separated.

QUOTE (bmoyer @ Feb 4 2009, 08:00 AM) That was my hunch as well and I did see the buffer number was not rising as fast as the loop rate. Although this implementation demonstrates that it's not limited by speed, either writing to disk or data processing. Many cameras can't deliver 30fps at full resolution (1280 x 1024 for example). The next question I'd ask myself is: What's the camera's model? Can it run at 15fps at full ROI?

QUOTE (jim85 @ Feb 4 2009, 05:06 AM) Your profile says 8.6. You should change that. I assumed you could open it. It's a simple query using "visa". Change COM1 to whatever GPIB address your equipment is at. http://lavag.org/old_files/monthly_02_2009/post-10515-1233754156.png' target="_blank">

QUOTE (pwu.380 @ Feb 3 2009, 04:12 PM) I don't have a real intelligent answer for you, as I haven't really asked myself the question. But the help file says this: Immediate? determines if the system returns the image currently being acquired or the last completely acquired image. The default value if FALSE, which causes NI-IMAQ to wait until the current image is completely acquired before returning the image. TRUE returns the next acquired image That explains why it's faster, but not why it's five times faster... I would have guessed that the maximum delay between true and false would have been the duration of one frame, hence I would have expected at most a two-fold increase in speed. Since it's much faster, there must be other considerations. Perhaps someone else has a better description of what it actually does...

QUOTE (pwu.380 @ Feb 3 2009, 02:28 PM) I got to write to disk at maximum speed of my camera (26fps) with your code with only a small change: Wire a TRUE constant to the IMAQ Grab Acquire.vi's IMMEDIATE? input. It's false by default. http://lavag.org/old_files/monthly_02_2009/post-10515-1233692772.png' target="_blank">

Can you post your code?

QUOTE (Nikunj @ Feb 3 2009, 09:28 AM) Hi Nikunj, for default conditions at start of VI, you can either make values default (simplest, but likely not ideal for hardware) or you could save your conditions in an initialization file and load them before any other tasks performed by your program.

QUOTE (Maca @ Jan 30 2009, 08:56 PM) Actually, a .mat file is a binary file for data. .m files are scripts. .mex files are the ones, from what I understand, that emulate VIs.

I've answered this in a subsequent thread, but it should appear in this thread as well. [cross-post] Calling LabVIEW VIs from Matlab

QUOTE (jojo_lapin @ Jan 30 2009, 07:40 PM) Hey there Jojo, Have a look at this link on the dark-side. There's a Matlab toolkit for calling LabVIEW VIs, including a way to convert VIs to MEX files as you previously asked here.

QUOTE (Paul_at_Lowell @ Jan 30 2009, 01:21 PM) Agreed.

QUOTE (Paul_at_Lowell @ Jan 30 2009, 11:25 AM) You do have a typedef with LVOOP, they're just embedded in the lvclass library and created for you automatically.