Getting LabVIEW Scripting out of the shadows

[Antoine Chalons]

QUOTE (Jim Kring @ Apr 17 2009, 02:14 AM)

To get this back on topic, I think that we should all wear tie-die shirts to NIWeek that say, "Legalize Scripting".

It's a great idea!

Let's do like last year and have a LAVA NIWeek T-Shirt Design Contest and then a poll.

[shoneill]

QUOTE (Val Brown @ Apr 16 2009, 10:38 PM)

I do all of that online in one operation so I'm not sure what's happening on your system except, perhaps, it's not online?

QUOTE

the development PC isn't connected to the internet

Shane.

[ned]

QUOTE (Val Brown @ Apr 16 2009, 04:38 PM)

I do all of that online in one operation so I'm not sure what's happening on your system except, perhaps, it's not online?

Yup, that's exactly what his problem is. If you check off the "Send me email confirmation of this activation" box when you install/activate your NI software, you'll get an email back with a bunch of long, unique codes, one for each product you've activated. So he's not getting different treatment than the rest of us with an SSP, he's just unfortunate to be working on a machine that's not on the internet.

EDIT: oops, somehow that comment was the last one on the page and I missed that the comments had spilled onto the next page where everyone else had commented on the same thing before I replied.

[Val Brown]

QUOTE (ned @ Apr 17 2009, 05:44 AM)

Yup, that's exactly what his problem is. If you check off the "Send me email confirmation of this activation" box when you install/activate your NI software, you'll get an email back with a bunch of long, unique codes, one for each product you've activated. So he's not getting different treatment than the rest of us with an SSP, he's just unfortunate to be working on a machine that's not on the internet.

EDIT: oops, somehow that comment was the last one on the page and I missed that the comments had spilled onto the next page where everyone else had commented on the same thing before I replied.

Shane et al: Yes that's what I thought but I guess the background implication in asking it that way is: Why isn't it internet enabled and/or why can't that be done just for this one operation?

CRELF: Yes, I'm sure you're right because the only possible timeline I've heard discussed is that scripting will be released AFTER all the toolkits are implemented for Linus and Mac and the timeline for THAT to happen was something like "...when Bush gets elected for the third time."

[TobyD]

QUOTE (ShaunR @ Apr 16 2009, 01:11 PM)

That said, I'm not talking about the Serial Key (I've got one of those that covers everything) I'm talking about the activation codes since the development PC isn't connected to the internet

Ahh, now I understand. I had to go through that once and it is a bit of a pain. My keys all came through in one email though - a little nicer perhaps.

[ShaunR]

QUOTE (Val Brown @ Apr 17 2009, 04:44 PM)

Shane et al: Yes that's what I thought but I guess the background implication in asking it that way is: Why isn't it internet enabled and/or why can't that be done just for this one operation?

CRELF: Yes, I'm sure you're right because the only possible timeline I've heard discussed is that scripting will be released AFTER all the toolkits are implemented for Linus and Mac and the timeline for THAT to happen was something like "...when Bush gets elected for the third time."

Because our IT is analy retentive.If I connect it to "THEIR" network then they have to have ownership which means the following:

1. Cannot take the lid off to install cards. Have to send a support request to get the card installed which may be in 2-3 days time if I'm lucky. If found "tamperig with company property"....written warning

2. No administrator priveleges. If software needs to be installed...Yup..you guessed it..Support ticket...2-3 days.

3. Must have a defacto desktop/laptop PC with all the their crap and must use XP even if the customer wants Vista.

4. The licence would have to be in one of their names (as you know...NI only supply support to the name on the license) so they can provide me with support <img> which means that yet again I would have to send a support ticket to get them to phone NI to asks a question which they know didly squat about.

I will just point out though that I do have number 3 also. They decided that a dual core (not even core2) 1.6 GHz Toshba laptop with 512MB ram and a 20 Gig hard-drive is an adequate Labview development platform. It takes 20 minutes to boot in the morning if connected to the network because of their policies.

Because of that, I run Labview, labwindows, test stand and all the toolkits on an industrial PC on it's own network where I can do what needs to be done. When it needs to be done.

We actually rate our IT department as a project risk. The less involvement...the better.

So. It is a real pain but the alternative is worse!

[asbo]

Jeez, I was wondering what kind of insane situation one could be in to require the circumstances you described. That's harsh stuff ...

[Grampa_of_Oliva_n_Eden]

QUOTE (ShaunR @ Apr 17 2009, 04:38 PM)

Because our IT is analy retentive.If I connect it to "THEIR" network then they have to have ownership which means the following:

1. Cannot take the lid off to install cards. Have to send a support request to get the card installed which may be in 2-3 days time if I'm lucky. If found "tamperig with company property"....written warning

2. No administrator priveleges. If software needs to be installed...Yup..you guessed it..Support ticket...2-3 days.

3. Must have a defacto desktop/laptop PC with all the their crap and must use XP even if the customer wants Vista.

4. The licence would have to be in one of their names (as you know...NI only supply support to the name on the license) so they can provide me with support <img> which means that yet again I would have to send a support ticket to get them to phone NI to asks a question which they know didly squat about.

I will just point out though that I do have number 3 also. They decided that a dual core (not even core2) 1.6 GHz Toshba laptop with 512MB ram and a 20 Gig hard-drive is an adequate Labview development platform. It takes 20 minutes to boot in the morning if connected to the network because of their policies.

Because of that, I run Labview, labwindows, test stand and all the toolkits on an industrial PC on it's own network where I can do what needs to be done. When it needs to be done.

We actually rate our IT department as a project risk. The less involvement...the better.

So. It is a real pain but the alternative is worse!

I swear I have you guys as a customer. I think my contact brings me in just to deal with talk IT at them. :headbang:

Ben

[Charles Chickering]

QUOTE (Jim Kring @ Apr 16 2009, 07:14 PM)

To get this back on topic, I think that we should all wear tie-die shirts to NIWeek that say, "Legalize Scripting".

I'm in. Just let me know when you get the shirts made.

Charles

[Michael Aivaliotis]

Some news over here on this topic.

[Cat]

QUOTE (ShaunR @ Apr 17 2009, 04:38 PM)

We actually rate our IT department as a project risk. The less involvement...the better.

What a great idea!

I feel your pain about the whole IT thing. That's why my development computer is off the net, too. And why, if I have to reacvtivate LabVIEW (or read or contribute code to LAVA), there's lots of SneakerNet involved going back and forth between the Official Computer and my real computer.

[JackDunaway]

Here is my position on the topic:

Scripting is out there and many people are using it to create some amazing tools for assisting LabVIEW development and automating various tasks. I'd like for NI to give us its blessing to create such tools, so that we don't feel like renegade outlaws and can feel comfortable sharing them with others. And, I'd love for NI staff to be able to contribute to the technical discussions around scripting -- the current position from NI seems to be that it doesn't exist. Bottom line, machine readable and writable source code is a prerequisite for creating software engineering tools. And, it would be great for NI to empower the LabVIEW community to create better software engineering tools for LabVIEW. Bottom line: I think that it would be of great value to let the LabVIEW ecosystem create innovative features and tools on the LabVIEW platform. It's a win-win situation.

 

 

 

This post is quoted during Jeff Meisel's keynote presentation (@9:39 in the video).

 

Jeff emphasizes the importance of NI collaborating with the community to build key API access into the LabVIEW platform, and how the efforts of community leaders have paid off in the past several years.

 

Link to the presentation: http://www.infoq.com/presentations/National-Instruments-API

[Phillip Brooks]

I read this last night...

 

http://techcrunch.com/2013/04/28/facebook-and-the-sudden-wake-up-about-the-api-economy/

 

APIs Are Like Glue

 

In the first generation, Mashery and companies like Apigee pioneered the API management space. Twitter and other web companies emerged in the second generation. In the third wave, enterprise vendors, like Intel and CA, are recognizing this big movement and entering the market to connect hardware and software systems.

 

Now the API movement is headed below the application to the machine level, Doyle said. It’s at this level that we see the emergence of the Internet of Things. Here, everything becomes programmable, able to send and receive data, integrate it and trigger actions.

 

I've noticed an up-tick in Arduino type questions on the NI forums. 

[hooovahh]

I've noticed an up-tick in Arduino type questions on the NI forums. 

I have too, and I hope that means they will push for more refinement with the Arduino tool kit they made.  Possibly charge some small amount for it so it can get some more support and development.  I mean it works don't get me wrong, but I find minor bugs with it, and not officially supporting several Arduino boards.  It doesn't look like support has stopped (last revision was last August adding IR Transmit VIs) I would just expect more interest for low cost hardware when combined with rapid prototyping in LabVIEW.