Khalid

LV Punk said it very well about Alfa's posts:

Found this nice utility on NI's website which checks if a DLL is kosher for RT: http://digital.ni.com/public.nsf/allkb/0BF...6256EDB00015230 Regards, -Khalid

Here's a workaround in the interim: Scrolling horizontally with the mouse wheel works when it's rolled over the horizontal scroll bar. -Khalid

So, did you get the job? That should keep you "occupied." -Khalid

Hmm.. maybe because they like Canada and like to show it? (unlike some who stay there -- sometimes doing nothing and living off welfare -- and still b*tch about Canada) -Khalid PS: Or, they might just be having a bad hair day?

Here's something that might help you... Sorry, didn't see any non-dummies version... -Khalid

Couple of things: 1. I don't see your DLL function return anything. 2. How are you calling the funciton in LabVIEW -- what are the arguments you're passing, etc.? -Khalid

Maybe they mistook them to be you?? Canada's been great.. can't wait for my next $400 prosperity cheque -Khalid

Personally, I rather be happily-employed... especially, if you are assuming people like you as being intelligent.

Hi Michael, This is an excellent idea, and a great first-jab at it. I was wondering if you (or anybody else) had a chance to work on this more. I would like to make some modifications and wanted to start-off with the latest version. Thank you, -Khalid

I downloaded this LVDEBUG utility. It's an interesting way to monitor data in real time. I was however wondering what was the original intent of this utility as far as the DEBUG versus RELEASE builds go. I am guessing we don't want the data to get queued-up in the RELEASE mode; but to keep the VIs from breaking, we replace them with their RELEASE versions. Am I right here? If so, then the DEBUG_TX_R.LLB should only have dummy VIs; but it appears to have the same exact VIs as the DEBUG mode i.e., the Queues, etc. So, even in the RELEASE mode we are queuing up the info' (-- but just not displaying it since the DEBUG_RX_R.LLB only has a dummy VI). Shouldn't we also have dummy VIs for all the VIs in the DEBUG_TX_R.LLB as well? I have also emailed proximableu directly. Any input/ideas on this would be much appreciated. -Khalid

Hi Eric, You should be able to make Win32 API calls on Phar Lap RT. Here's a quote from their website: "Because ETS was designed as a Win32 API compliant operating system, all the standard Windows conventions are maintained. This includes APIs, memory management, mutexes and semaphores that Windows developers are accustomed to using." [Link] To confirm this, I just successfully ran -- targeted to my cFP -- VIs with the following Win32 calls: GetLogicalDriveStringsA GetSystemDirectoryA GetSystemTime GetTimeZoneInformation GetEnvironmentVariableA Coincidentally, all are from the kernel32.dll. Regards, -Khalid

Couldn't help but notice the "Modbus" in the function definition. Maybe you can find out if this device talks Modbus. There are Modbus VIs available from NI for free download (though their quality isn't the best). -Khalid

How do you know there's a memory leak? Can you post a simpler version of your VI? -Khalid

Check out the following example: examples\FieldPoint\Applications\Temperature Measurement.vi You can use this as a starting point for the FieldPoint part. Then, look at some examples on graphing data in labVIEW: examples\general\graphs And you should be all set to develop your own application. Let us know if run into any specific issues. -Khalid

Here's another variation: I have used a Cluster of numeric controls (restricted to 0 and 1 values only) and the KeyFocus property to get the "autotabbing." Run the VI and start typing the 0s and 1s. The last entry (7th bit) will output the final array of values entered. :!: NOTE: Run this VI by clicking on the Run arrow on the toolbar, and NOT by hitting Ctrl+r. Ctrl+r seems to trigger the KeyUp events! This behaviour can be fixed by filtering "Menu" keys (i.e., Ctrl) using the 'Mods' output in the Event structure. This is left as an exercise for the students Regards, -Khalid Download File:post-311-1140852807.vi

Thanks for pointing these out. They seem very promising for quick tasks and small utilities. Any idea how these scripts work? Do they turn around and call VBScript, or Windows API, or something even lower-level? Just curious... -Khalid

Here's my typical solution to such problems: download Portmon (or any other such tool) and monitor the actual bytes going in and out of the Serial port. This should tell you who is the culprit! http://www.sysinternals.com/utilities/portmon.html Hope this helps. -Khalid PS: In Portmon, I find it easier to work if I set the mode to HEX, and filter unnecessary commands and just get the READs and WRITEs.

It's obvious that LabVIEW is not able to connect to your mail server. Can you send/receive mail from this computer using any other mail client via the same SMTP server? -Khalid

Do you get any errors from the Email VI? -Khalid

What version of LabVIEW are you using? If you have 7.1 (and 7.0?), there are SMTP-based Mail VIs under the Communication palette. If you're using older versions, you will need the Internet Toolkit from NI. You could also check out the OpenG for these features. -Khalid

ECM, in the automotive industry, stands for Electronic Control Module. "Electronic Control Modules are subsystems consisting of CPUs and assorted signal inputs and outputs dedicated to controlling a component within the vehicle. They range in complexity from an Engine Control Unit which handles the logic for managing the power-train system efficiency, to an Anti-lock Braking (ABS) Control unit that monitors vehicle speed and brake fluid, to a simple body module that controls the automatic door locks or power windows. In many cases, these modules communicate to each other through such protocols as CAN, LIN, J1850, and J1959. The NI Automotive Test Platform provides a flexible and scaleable test architecture that meets these technical requirements in a cost-effective manner, throughout the product lifecycle, from design validation through manufacturing and service." Source: http://www.ni.com/automotive/ecu.htm

I don't mind.. if you send it -Khalid

What data do you want from the engine? What hardware are you using? Does the Engine use an ECM? Is it CAN based? -Khalid PS: your smiley's and fonts got all messed up.. maybe you should preview the post before posting.

It depends... if you're using a VISA resource for each "circuit board" then you will need to assign a new resource. Maybe you can give more details of your setup, etc. -Khalid