i2dx

why do you want to punish them for doing a good job? That's unfair

go to http://www.ni.com/labview and take a look at the LabVIEW Add-On Modules and Toolkits Section. There is a description of every toolset you can get from NI for LabVIEW

I can replicate this in LV 8.20 and LV 7.1.1

It's nice to have a "non official but obviously fast and reliable mechanism with semi direct access to the developers for bug reporting" here Thank you Stephen

hmm ... Access does support this in a *certain* way, but I would not use it, because the Jet module creates a local copy of the *.mdb file for each query, which means, that you get a real huge network load with increasing file sizes and if your network gets to slow, you have a good chahce to loose the integrity of your data => if you have multiple clients, use a DBS

hmm, maybe a good start is the pinned post "VI Scripting - readme first"?

hmm - I am not sure - but I think this is a really good way to get a corrupted project. LV 8.x opens one application instance for each target and keeps them synced. If you edit a VI with your "own external" LV instance you can have different copys of the same file in memory and I think that will mess up your whole project.

hmmm ... just to be honest: business as usual = show a little smile on things that have improved and rant as loud as you can if something does not meet your expectations. the reason why I started this thread was (as described in the subtitle ) that I felt that I should not just rant but mention the things that have improved from 8.0.1 to 8.20

Check the interface configuration of the 34970A! as far as I know, GPIB is the default setting for this device, so you have to switch to RS232 and check the communication settings (Baud Rate, Start Bit, Stop bit, Handshaking, etc ...) The communication is plain ASCII, maybe you want to turn of the termination char? The device should respond to a IDN? query with the device ID - you can check that with a terminal programm. If you get a response the RS232 communication works properly. good luck

hmm, strange. LV 8.20 seems really stable to me. The only (reproducable) situation when LV crashes is, if I edit a typecasted enum, which is part of a e.g. typecasted cluster AND a VI containing one of the typedefs is open. LV crashes on the "save and replace" dialog. I have informed NI about this behaviour, but it has not yet been confirmed as a bug - although the AE could reproduce it - it seems they are still working on it

that's why I do not post in the other forum - but it's a phrase from the Microsoft website, not from NI. Whatever, I hold the opinion, if you want to program some piece of hardware, you have to have some skills. No programming language or code generator can replace the knowledge of a programmer. Neither can Express VIs replace the knowledge of how to correctly acquire data nor can a "robotics toolset" create

hmpf ... sorry, but this is marketing bulls%&"

some time ago, I have written a RS232 demo. You can find the (LV 7.1.1) code here

Status Update: confirmed as a bug. CAR ID=44715JAQ will be fixed with LV 8.2.1 workaround in the meantime: don't use the application exit event ...

as far as I know there is a separate scripting license file, you can get from NI, but HOW to get it is an other topic: maybe you have a chance, IMHO you need 3 prerequisites: a) a good reason why you need it b) a signed NDA c) a good relationship to NI, maybe a LV Champion is helpfull for the rest it will probably be a NSL (No Such License) please let me know if you got it, I'm interested, too

hmm ... I would not expect everyone to become a premium member. IMHO Premium Membership is not intended to make MichaelA ritch, but raising the funds to operate this site!?

hmm, this is a dog eat dog situation, because YOU produce a big bang with a preassure cooker ... (and it definitively produces background microwave radiation!) strange ... I'd like to diskuss more asspects about this topic and I'd like to call that the "LAVA paradoxon"

no, it's not running on a RT system, but you are right with your comment! using "quit labview" on a RT system results in "strange behavoiur" e.g.: your application remains in memory can restart if you open max and edit tasks! the reason for my problem was an other one: If you have an event structure in your application, which catches the "application instance close" event, the quit labview function will not work any more. I have reported this as a bug and I am waiting for confimation ... You can try it out with the attatched VI, the behaviour is reproducable on my system - even in the development environment LV will not close on calling "close labview", while calling the function without the event structure closes labview (as it should). thank you all for your quick response! Download File:post-885-1165504596.zip

Hi everybody, I have a problem with the exit labview VI in a compiled exe (LV 8.20): I have the "exit LabVIEW" VI in the last frame of my main VI: this should close the RT Engine instance of labview, but it does not. the VI stops, but remains open has anyone an idea, why?

hmm, but there is not much difference between a pressure cooker and the big bang, isn't it ?

ok, that's fine, then chris was a really good choice :beer:

just to make you feel better: [ironic] well, you're right ... I would have prefered Jim as the first TALM ever, too [/ironic] anyway, even I think, you deserve it and regarding the SNR: sometimes, a "I dunno"-answer helps, too cheers and congratulations!

hmm ... I don't think so. These postings make sense here, because it's topic is about the fifth dimension. But the fifth dimension is hard to get and therefore it makes sense to start with the well known 3 dimensions, which are shown in martins post. Maybe we add some information about spacetime here and then - who knows? - we are maybe able to proceed to the 5th dimension? It would be really interesting to know, how to programm in 5 dimensions

hmm ... if you only need the average of your values @ 1 Hz, maybe you want to use my "IBB Logger Base" ? It accuires data internally @ 1 kHz and you can decide, how you want to evaluate your data (Average, RMS, etc ...). You can select a "Sampe Rate" from 10 Hz to 0.1 Hz (?) and all Data are displayed on the front panel and logged into a database, where you can export them into an *.CSV-file You can download it here: IBB Logger Base 2.0.1 Please let me know, if your DAQ-Hardware is not supportet. As far as I can be used with DAQmx, I can give you an update, which supports your hardware ...