xtal

Yay!! I can't wait to see everyone again!

I am not sure whether if it able to work in labview 8.2.

or is there any other ways to get the same results?

Yes, the Database Connectivity Toolkit works fine with LV 8.2 and it comes with lots of examples.

You can use ActiveX or DotNet to directly communicate with an SQL database.

Here's where Todd (of An Engineering Mind) interviewed my team: http://www.youtube.com/user/anengineeringmind#p/u/7/DbGEWnkH4FM

So my question is if I was to interface to say a MySQL database on the same machine as my LabVIEW application through the NI-CT can I just create the following ini file:

Server=localhost;Database=imt;User ID=root;Connection Timeout=60;Trusted_Connection=FALSE;Net=dbmssocn;

and I could just pass these values into the DB Tools Open Connection.vi and it would link to the database?

Yes, you just wire the string directly to the Connection Information input on the Open Connection VI.

Hey, Mark

I enjoyed reading your Tweets about your team. Y'all did better than us in the general competition but we got some great breaks with winning awards and such. Here is more info on our team:

Team 2486 - The CocoNuts from Coconino High School: http://www.fusd1robotics.org/chs_robotics/index.htm

And here is a video of our first attempt at driving the robot: http://www.youtube.com/watch?v=Z9-MILWge04

This has been tons of fun!

Hi, Chris

I don't have a complete answer for you because it's been a while since I've had to build an installer like you mention. You didn't say what version of LabVIEW you use; my suggestions refer to the Installer Build Specifications found in LV 8.x projects:

- System DNSes are registry entries. So you can figure out their various keys and have either the installer create them or you could write a short LV program or batch file that creates them and runs after the main installer. There is a Registry category in the Installer Properties.

- In the Advanced category in the Installer Properties you can specify EXEs to run after the main installation. I've used this to install non-NI drivers, run batch files, etc. You could use this to install MySQL components. You can also enter command line arguments here.

I just wanted to see if anyone else on LAVA was attending the 2010 FIRST Robotics Competition next week. I'd love to get together with other folks and chat about mentoring over a coffee or beer.

Crystal

{Also hoping to see some temperatures above freezing and some ground cover other than snow for a few days}

I feel for you, Scott! That looks like all the projects I inherited when I started working here. I can very well understand why everyone else in my group now hate LabVIEW and refuse to use it.

I was at the Arizona Regional last weekend and it was amazing!! The team I mentor won the Engineering Inspiration award so that means I'll also be going to Nationals in Atlanta next month with them.

Good luck to everyone and I hope to see you in Atlanta!

I've seen the same thing, channels switching in the middle of a run, with an SCXI system I use here occasionally. I never did figure out what the problem was because it was so intermittent and unreproducible. I am using LabVIEW 8.2 and the SCXI-1600 with 2 or 3 SCXI-1112 modules.

xtal = Crystal

I'm pretty sure DNS entries are just registry entries. So you can figure out the format of the mySQL ones and then use the Registry VIs in LV.

Congrats, Mark!!

Congrats, Mark!!

And I completely understand about the tarantulas...I only have one but she's fascinating to watch and learn about.

QUOTE (crelf @ Jan 12 2009, 07:27 PM)

It's good to know that I'm not the only one with this issue :thumbup:

I'm in the same boat as you are, Chris. Regulated industry and everything. Luckily for me, we just switched to SVN from VSS. Now I know what to look out for.

Good luck.

QUOTE (jlokanis @ Dec 30 2008, 03:09 PM)

Yes, the NI toolkit is very slow, due to their use of the ADO.NET interface and the aforementioned iteration issue.

Hey, John

I just wanted to make a quick clarification. The NI Database Toolkit uses ADO, the ActiveX version and not .NET. It does have VIs to do the faster GetRows calls mentioned by others. ADO is what LabSQL uses, too, so I doubt it would be any faster than the NI Database Toolkit. However, I believe ADO has less overhead than ADO.NET or any of the .NET interfaces. I'd be interested to know for sure if that's the case.

I've been using the .NET interface quite a bit lately with SQL Server, but we are much more interested in data security than speed, so I've not done any benchmarking. And, like you, we use lots and lots of custom SPs.

Good luck and please let us know how this turns out.

QUOTE (Aristos Queue @ Jan 6 2009, 06:46 PM)

Have any of you filed a bug report? If not, please do so with VIs/lvproj files attached that reproduce the bug.

Originally I went through hoops with Tech Support for weeks to get things hacked enough to run and my recent crashes aren't reproducible other than they always occur in tagger.exe.

Hey John!

It's great to see you posting on LAVA and starting those blogs. Now that I'm on the other side of the fence, I really appreciate things like this.

Thanks!!

Yes, I see the same thing with one of my main projects after upgrading from 8.2.1 to 8.6. Always an asterisk on it. I don't use auto-populating folders but LV 8.6 has crashed on me a number of times.

QUOTE (hooovahh @ Oct 7 2008, 09:38 AM)

I was kinda hoping this would be a scripting VI which scan a set of VIs and locate all the misspelled words, now that I would use on every VI I made. But that wouldn't fit into your "quick and dirty" definition. This is still a cool program without the scripting feature.

I use the Spell Checker in VI Analyzer for this. It scans all the VIs, gives a list of misspellings, and you can double-click and it takes you to the place the misspelling occurs. Quick, easy, and you can add words to a user dictionary for company acronyms and such.

Chris, I think there might be something wrong with you...I couldn't make it past a minute.

And Norm is a much better dancer than this weirdo (but I didn't see his happy rollerderby girl dance, either).

At one point, there was a bug in the ODBC drivers for Oracle that limited the size string (or BLOB) you could write at one time. However, with the OLE DB Provider for Oracle, I was able to write 8 MB BLOBs of data (maybe more, I honestly can't remember anymore - it was in the CAR) with no problems. I kept writing bigger and bigger BLOBs to an Oracle table until I ran out of memory. So I recommend checking what driver you are using for your data communication through ADO.

Yes, the NI website is having some serious problems. It took me a day and a half to look up a couple products and get a simple quote.

I'm with you all the way. I still have a sore throat and sniffles after being so cold in the convention center. And this time I had two sweaters on at all times. I come from a climate where we don't need air conditioners and am so thankful to be home.

QUOTE (Aristos Queue @ Jul 30 2008, 12:01 AM)

Don't buy one. I have a spare you can try when you get here.

Thanks!! Bring it to the BBQ if I don't see you before then.