Fixing a NXT LabVIEW Toolkit compile/load problem

I bought myself a Lego NXT Mindstorms to play with. I'm using the LabVIEW 8.5.1 from the FIRST Robotics competition and I downloaded the NXT Toolkit for Labview.
I did a mass compile on the toolkit (like the getting started said to) and did the excersize. I get the following error:
Error 1003 occured at Invoke node in NXT Toolkit.CompileOrCancel.vi->NXTToolkit.Target.Agent.vi
Possible Reasons:
LabVIEW: The VI is not executable... It said to do a file->open.
Method Name: Run VI
VI Path: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\NXTToolkit\gcomplier\Backend.LEGO\NXT.Compiler.Core.vi
The vi was broken but it had a password to open the view so I couldn't tell what was going on.
What do I do to fix this?
Thanks
"Lockheed" Joe
Testing Blog"

Hey Joe,
The Lego NXT Mindstorms and the LabVIEW Toolkit for the Mindstorms are officially supported by Lego's Technical Support. Check out this knowledgebase for a little more information regarding how to get the quickest support for your Mindstorms NXT issue.
Hope this helps,
Ben
Hope this helps.
-Ben
WaterlooLabs

Similar Messages

NI LabVIEW Toolkit for LEGO MINDSTORMS NXT

Labview 7.1.0と一緒に、タイトルのtool kitを使って、
LEGO MINDSTORMS　NXTを動かそうとしているのですが、
一括コンパイル、nxt tool kit 1.0.1 patchコピーを終え、
"Getting Started with the LabVIEW toolkit for LEGO MINDSTORMS NXT"（添付）
の最初の"Building a LabVIEW VI that Runs on the NXT"に従って、
作成したVIをNXT上で動かそうとしたのですが、
Debugボタンを押すと、コンパイル、ダウンロードまではうまくいくのですが、
ダウンロードされたプログラムがNXT上で動作せず、動かそうとすると、
NXT本体のディスプレイにFILE ERROR!と表示されます。
NXTのバージョンは、1.03で、
"LabVIEW Toolkit for LEGO® MINDSTORMS® NXT"を
一括コンパイルした際には、次のようなメッセージが表示されました。
#### Starting Mass Compile: 2008年7月2日 18:41:42
Directory: "C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons"
Failed to load (C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\NXTToolkit\shared\NXTToolkit.GetRelevantContexts_8_0.vi)
Failed to load (C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\NXTToolkit\shared\NXTToolkit.OpenVIRefInContext_8_0.vi)
Failed to load (C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\NXTToolkit\shared\NXTToolkit.RemoveScrollbars_8_0.vi)
#### Finished Mass Compile: 2008年7月2日 18:42:58
Labview 7.1では関係ないのかなと思っているのですが、関係あるでしょうか？
その他でも、不具合原因について、心当たりのある方がいらっしゃいましたら、
アドバイス頂ければ幸いです。
小松崎
添付:
LabVIEW_Toolkit_for_LMS_NXT_Getting_Started_Guide.pdf ‏201 KB

I do know of this one software where you can simulate the NXT, but it might only be for NXT-G programs.
SimplySim at The NXT Step
Other than that I don't think there's any way.
As for the difference between the two, there's a whole ton. Those are two different programs with very different syntaxes. Lego NXT-G is the basic software that comes with the NXT kit. It's a very scaled down version of LabVIEW and is pretty nice. LabVIEW is much more advanced and you can do much more with it, but you are restricted to using the LabVIEW NXT Toolkit and the NXT's cababilities. (no float, only so much RAM, etc.). But you can still do a ton more with it. Yes, you can data log with LabVIEW in, like, many ways.
Hope that helps!

LabVIEW Toolkit for LEGO MINDSTORMS NXT bugs

When you find bugs in the toolkit, post them to this message thread.
This board will be regularly monitored by both NI Application Engineers and members of the development team.
Thanks for helping us create a better toolkit going forward.
John Field
MINDSTORMS Software Group Manager
LabVIEW R&D

Hi John,
Problem: Unsupported case structure values in NXT Toolkit VIs.
I think the problem is, that the VIs of the NXT Toolkit do not follow the restrictions of the Programming Guide of the NXT Toolkit. The programming Guide says at page 6 (Structures, Case Structure) that
“Only one specific value (or "Default) is allowed in the case selector lable for each subdiagram."
But for example the "PortSemaphore.AccessSemaphores.vi", which is part of the NXT Toolkit (and which is a Sub VI of "NXT_SyncUnlimited.vi") uses a Case Structure with the values “0, Default”, “1”, and “2”. This is only one example. I found many VIs in the NXT Toolkit which are using case structures with more than one specific value or with a “0, Default” value.
Why does the NXT Toolkit include VIs whitch are not programmed according to the Programming Guide of the NXT Toolkit?
How can I solve the problem? Do I have to modify each NXT-Vi with incorrect case structure values?
I am using LabVIEW 7.1 and NXT Firmware 10.3.
Regards
Manfred

LabVIEW Toolkit for LEGO MINDSTORMS NXT in Windows Vista

Anybody knows how install LabVIEW Toolkit for LEGO MINDSTORMS NXT with Windows Vista?. Installing it gives me an error that says 'The windows installer is corrupt. To attempt to resolve the issue, please register the engine by running regsvr32.exe on msi.dll'. But it doesn´t work.
Thanks in advance

The work around for this issue is to install each of the MSI files setup.exe calls when running the installer. I was able to reproduce this issue for the 1.0 toolkit I was unable to do so for the 2.0 toolkit. This being said the instructions bellow are for those of you who are running into this issue with the 2.0 toolkit.
Listed bellow are the MSIs you will need to run (shown here at their default location after the self extracting EXE has been run). You should run these MSI in the following order.
C:\National Instruments Downloads\LabVIEW\7.1\LabVIEW NXT Toolkit\2.0\Products\MetaUninstaller\MU\MetaUninstaller.msi
C:\National Instruments Downloads\LabVIEW\7.1\LabVIEW NXT Toolkit\2.0\Products\MDFSupport\MDF\MDFSupport.msi
C:\National Instruments Downloads\LabVIEW\7.1\LabVIEW NXT Toolkit\2.0\Products\MDFSupport\MDF\EULADepot.msi
C:\National Instruments Downloads\LabVIEW\7.1\LabVIEW NXT Toolkit\2.0\Products\LVLEGONXTTK\LVLEGONXTTK\LVLEGONXTTK.msi
C:\National Instruments Downloads\LabVIEW\7.1\LabVIEW NXT Toolkit\2.0\Products\LVLEGONXTTK_LV71\LVLEGONXTTK_LV71\LVLEGONXTTK_LV71.msi
C:\National Instruments Downloads\LabVIEW\7.1\LabVIEW NXT Toolkit\2.0\Products\NXT_Driver64\LegoMindstormsNXTdriver64.msi
A similar procedure can be used to install the 1.0 toolkit if need be. You can get the install order from the parts from the [Parts] section of the setup.ini.
Mark
LabVIEW R&D

Teststand generates error ' labview has encountered a problem and needs to close'

Hi,
I am using Teststand 3.1 and Labview 7.1.
My problem is that I have a 1D array of 6 elements in Labview that I need to receive from Teststand.
If the array size is set to variable in Labview there is no problem but if I set it to what I require ( fixed 6 ) then when I specify module in Teststand an error message appears , ' LAbview.exe has encountered a problem and needs to close '. Then I get an 18001 about ActiveX as labview has closed.
Why does this happen ?, is it a bug ?

No bother its attached !
The vi writes to a global variable.
The 'Bytes To Send ' 1D array seems to be the trouble, If its set to fixed 6 in LV then Labview crashes from Teststand when I specify module.
If its set to variable its ok.
Attachments:
Global_Write.vi ‏26 KB

Fixing tags for classical and compilations

Hi. Does anyone know a way of tackling the following two tagging problems?
1) I'm finding that the tagging service that iTunes uses, Gracenote, to be pretty inconsistent when it comes to classical music. In some cases, it makes the artist, the movement and the composition, the track name, as in:
Name: String Quartet No. 5, Sz 102
Artist: 1. Allegro
In another case, it has labelled the track names of several (but not all) disks it a box set gibberish, as in:
Name: &}4ÍOò ,7j Øw¿ \Á59-1 éºâÕ¹ü,1}à
Artist: Amadeus Quartet
Album: String Quartets Vol.4
Since I subscribe to Match, I've tried both downloading mislabelled songs that are available in the iTunes store and asking iTunes to "Get Track Names". But neither solution has helped. I've also tried MusicBrainz Picard. But that's also really not very good with classical music. Short of doing it manually, which would take forever; is there another way of addressing this?
2) I've had iTunes tag some of my compilations in my preferred format, which simplifies browsing my catalogue by artist. It looks like this:
Artist: Various Artists or VA [album name]
Album: [album name]
Name: [artist] / [song name]
A good number of them, however, are tagged as if they were a non-compilation albums, eg.:
Artist: [artist name]
Album: [album name]
Name: [song name]
This means that each compilation adds a dozen or so artists, with one song each. This makes it a pain to browse by artist, especially in an iOS. For this reason, I'd like to have all compilations conform to the first format. But again, I haven't come up with a way of altering the tags in mass.
Any tips to address either of these issues would be greatly appreciated. Thanks in advance.

Hi,
Thanks for the respose. I realize that I need to settle on a pattern that I like and adopt it. My question, though, is about how to adopt and implement it. When it comes to arist and composer you can go at least change them manually album my album. But changing by every single track in an album to adress the problems that I describe would take forever. The same issue arises with fixing the tagging pattern of compilations.
I would imagine that there should be a way of customizing the manner in which services like itunes/Gracenote popolate the fields. But I haven't yet found a service that a) has an adequate classical music database and b) allows that kind of flexibility. Mediamonkey says that it does (I haven't tried it); but it's Windows only.

Why PI Acton Labview toolkit is not free but C++ SDK is free

Now i am using PI Acton Spectrapro 2300i.
and want to develop our software to control the system
but the company told us the C++ SDK is free
but the labview Toolkit is not free.
Why ,for i have owned the dlls about the system ,if i can call the dlls in the labview.So the labview should be also free.
Are three some problems when calling C++ in Labview,or need some driver when using Labview??
Thanks very much

You should ask the supplier about why they charge for the LabVIEW toolkit
and not for the C++ SDK.
Calling C++ dlls is not easy from LabVIEW, unless the functions are exported
as c functions. The C++ naming convention is something LabVIEW cannot
understand. A C++ dll doesn't automatically mean it uses a C++ naming
convention, so you'll have to check. Open the dll in a call library node and
see if the names you'd expect are there. If they are available, and you
don't see strange signs like _, *, &, # or @ in the names, it's probably
easy to call from LabVIEW.
One way to deal with this is to make a C/C++ wrapper that does use C naming
so LabVIEW can understand it, but you can't do that in LabVIEW.
Regards,
Wiebe.

Adobe Captivate 8 projects published to HTML 5 shows major loading problems and stops

Adobe Captivate 8 projects published to HTML 5 cause major loading problems in most browsers(IE 11, Chrome v. 35.0, Firefox v. 31). Loading… (screen)
The view stops after a while and only the Loading… (icon) can be seen on the page.
Is this a known problem with Captivate projects published to html5 and is there a way to fix it? What is wrong?
Test the html5 version of this project at: http://kurs.dokker.no/captivate/
and see for yourself what happends.

I changed the Preferences/Project/Start and End Preloader % to 25 and published the projects again. The course: http://kurs.dokker.no/captivate/elev/
stopped like before on one of the first slides, loading… screen like before in IE11.
In Chrome v. 37.0 the course worked badly, would not run, sound missing and buttons not working.
In Firefox 31.0 the course worked to a degree even if the program was advising to use another browser for this content.
In Opera 23.0 sound was missing and else working as bad as IE.
All this testes is done on a PC using Windows 8 connected på internet via ethernet, download speed: 66.57.
I would like to use the HTML5-format since it has a cleaner view than swf-files that appear to be jagged, but there is a lot missing before Adobe Captivates html5 publish is where it needs to be. Her are the complete html5 course and here are the swf based course for comparison.

LabVIEW Compare Tool load time of files from repository

I have the LabVIEW compare tool setup for differences for .ctl and .vi files in Surround SCM source code control system. The source code control system runs on a networked server. My PC is on the same network as the server.
When the LabVIEW compare tool reads VIs that are from a source control repository for diffing against files on my computer, it seems to load the repository files from a temporary folder located in users\username\appdata. It takes a long time to load VIs that have lots of subVIs because as the tool searches for each subVI the tool begins its search in the vi.lib and instr.lib folders before finding the subVI in the temporary folder. It is taking a few seconds and sometimes as much as 10 seconds to load each subVI. This takes a lot of time to Diff VIs that have many subVIs. Is there a way to make the diffing process go quicker? Or is this something that would need to be fixed in the LabVIEW compare tool?
Thanks,
Gary
Solved!
Go to Solution.

That's the normal behavior of the LVCompare.exe, and the folders at which starts looking for subVIs or control files (.ctl) cannot be modified. The available options that can be configured are the following:
Configuring Source Control with LVCompare.exe
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configlvcomp_thirdparty/

Labview slider event handling problems - revisited

This topic asked a question that was very close to a problem I am having:
Labview slider event handling problems
That is, how do I, using an event structure and/or other means, only read out the value of a slider control after the value change is finalized?
The extra constraint I'd like to place on this, which I believe will invalidate the answer given in the thread above, is that my slider control also has a digital display which can also be used to change the value without ever using the mouse. I cannot look for a value change followed by a mouse-up event if the mouse was not used to change the value.
Any ideas how this might be accomplished? FWIW, I am using LabVIEW 7.0

Each and every incremental value-change event generated by the movement of the slider is still detected and queued up for use by the event structure and the event structure loop wades through them all before it's done.
I have come up the attached "fix" (LV v7.0) for this problem. While it is not as clean a solution as I had hoped it would be, it's the best I can manage given what LabVIEW offers me to work with and it does work in the situation where I need to use it.
Now, within the Finalize Slider Events subVI, I'm keeping track of the most-recent values seen by the subVI, checking to see if they have changed, and reporting out that fact. That gives me a Changed/Not-Changed bit within the event case that I can use to control what code then gets executed. If the event case is just playing catch-up to the real value of the control, I can now see that fact and ignore it.
In this version I've also dumped the variant output and limited the VI to using DBL values. I decided it added complication to something that was too complicated already and I wanted the output terminals for other purposes anyway (reporting of the correct "OldVal" of the control).Message Edited by Warren Massey on 04-28-2005 03:56 AM
Attachments:
slider_events[5].llb ‏77 KB

Run exe constructed in labview 6i without loaded nidaq drivers.

Exe is constructed using labview 6i. It would be convenient to install the exe and run time engine on the HDD,
and execute as a demonstration program, without loading the nidaq drivers.
No daq card in pc, nidaq would be on CD. Suggestions are appreciated.

If you want to run an exe without loading DAQ drivers, you will need to ensure that no DAQ calls are statically linked in the final executable. As waldemar.hersacher mentioned, you can do this by using VI server for all your DAQ calls, then calling stub routines if you are using the laptop for demo purposes. It would probably be easiest to put all your DAQ calls into a few subVIs and call those dynamically instead of each individual DAQ VI call. If you miss one, your launch will fail when DAQ is not present (you will get the standard LabVIEW searching for subVIs dialog and then a message telling you that you need the full version of LabVIEW to correct the problem).
There are lots of ways to switch between the "demo" mode and the "live" mode. A dialog which pops up on startup and is accessible from the menus is the most obvious.
Good luck. If you need more hints, let us know.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Mail loading problem

Hi all
I've got this mail loading problem,
whenever the mail is loading I always scroll down to read the text first
but it always to back to the top, I scroll down again it scroll back up.
this happen only during the images are loading.
it is very annoying, though it might be fix in 10.5.7
but it was not.
any plan to solve this?

I have the same problem. Did you get any answers?

Macbook Pro/Mozilla Firefox --Page Loading Problems

I experience 'page loading' problems when going from one page to another. Sometimes the page takes a long time to load. Sometimes it times out and never does load.
Does anyone else with this combination of laptop and browser experience these problems? Any suggestions for overcoming this lag?

I know OS X used to have some problems with the way some routers do DNS. There was this topic a while ago:
http://forums.verizon.com/t5/FiOS-Internet/DL-page-load-speed-great-but-browser-quot-looking-up-quot...
For our Mac we had to set the router to send external IP addresses of a DNS system (either verizon's or something like OpenDNS which we use).
You could manually change the DNS settings on the Mac to see if that fixes the problem and then you could mac the change the settings at the router level if you like.

Partial page load problem when using Muse in an existing non-Muse Masterpage; how to issue a jquery

Partial page load problem when using Muse in an existing non-Muse Masterpage; how to issue a jquery args.get_isPartialLoad().
My page is loaded into a palcehold within the Ajax update panel within the current Masterpage, so page loadload doesn't occur. But if my Muse page can capture the partial pageload then I can tell jquery to run the Muse formating routine.

Jackie, I am having the same issue and agree that it obscures our site analytics.
I only have the "WebMarketing" subscription - so I cannot see how often people visit my site (unless I just dont know how to view that). Here is a screen shot of how many different locations I have and how much it affects my site visitor count based on the other locations which seem "legit" because they have more page views than visits.
I hope there is a way to fix or block this.

FLIR sc655 and ThermoVision Labview Toolkit

Hello,
I am having trouble with the FLIR Labview toolkit. I cannot seem to get even thier basic examples to work. I have Windows 7, Labview 11, Thermovision toolkit 3.3.7 (latest version on FLIR website). The error occurs in "ThermoVision open.vi". the error code is -1 which labview says is unknown. Looking deeper the error appears to occur in the sub-vi "ThermoVision CreateActiveXRefnum.vi".
As far as the camera itself I am connected through GigE port. I see the IP address just fine in IP config and I can acquire images in both IR monitor and NI MAX just fine. Something is going wrong it seems wit hte active X control through labview. The ThermoVision SDK runtime is installed which has the active X program so I have no clue what is going on or why I cannot use the FLIR tools to connect to the camera.
Has anyone had thier problem and/or have any insight as to what is wrong?
Thanks

Greetings;
While I have not used the ThermoVision toolkit, I have taken a quick look at their manual and have a few questions; would you happen to know if the toolkit's version is compatible with that version of LabVIEW? In addition, is there any order requirement for the installation as well as any driver that is required other than Vision Acquisition?
I have done a bit of research and come across a few topics in our forum that also deal with this particular toolkit; the last link has been particularly longstanding and a user seems to have worked with it extensively:
http://forums.ni.com/t5/Machine-Vision/FLIR-A320-infrared-camera-Labview-Developer-Kit-feedback/td-p...
http://forums.ni.com/t5/Machine-Vision/How-to-build-an-application-in-LabVIEW-10-including-FLIR/td-p...
Ultimately, since NI-MAX works correctly, would it be possible to test the camera in LabVIEW without using the toolkit's VIs? The camera seems to be fully GigE Compliant which means that you should be able to reach it with IMAQdx VIs. If the camera does indeed work in LabVIEW correctly, it might be worhtwhile to reach to the developpers of the Toolkit to see if they have any insight on the matter.
Cordially;
Simon P.
National Instruments
Applications Engineer

Fixing a NXT LabVIEW Toolkit compile/load problem

Similar Messages

Maybe you are looking for