Jump to content

CraigGraham

Members
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

0

About CraigGraham

  • Rank
    More Active
  1. The path's being ignored anyway- the DLLs are in a seperate folder elsewhere in the PC's filesystem, but the installer shoves them all in a support folder in the same directory as the built executable, called "data" by default. We did try FTPing the original executables in- that's the reference executable I mentioned. And regarding taking an image- anyone know how? This just has RT installed. NI built the PXI controller up, and gave a multiyear warranty for it which I suspect'd be voided if I was to take the hard disk out and put it into another machine to read an image off.
  2. I've a problem with a PXI chassis running LabviewRT at a client's site. Some months ago, we got the chassis from Labview, installed necessary DLLs for a couple of non NI cards and put our app on there; it then worked fine until the client reformatted the disk and reinstalled Labview. Precisely why this happened is unclear but doesn't seem to be related to a problem with the software. We're on 8.6.1. I reformatted again and reinstalled myself, to rule out any oddities that might have occurred when the client did it. We're now in the position that although as far as I can see the software and
  3. We have to put a bid in on a project that the client has decided to use Compact RIO for. New toys they want to play with. I've not done it before so I've been playing with the FPGA module and FPGA interface in Labview 8. Actually doing FPGA code and running it on a bit of hardware set as emulated works fine, but I need to be able to communicate with a UI VI on the host PC. When I (or any of the examples) try to open a reference to the FPGA VI from the host, an error is generated to the effect that Labview can't find the hardware. Should I be able to do this on emulated hardware or is the emu
  4. QUOTE(ashishuttarwar @ Nov 26 2007, 12:20 PM) Yeah, using App Builder on the machine having set the LV execution target to cFP gives you that startup option and installs straight to cFP. As far as I can tell, though, there's no way of getting that option if you don't have the target cFP connected. There's unofficially a dev environment still installed down there that I shoved on for debugging, so for the moment I can talk him through App Builder on the phone, but if we can't officially update a cFP installation without going down with a full development system then it's a mark against usi
  5. I've a distant cFP unit that needs an update to the VIs running on it. App Builder (LV7.1) has options to prompt for an RT target, so I bundled it all up into an .exe to ship to the client, who then ran it and selected the cFP unit. It downloaded without error, but following a cFP reboot the old app is still there. Is there a way to get an executable I can send to the client which permanently updates cFP in the same way as when I run App Builder on a PC local to the cFP unit and build directly to cFP? The way I've tried so far seems to be akin to targetting Labview at cFP, loading the VIs an
  6. I've a distant cFP unit that needs an update to the VIs running on it. App Builder (LV7.1) has options to prompt for an RT target, so I bundled it all up into an .exe to ship to the client, who then ran it and selected the cFP unit. It downloaded without error, but following a cFP reboot the old app is still there. Is there a way to get an executable I can send to the client which permanently updates cFP in the same way as when I run App Builder on a PC local to the cFP unit and build directly to cFP? The way I've tried so far seems to be akin to targetting Labview at cFP, loading the VIs an
  7. I've got to make some mods to a legacy VB6 app that's written using Imaq, NI-DAQ and ComponentWorks. There's no documentation about build environment. I've installed VB6, NI-DAQ, IMAQ, NI-Vision and Measurement Studio into a VM running XP and can now load the project without it bailing out due to missing .ocx files etc. However there's methods and types that are unrecognised- initially, CWIMAQBCGOptions. VB6's autocomplete does recognise "CWIMAQBCGOptions" but when I try and build/run the app I get a compile error "Can't find project or library". Google and NI's search give no hits. Anyone k
  8. QUOTE(Neville D @ Mar 20 2007, 06:13 PM) No, could find nothing like that in MAX. I didn't have the old IMAQ on the machine so couldn't try the old examples. What it turned out to be was a register "ISO_ENABLE" inside the camera. This register gets set when calling IMAQdx Start Acquisition and overrides the single/multishot settings defined by the "configure acquisition" VI to force the camera into free running. Writing a zero to it immediately after calling start acq. gets everything working fine. This behaviour is there even when setting the camera to a non-ISO capture mode in MAX so
  9. I'm playing with a firewire camera in IMAQdx, LV7.1. Yeah, not got round to updating to 8. I've done an ugly as hell test VI (that I'm not going to post in its present form) that's based around the code in "IMAQdx Snap.vi". The only functional changes are to put the Start Aquisition...Get Image...Stop Acquisition group of sub VIs inside a while loop to snap an image every time I hit a button, and to monitor and display the output of various digital lines as it's happening. What I've discovered is that the camera is actually taking 2 shots each time. Further investigation reveals that, even i
  10. I've got to go fix a project I'm unfamiliar with, and I'm looking through the code to get pointers. It's a PC talking to a cFP unit via the TCP VIs. There's also the data publishing stuff and direct Fieldpoint IO point reads being used at the same time. Symptoms are that after an unspecified length of time, the PC loses comms with the cFP unit. There's two places the reported error can come from- first is from a Fieldpoint network read function, second is if the TCP bit fails to establish a connection. I suspect the latter. The way this is written, the TCP stuff opens a connection, sends
  11. CraigGraham

    Watchdog

    I'm revisiting a cFP project I've been away from for a year, and I no longer have access to the hardware until the few days when I go onsite to deploy an update. I want to add watchdogs to the cFP code, but can't seem to find decent info and with no cFP controller I can't play. Don't want to be implimenting new features in the deployment time. I have several loops, and ideally would like one watchdog per loop so if any loop hangs the whole thing reboots. Can I do this simply by having multiple "Watchdog Configure" nodes and wiring the watchdogIDs to whack nodes in the individual loops? I've
  12. I did a check of this since a recent app makes a lot of use of abstracted data types for plugin modules. Converting a test cluster from a variant to data, modifying an element then converting it back to a variant takes about twice as long as when the conversions are to and from flattened strings. So aside from the implicit conversion to variant, variants no longer have any appeal to me. Would be nice to be able to define a string input to a VI as being "implicitly flatten".
  13. It's a poor substitute, but you can use ActiveX controls under Windows- either existing ones or ones you've created yourself in a different language. Before NI supplied a treeview control, for instance, I was using the standard Windows one via ActiveX. Obviously many drawbacks over a native G implimentation, but it does have uses.
  14. How long has that "prepare for reentrant execution" option been there? i.e. how long have I needlessly been messing around with VI templates?
  15. Ooo. There IS an option "--no-tty" that I thought just suppressed all output. It turns out it lets me redirect the streams to get at them from inside Labview, but when I try and do interactive stuff it tries to be too clever; gpg: Sorry, no terminal at all requested - can't get input So I think I'll call it quits for the moment. There's two alternatives- LibGCrypt on Linux that I'm going to play with, and the commercial PGP SDK that I'm looking into. Though I suspect the commercial one will be a bit too pricey and charged per deployment. Can Labview on Linux use dynamic link libraries? Migh
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.