LabVIEW 2012 and LegoNXT

Hi,
Will my EV3 Lego mindstorm brick work with LabVIEW 2012 and LabVIEW Lego MindstormNXT 2012? Because when I'm installing LabVIEW module for Lego 2012, it'sprompting me to install LV2012 SP1. I already have LV2012 but NOT SP1. 
Regards.

NapDynamite wrote:
The system in my lab has no SP1, probably the guy over here never bothered to install that update. Now when I checked those updates to install SP1, the update service is locked for this patch and is asking for renewal of subscription.
My boss, who is not very cognizant of software stuff, is now asking me to use the EV3 software which comes along with LEGO pack becuase he's not ready to spend much to renew.
And my dream of teaching LabVIEW to school kids is now in vain.
Regards. 
In vain?
A bit dramatic isn't it?
One license is $99.
Site license is $570.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/210666

Similar Messages

  • LAbVIEW 2012 and Solidworks Examples update

    Hi,
    I noticed that the examples shipped with NI Softmotion module is not updated (SoftMotion>Mechatronics). Although the directory has been changed, the example still points to LabVIEW 2009 folder. I also would like to ask whether these examples was tested with LabVIEW 2012 as it doesn't run with my machine which has LabVIEW 2012 and Solidworks 2010 SP4.
    Your help is much appreciated.
    P.S: I apologize for double posting since no single reply was mentioned on Motion forum.
    Waleed El-Badry MSc.,MCPD, ISTQB Certified Tester
    Assistant Lecturer
    Mechatronics Department
    Faculty of Engineering
    Misr University for Science & Technology

    The problem seems to be with Scan Engine.
    Here is a screenshot of the error mesage when deployment:
    Configuration:
    OS: Windows 8 Final
    LabVIEW Version: 2012 with all updates installed
    NI SoftMotion Version: 2012
    Solidworks Version: 2010 SP4 
    I doubt the problem lies in OS as all examples are running flawlessly except that with Mechatronics Examples. Hope to get any response from NI SoftMotion Team. Thanks for your assistance in advance.
    Waleed El-Badry MSc.,MCPD, ISTQB Certified Tester
    Assistant Lecturer
    Mechatronics Department
    Faculty of Engineering
    Misr University for Science & Technology

  • I have both LabVIEW 2012 and 2013 but MathScript RT Module can only be installed in 2012 not 2013

    It can be succesfully installed on 2012 and I can't choose to install it on 2013. Why can't I install MathScript RT Module on both versions? Or did I do anything wrong?

    Are you installing the  version of the module that matches the LabVIEW version?
    What kind of errors do you get?
    LabVIEW Champion . Do more with less code and in less time .

  • How to build a TestStand 2012 workspace ( insert a project / insert a folder) programmat​ically using LabVIEW 2012 and the TestStand API.

    Hi everybody!
    I am just trying to find out how to create a TestStand workspace … in LabVIEW using the TestStand API.
    To create a new workspace was quite easy. Unfortunately I am not successful to insert a new or existing project to the workspace.
    Furthermore I have to insert a folder from disk to the new or existing project in the way that I can use an absolute path for the directory …  
    Maybe someone had already solved this problem, in any case  I am thankful for any hint.
    Greetings from Germany,
    Norbert

    Have you find out how to add a folder to a project? I'm looking for this to... I tried WorkspaceObject.NewFolder[Name]whitout success...
    For creating Workspace and project see the newer resolved thread I created.
    Martin

  • Report Generation Toolkit Compatibility with Microsoft Office 2013 and LabVIEW 2012

    Hello community,
    on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
    In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
    Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

    Hi digital_badger,
    as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
    1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
    2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
    Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
    3. You could leave your setup as it is and stick to your MS Office 2010.
    I hope I could give you a good answer to your question

  • LabView 2012 Security System Main vi's have error 200559

    The vi's give errors of 200559 in my LabView 2012 and NI application engineer "John Staskal" told me as "Another good step 
    is to recreate the VI in your current version of LabVIEW so that you know the error is not caused by upgrading the VI to a newer version of LabVIEW." I did all that, but not resolved.
    Their application engineer John Staskal also told me as "In addition to working to resolve the error you may want to pursue is posting on our upgrade forum and asking the community to convert the VI to a current 
    version of LabVIEW.  http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion".
     I did all trouble shooting steps such as highlight execution, probes, etc as what their application engineer told me and still having error of 200559 in LabView 2012.
    I  appreciate help from any one.
    Ali Tariq Bhatti
    Ali Tariq Bhatti
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    NI ELVIS II Security System VIs (2).zip ‏313 KB
    Error 200559.docx ‏500 KB

    RavensFan,
    I) Yes, I open up the front panel of the Express VI's and probe into them.
    2) I use the express vi's, but if you see my attached vi's file. You will see Security System Main vi is the main vi where the program is running and where I am getting the error of 200559.
    3) I also attached the word document file, so I am getting error of 200559 in probes 3, 4, and 5 using Export Key Press and Voltage vi's in this post.
    4)Do you know, how to convert these my attached vi's to 2011, 2010, 2009, or LabVIEW8.5 version. May be, it fix the problem, or if you know some one to get help from or get chance to use ELVIS II board, so let me know .Your help or any one's help is appreciated.
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    did probes for Export Press and Key vi's file.docx ‏340 KB

  • LabVIEW 2012 f1 Patch crashes

    I've just installed LabVIEW 2012 and unfortunately I've already run into some troubles.
    I received a "Setup has stopped working" when I installed the device drivers.  But the installation appeared to be fine.  LabVIEW started and MAX would open.  I did not try connecting to any hardware yet.
    When attempting to install the f1 patch, LabVIEW crashed again.  Subsequent retries net the same thing. 
    Has anyone else had this trouble with the patch?   
    This is on a Win7 machine with LV 8.6, and 2011 previously installed. 
    Patrick Allen
    Solved!
    Go to Solution.

    Why do you have LabVIEW open when you are trying to install a patch?  Are you running other versions of LabVIEW when performing the install?  It is highly recommended you are not running anything NI when running installers from NI.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Upgrade to LabVIEW 2012 caused Additional Installers issue

    Hello again all you helpful forum-goers!
    I have been using LabVIEW 2010 (SP1) for a while on my Windows XP computer, but I recently purchased and installed LabVIEW 2012 for a future project.  In the meantime, my previous projects must still use LabVIEW 2010 until I use my company's formal change tracking system to upgrade them.  However, when I recently opened one of my older projects in 2010 to update it and rebuild the installer, I saw in the Additional Installers tab a bunch of blank lines at the end of the list (see attached screenshot).  This doesn't directly hurt me, but I have to think it is a symptom of the root problem.
    More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked.  That seems like an upgrade oops on National Instruments' part to me.  I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
    Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk.  "FADEC_Emulator" is the name of my software.  Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3.  Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked.  However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3).  Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3?  Confusing!  And if it did that, why didn't it have that version handy already?  And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
    I'm afraid that since installing LabVIEW 2012 my system has gotten into an unstable state, and I now have possibly corrupted my project's LV project file.  I need to have both 2010 and 2012 on my computer for the time being.
    Does anyone have any idea what is going on with my system, and/or how to fix it?
    Thank you very much in advance for your suggestions and time!
    -Joe
    Solved!
    Go to Solution.
    Attachments:
    Additional Installers Blank Lines.png ‏45 KB

    Hi Joe,
    I tried to reproduce your issues, and encountered mixed results. Please verify with what I've provided below that we are testing under the same conditions
    jmorris wrote:
    More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked.  That seems like an upgrade oops on National Instruments' part to me.  I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
    In this scenario, I built a test project with VISA RT 5.0.3 and LabVIEW 2010 configuration. I then installed LabVIEW 2012 and VISA 5.2.0 on top of the aforementioned setup. When I opened the 2010 project in 2012, VISA Run-Time 5.2 was checked (as expected, dissimilar to your configuration). As I mentioned earlier, this may have been because VISA 5.2.0 did not install properly.
    jmorris wrote:
    Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk.  "FADEC_Emulator" is the name of my software.  Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3.  Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked.  However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3).  Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3?  Confusing!  And if it did that, why didn't it have that version handy already?  And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
    For this case, I built the installer on LabVIEW 2012 with VISA RT 5.2.0 then saved it for LabVIEW 2010 compatiblity. When I opened the installer in a LabVIEW 2010 with VISA 5.0.3 environment, VISA 5.0.3 was checked (as expected since LabVIEW will default to the latest version of VISA on the PC regardless of what the original installer referenced). I did, however, see three extra blank lines in the additional installers tab (more on this below) . I also tried to build the installer as you indicated, but did not get any prompts for disks and was able to build successfully. 
    One thing to keep in mind is that LabVIEW by default will use the version of the driver that is installed on the build PC, regardless of whether it is newer or older than the installer references. If you feel this negatively impacts your successes as a developer, please feel free to post a feature request (e.g. for a prompt when the driver version changes) in our idea exchange forum (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas ).
    Lastly, regarding the empty lines in the additional installer specifications, this problem appears to be fixed in LabVIEW 2012 and only manifests itself in 2010. During my course of testing, this did not affect building the installers and is a minor inconvenience which has been fixed in subsequent versions.
    Please let me know if you have any additional questions/comments regarding these issues. 
    Regards
    Doug W
    Applications Engineer
    National Instruments

  • Can I get MJD (date and time) in LabVIEW 2012 SP1?

    I need to time stamp my data before sending it to the file.  I have been doing this with the standard calendar date and time but MJD is what we prefer to use.  How can I get an MJD timestamp in LabVIEW 2012 SP1?
    Solved!
    Go to Solution.

    Hello Brad_Henry,
    The Format Date/Time String will return the day of the year when the %j argument is used, as per this help document:
    LabVIEW Help: Format Codes for the Time Format String
    http://zone.ni.com/reference/en-XX/help/371361J-01/glang/codes_for_time_format_str/
    If you're looking for the actual MJD, I'm not aware of a built-in function that generates this so you'll probably need to create or find a function to calculate it manually.  This should pretty basic arithmetic, and it looks like people have already made a few public examples, the first two search results here look to be just about what you need:
    ni.com search:
    http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:ex/q/julian/
    Regards,
    Tom L.

  • Compatibility of LabView 2012 installed on XP with Vision and Trad DAQ

    Is LabView 2012 runnung under Windows XP compatible with
    A: NI Vision 2011 ? 
    B: Traditional DAQ 7.4.4 ?

    This should answer your question:
    Windows Version Compatibility with LabVIEW
    Compatible Versions of Vision Development Module with LabVIEW and LabWindows/CVI
    NI-IMAQ, NI-IMAQdx, NI-IMAQ I/O, and VAS Compatibility with Different LabVIEW Versions
    NI-DAQ and LabVIEW Version Compatibility (for Windows)
    I would still suggest to have a look at the readme files as well.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • Again mixed signal graph and Labview 2012

    I have just experienced a weird change in labview 2012 on the mixed signal graphs. In a preliminary analysis, it seems that the most critical behavior is related to the silver mixed signal graph, although i didn't have the time to test the standard one.
    Straight to the point... the property "plot area size" not only resizes the plot area, but also the graph; this is in contrast with what happened previously in LV2011. If the graph belongs to a subpane and if the property "fit control to pane" is enabled, the area resize prevents the graph from correctly fitting the pane. 
    Any suggestion?
    cheers
    m.
    Attachments:
    MixedSignalDisaster.vi ‏13 KB

    I think that since this behavior is a regression (working properly until LabVIEW 2011 SP1) this should be fixed as soon as possible through a specific fix, without waiting for the next Service Pack.
    This regression has been blocking the development of our application.
    Could someone from the NI support give an answer, please?
    Vix
    In claris non fit interpretatio
    Using LV 2013 SP1 on Win 7 64bit
    Using LV 8.2.1 on WinXP SP3
    Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
    Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

  • Installing both Vision Builder 2012 and LabView 2012 on same Computer

    am new to NI Vision Builder Automation Inspection 2012 (Which I am supposed to learn and use for part inspection) as well as LabView (Which I need not know at this time)
    When I was presented (to work with) a 1722 Camera and the computer, Labview 2012 was already installed but not Vision Builder.
    The IT folks installed the Vision builder without uninstalling LabView.
    I have my problems getting upto speed with my inspection work, but is any of it attributed to both systems being on the computer?
    Can I (Must I) uninstall LaView??
    Thanks

    LabVIEW and Vision Builder run fine on the same computer.  I have several versions of each on mine with no problems.
    Bruce
    Bruce Ammons
    Ammons Engineering

  • Labview 2012 (64bit) not working with ActiveX and MSAccess

    I have a program developed to open a MSAccess database file and import data using ActiveX commands. The program works with LabView 2012 (32bit) but fails on the ActiveX open command when using LabView 2012 (64bit). I also have the application built as an EXE and it works fine in a windows 32 bit environment (XP or Win 7-32bit) but fails when run on Win 7-64bit. I isolated the error down to the Active X automation Open VI.
    Anyone have a solution for the incompatibility?
    summary
    1.) VI and EXE works on XP and Win 7-32bit
    2.) EXE fail on Win 7-64bit.
    3.) VI works on Win 7-64 bit with LV 2012 (32bit)
    4.) VI fails on Win 7-64 bit with LV 2012 (64bit)

    It looks like you are trying to load a 32-bit DLL from a 64-bit OS. Do you have a 64-bit version of access installed? You'll need to change to that. On the other hand, ActiveX with Access is so slow. You can speed things up considerably by using ADO (i.e. NI's Database Connectivity Toolkit or something like LabSQL).

  • Os x maverick and Labview 2012

    Do have anybody experience with Labview 2012 under OS X Maverick? Is it any trouble after update from Mountain Lion (10.8.5) to Maverick with Labview 2012?
    Solved!
    Go to Solution.

    Hi Vitko,
    Maverick is at this point regretfully not supported.
    That being said - it might work - it really depends on what changes did Apple did to the kernel in the meantime.
    Maybe some of the forum users have hands on experience that they can share about trying this combination.
    Best regards,
    Jano

  • Some fonts are not shown correctly in LabVIEW 2012

    I found a bug related with fonts in LabVIEW2012 f3 KR.
    - When I select NI7SEG in font selection dialog, right font is not shown in the example box.
    - Draw text at point.vi shows same problem for some fonts while other fonts are working.
    I reported it to Korean NI. As far as I know, this was not reported in previous versions and I couldn't find any related documents in Google. 
    So, here I would like to know whether it is related with only Korean version. Please let me know if English version is OK. 
    * OS: Windows 7 32bit KR

    Just now, I installed LabVIEW 2012 f3 (32-bit, English) and checked for the issue. But the font(NI7SEG) was not shown properly in VI either.
    - Both of Korea and English version of LabVIEW 2012 on Win 7 Korea OS shows wrong results. It is same on 64-bit OS.
    - LabVIEW 2010 but on same PC shows correct fonts.
    Is there a limit of number of fonts in LabVIEW? There are more than 100 fonts are shown in the "Selection Font" dialog and I can divide them into 3 groups by sequential order. I find that all fonts in the 3rd group are not applied correctly.
    (1st group)
    Arial Unicode MS...
    Bookshelf Symbol 3....
    Windings 3
    (2nd group)
    @Arial Unicode MS...
    @Terminal
    (3rd group)
    Arial...
    Consolas...
    Courier...  
    Licida Console... 
    NI7SEG...
    Verdana

Maybe you are looking for