Mellroth

QUOTE(jaec @ Apr 5 2007, 09:30 PM) I think you are in the wrong forum /J

QUOTE(crelf @ Apr 5 2007, 06:03 PM) NULL terminated post /J

QUOTE(Tomi Maila @ Apr 5 2007, 04:48 PM) Tomi, I think you are safe If I remember correctly, bsvingen did some testing of this in another thread (that I can not currently find). The result, as I recall them, was that the LV2 global was faster than using queues. /J

When unflattening a string that is wired to a shiftregister, the remaining string output (from unflatten function) might contain garbage when it leaves the loop. The result of the operation depends of the size of the remaining string, small strings are OK, but large strings contains garbage. To test this: flatten a cluster containing a boolean and a numeric, then add some additional data (U8-array converted to string). The combined string is then fed to an Unflatten function within a while loop (only running one iteration). Unflattening is done in two ways, one where the string is passed through a shift register, and one where data is passed through a loop tunnel. In the case of a loop tunnel, the remaining string and the resulting U8-array is OK, but with the shiftregister, data in the U8 array is corrupted. To summarize; when using large strings the remaining string output is OK within the loop, but right after the loop it has changed. See attached VI for details. http://forums.lavag.org/index.php?act=attach&type=post&id=5413 This has been reported to NI, but I have not gotten a CAR for this one yet. /J http://forums.lavag.org/index.php?act=attach&type=post&id=5412

QUOTE(spacetoon34 @ Apr 5 2007, 05:08 AM) Hi, as Mikkel said, check that other thread for answers. The VI you supplied won't work in any LabVIEW environment, due to that you are trying to Wait 0.1 ms. The DBL value (generated from 1/10000), is coerced to a U32 value and is interpreted as 0 (zero), so the wait for next multiple waits for 0 ms. /J

QUOTE(superslug @ Apr 4 2007, 07:38 AM) Hi, As REM1 is saying you should probably use a Chart instead of a Graph. However, I don't think that this is your problem, because you say that data "disappears until the next update". If the graph goes blank you are probably getting false updates, meaning that you either update the graph or the shared variable with invalid data. Regarding settings, it is very hard to say anything without looking at your code. /J

QUOTE(karim @ Apr 3 2007, 01:10 PM) Have you tried googling for "LabVIEW parallel port"? If not please try the link below: http://www.google.com/search?q=LabVIEW+parallel+port&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:sv-SE:official&client=firefox-a' target="_blank">http://www.google.com/search?q=LabVIEW+par...lient=firefox-a I doubt you get any member to email you with an answer, since this would expose the members email address. Give google a shot, then try to do your assignment. If you still have questions about why your program does not work, please post your VI and the question in this thread. Maybe someone will then help you. The more effort you show, the higher the chance of help. Sincerely /J

QUOTE(Jim Kring @ Apr 3 2007, 09:31 AM) Looking forward to this blog. :thumbup: /J

QUOTE(crelf @ Apr 2 2007, 09:39 PM) hope that this is not taken literally /J

QUOTE(Eugen Graf @ Apr 2 2007, 11:40 AM) Use the break point tool from the Tools-Palette. When the break point tool is black, it will add a breakpoint, when it is white it will remove a previously added breakpoint. In your case use the tool and click within the loop. /J

I almost always use the WHILE loop in my LV2 globals, but sometimes I've used the FOR loop approach below to store data. http://forums.lavag.org/index.php?act=attach&type=post&id=5367 http://forums.lavag.org/index.php?act=attach&type=post&id=5368 /J

QUOTE(i2dx @ Mar 25 2007, 09:47 AM) Thanks for the reminder :thumbup: , as you said it is really good to have when evaluating beta versions. /J

QUOTE(Mike Ashe @ Mar 24 2007, 06:08 PM) I'm on my 4:th ... /J

QUOTE(Nullllll @ Mar 24 2007, 04:06 PM) ... spooky makes you wonder... /J

QUOTE(Nullllll @ Mar 24 2007, 03:53 PM) Please Nullllll, put some effort in trying to make the VI first, then ask questions why it does not work. Apart from proving that you have actually tried something, it is often easier for us to get what you intend to do, if you include an example. That said, create a subVI that acts as a dialog with the inputs you need, just display and use that dialog where you need it, this sub VI can then output any data type you need. Simple questions that can be answered by selecting a buttons (like OK, No, Yes, Cancel), can be implemented with the LabVIEW dialog VIs. /J

I read Chris post, and realized that I was a bit unclear in my previous post, thanks for the clarification Chris :thumbup: . I was trying to examplify that you could get the error 1003 ,when trying to call a dynamic VIs without a proper development distribution, i.e without necessary supportfiles. QUOTE(chrisdavis @ Mar 22 2007, 01:49 PM) You don't have to use an LLB, it will work by selecting single destination in the Distibution settings as well. If the dynamic VIs calls a DLL or any other external files this might be a better (the only?) option IMHO. If the dynamic VI uses any functional global to share data with the main application, be careful with the "name mangeling". /J

QUOTE(BenD @ Mar 22 2007, 12:14 PM) Have you tried making a developer distribution of the VI you want to call dynamically? I've seen error 1003 when the dynamic VI hierarchy contains VI.lib/user.lib files not compiled to the exe, e.g. if the exe does not contain any timed loops, but the dynamic hierarchy do. /J

QUOTE(Aristos Queue @ Mar 20 2007, 02:45 AM) The dark side... I have spoken to NI about this issue several times. It seems like almost all the Pt by Pt functions uses the build array until the buffer is filled, then they switch to a mode where data is rotated at each call, making them more or less useless in an RT environment. /J

QUOTE(Mike Ashe @ Mar 15 2007, 01:21 PM) "Always look at the bright side of life..." /J

QUOTE(frentzen @ Mar 14 2007, 12:28 PM) I tried your VI, and it gave an error (you should really check the error outputs) stating that temproot was NULL. To make your VI run without this error, I had to fix the file name from "Mean[1].20061013_123043.xml" to "Mean.20061013_123043.xml". Hope this helps. /J

QUOTE(thomas2609 @ Mar 13 2007, 11:26 AM) Have you tried with comma (,) instead of period (.) as decimal character? /J

QUOTE(ruelvt @ Mar 11 2007, 04:32 AM) Hi, To get more help, could you please specify; * cRIO model? (the IP performance is really boosted in cRIO 9012, mainly due to change of chipset) * LabVIEW version? * It would also be easier to help you, if you could upload an example to show what you have tried so far. We have, however, used cRIO 9012 units to act as distibuted I/O. In this case the cRIO units received user commands through UDP, and also used UDP to synchronize Data buffers with the Master RT target. If no data was received (UDP timeout set to 1000ms), the load of the cRIO was around 5%, and when doing performance measurements (i.e. sending commands that were just looped back), the processor load was about 40-50%. I haven't really checked the memory usage, but what I have seen is that about 50% of the available memory is allready taken by the OS, leaving us with around 30MB for our applications. Another issue we have encountered in the cRIO systems is that using Queues/RT-FIFOs/Notifiers/LV2-globals to transfer data between processes, takes in average 270us for a transfer to complete, i.e. time from adding data until it is read by the receiver. This is probably not relevant for your current problem, but it might be good to have that in mind when you are using a cRIO. /J

QUOTE(Hoeloeloe @ Mar 8 2007, 02:51 PM) Without any actual knowledge of your code, it sounds as if you are sampling in the same VI that graphs the data? If this is the case, it means that your data acquisition is taking place in the same thread as the UI, and is therefore affected by events like the Mouse clicks/window dragging etc. To speed up your acquisition you could put the data acquisition loop in a SubVI (possibly setting this subVI to use another thread), then post data from the data acquistion loop to the UI loop using a queue. Have a look at the Producer/Consumer design pattern at NI http://zone.ni.com/devzone/cda/tut/p/id/3023''>http://zone.ni.com/devzone/cda/tut/p/id/3023' target="_blank">http://zone.ni.com/devzone/cda/tut/p/id/3023 To get more info, I think you'll have to post an example VI, so that we can see what you are trying to achieve. /J

QUOTE(tcplomp @ Mar 7 2007, 02:09 PM) :thumbup: /J

QUOTE(Eugen Graf @ Mar 5 2007, 01:11 PM) Start edit the palette ( menu Tools->Advanced->Edit Palettes... ) Add VI(s) to the palette by right-clicking on the area where you want them (Insert -> VI(s)...) When a VI has been added, right click on the ICON and select Merge VI http://forums.lavag.org/index.php?act=attach&type=post&id=5126''>http://forums.lavag.org/index.php?act=attach&type=post&id=5126'>http://forums.lavag.org/index.php?act=attach&type=post&id=5126 Save your palette. Next time you select this VI from the palette, it will insert a piece of code on your BD and controls/indicators to your FP. /J