Mellroth

QUOTE(crelf @ Jun 11 2007, 05:01 PM) Welcome back to the 5:th dimension crelf, or did you remove the RSS filter by mistake QUOTE(PaulG. @ Jun 11 2007, 05:07 PM) Whiskey-Tango-Foxtrot? I agree, but currently I'll stick with Whisky, maybe I can understand this thread if I get enough... /J

QUOTE(philm @ Jun 7 2007, 09:54 AM) The property "value" is not affected by zooming/panning, it contains the data used to draw the graph. If you only want to export the portion of the graph currently visible, you will have to filter the "value" data using the properties "XScale.Range" and "YScale.Range" to get the X- and Y- range to export. /J

QUOTE(Gavin Burnell @ May 30 2007, 10:22 PM) If I remember correctly, LabVIEW (<5.0) used different representations for scalars and arrays. A boolean array was stored with each boolean as a bit, but boolean scalars were stored as I16 (U16?) values. /J

QUOTE(Gary Rubin @ May 31 2007, 02:45 PM) This has been on my wish list for a very long time (added on NI wish list). I would also like to see array functions to copy values between arrays in one call, i.e. without using loops and without the need to first get the values then set the values. E.g. copy indices 1,3,9 from array-1 to indices 2,8,12 in array-2 directly. /J

QUOTE(jpdrolet @ May 30 2007, 02:20 PM) :thumbup:

QUOTE(alfa @ May 30 2007, 09:08 AM) Don't expect anyone to take that as a proof of that you are creating God A bit like the story: There was an old man driving alone down the highway when he got a call from his wife on his cellphone . "Henry!", she said. "You better be careful. I just saw on the news someone on that road recklessly driving the wrong way!" Henry looked out his window and said" I think there was something wrong with that report, Martha. It's not one car. It's all of them!" /J

QUOTE(Thang Nguyen @ May 24 2007, 07:24 PM) Hi, when you say ethernet, do you mean you can't connect with VI-Server or TCP/IP or...? If you are using VI-Server, you might want to check that the application is using the correct VI-server port and that access is enabled. Check the application ini-file, so that you have the TCP server enabled: server.tcp.enabled=True for other options, have a look at the Wiki: http://wiki.lavag.org/index.php/LabVIEW_configuration_file.VI_Server' target="_blank">http://wiki.lavag.org/index.php/LabVIEW_co..._file.VI_Server /J

QUOTE(Phil Duncan @ May 24 2007, 10:35 AM) You're welcome. Would you mind uploading the version using the annotations, to help others facing the same problem? /J

QUOTE(Phil Duncan @ May 23 2007, 02:39 AM) Phil, maybe this is a long shot, but have you tried using annotations to programmatically set the labels? This way the "labels" would be part of the plot itself. /J

QUOTE(BrokenArrow @ Apr 29 2007, 03:45 PM) Blubb,Bllbllb /J

QUOTE(Bernd F @ May 11 2007, 09:42 AM) After this crash, do you still have a the build arrays nodes set to different modes? If you do, could you please upload this VI (or relevant part of it), so we can understand what is happening. You don't have to upload the complete VI (if you don't want to), select the code in the picture and choose "create SubVI" from the menus. Uploading this subVI, should be enough to show us what is going on. /J

QUOTE(Eugen Graf @ May 11 2007, 10:17 AM) Like Michael said, there is no such thing as global constants, but you can mimic this by creating VI for a system (global) constant. In this VI put the system constants on the BD, then wire them to the indicators. To access the "constant" values, just call the VI as usual, using the outputs as your constant values. Or you can just use a FunctionalGlobal to store your global values. /J

QUOTE(Bernd F @ May 10 2007, 05:02 PM) As other pointed out, the type of the indicator seems to be unspecified. I also noticed that the build array node before the loop is set to concatenate, but the build array node after the loop, is not. I'm not even sure I understand how it cannot be set to concatenate, if you have elements of two different dimensions (I don't have LabVIEW available now so I can't check). /J

QUOTE(LV Punk @ May 10 2007, 01:30 PM) Sounds like a really good idea :thumbup: As you said, it is sometimes enough to show an icon to the user, to get them on the right track. By using these emoticons, we would also save disk on the LAVA servers. I don't know if it is possible to add an extra "emoticon" menu to the post editor, but if it is, this menu could hold all these small LabVIEW "pictures". /J

QUOTE(Eugen Graf @ May 10 2007, 11:13 AM) Looks good Eugen, you can, however, skip the "Get Date/Time in seconds" function, since the "Seconds To Date/Time" defaults to current time. Maybe you should also set the UTC boolean inputs? /J

QUOTE(Eugen Graf @ May 9 2007, 06:58 PM) You don't have to split the string by hand, you can: 1. use the format string "%.;%02d%02d%02d%f" to get all values in one scan, then either calculate # of seconds, or use the "Date/Time to seconds". 2. Convert the string to DBL, then divide by 10000, use quotient and remainder etc... then either calculate # of seconds, or use the "Date/Time to seconds". 3. ? /J

QUOTE(Eugen Graf @ May 9 2007, 06:48 PM) I'm sorry I didn't realize you were on LV8.01, in LV8.2 this issue seems to be resolved (except in that %3u does not work with comma). How do you want the string "155529.00" to be interpreted, as 15:55:29.00? /J

I don't think the original code and the workaround produces the same result. According to the probe in the picture, the input string is "155529.00". The workaround converts the string to a DBL value, i.e. 155529.00, and then to a Timestamp equal to "1904-01-02, 20:07:39.000", i.e. the value contained in the string is interpreted as seconds since "12:00 a.m., Friday, January 1, 1904, Universal Time" The original code, where you used the format string "%.;%<%H:%M:%S%3u>T", indicating that you expect the string to be parsed as 15:55:29.000 which is completely different from the result of the workaround. The solution therefore depends on what kind of time value you have in the input string: If you want it to be interpreted as 15:55:29.000, use the format string "%.;%<%H%M%S%3u>T", i.e. remove the colons (there might still be an issue with the localization). If you want it to be interpreted as seconds, use your workaround or use "%.;%t" as format string and convert to TimeStamp afterwards. Hope this make sense. /J

QUOTE(alnaimi @ May 9 2007, 03:38 PM) Hi alnaimi, I think you have wired the arrays into the bundle nodes in the wrong order. The upper terminal of the bundle node is the x-axis, and the lower is the y-axis. Enable context help, and put the mouse cursor on the graph terminal to get information about how to input data to the graph. Some comments 1. its generally a good idea to make all code visible on the screen, maybe your resolution is above mine, but there is very much free space in your diagram. Keeping the diagram smaller makes it much more easy to debug and/or understand. 2. try to keep wires from left to right, increases readability and makes debugging easier 3. try to keep wires straight, i.e. with less bends (increases readability) 4. try to avoid crossing of wires as much as possible, increases readability 5. do you really have to update VGS in every loop iteration, it seems like this could be done before you enter the loop? Good luck /J

QUOTE(Aristos Queue @ May 7 2007, 05:58 PM) My expression was that the original list described why a open VI suddenly needed recompilation, then it made sense to add the conditional disable symbol only. You are right that if the goal is to describe any reason for a VI to need recompilation, these three new entires could be added. /J

QUOTE(John Rouse @ May 7 2007, 04:09 PM) Hi John, have you checked the print properties? There is a drop-down menu that allows you to select if only connected controls should be printed (see picture below). http://forums.lavag.org/index.php?act=attach&type=post&id=5751''>http://forums.lavag.org/index.php?act=attach&type=post&id=5751'>http://forums.lavag.org/index.php?act=attach&type=post&id=5751 /J

QUOTE(BrokenArrow @ May 7 2007, 03:09 PM) Whoops, sounds like a lot of fun It might be possible to open up all VIs, then save the Serial Port Write.vi under a different name (e.g. mySerialWrite.vi), and finally re-save all VIs that linked to the Serial Port Write.vi (not the VIs in vi.lib though ) Then you could replace the internals of the mySerialWrite as you want. I don't know if this would solve your issues, but at least you would have more control. /J

QUOTE(Val Brown @ May 7 2007, 12:29 PM) Hi, LV Punk is correct in that the easiest way to do this is to simply enter a smaller value to the right. You can also open up the properties dialog for the slider, and mark the scale as inverted (the result is the same) http://forums.lavag.org/index.php?act=attach&type=post&id=5749''>http://forums.lavag.org/index.php?act=attach&type=post&id=5749'>http://forums.lavag.org/index.php?act=attach&type=post&id=5749 /J

QUOTE(Aristos Queue @ May 5 2007, 07:44 PM) This is probably more or less covered in your first point, but I think it is worth a separate entry. * a "conditional disable" structure in a VI will cause recompile, if the active selection symbol changes. E.g. using the TARGET_TYPE symbol in a VI that is used in more than one target. Opening the VI (or building applications containing the VI), will then indicate changes of the VI if it was not saved for the specific target. /J

Hello philm, I think you can use the VI (MultiColumnSort.vi) I uploaded to this thread MultiColumnSort to perform the sort operation that you need. This VI can sort a 2D string array in any column order. Hope you can use it. /J