Jump to content

Bobillier

Members
  • Posts

    222
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Bobillier

  1. Hi all Today i have find two bug (i think) with typedef controls. Ring 1) I create ring typedef with one value. I place it in my diagram and that create one constant (here all is normal) 2) I modify typeDef and add one another value in first position, and place it to diagram. Althoughthe they are synchronize, the new value don't appear in first constant and more bad, they can return same numeric value for differents values. ComboBox 1) I create combobox typedef with two values. I place it in my diagram and that create one constant (here all is normal) 2) I modify typeDef and add one another value in first position, and place it to diagram. Althoughthe they are synchronize, the new value don't appear in first constant . I know you can use find (Ctrl-F) and replace with source typedef to obtein correct values .But in case of combobox, this action all cste are size compress (another bug?). Eric ComboboxDeftype.ctl Constant DefType Bug.vi Deftype Ring.ctl
  2. True, but there is one interesting upgrade (in VIPM package) since Elijah Kerry blog (2 Fev 2011).
  3. I have found one really interesting link about error management. http://zone.ni.com/d...a/epd/p/id/6253 Eric
  4. You can find solution here http://lavag.org/top...__fromsearch__1 Look SelectionColorExample.vi at the end. Eric Oups too speed reply. in fact this example modify cluster and not array...
  5. Hi I need to create program on Mac to communicate to serial device. This device use extended ascii code (0-255). I know that the first 128 characters are same between Ascii Mac and Windows. But different for next 128 characters. Do know how convert them to be compatible between Ascii Mac and Windows? (Mac OSX and Labview 2009SP1) Regards Eric
  6. Hi Gavin I want propose you one small vi for your library. This Vi return the ConPane index on one control (connect to ConPane) if find. Perhapse you can add it to your library. Regards Eric Find Control Index in ConPane.vi
  7. Hi Ton Happy to see that you allways want feathers about State Editor. I have a problem with your request. If you generate one combo box , you can't modify it another time ussing State editor. Or i need to detect-it and and convert it to string constant. In which case are you ussing this kind of Combo (debug,...) Are you sure it's very usefull. Eric
  8. Hi I find a strang thing when i have upgrade one old Vi (s)version (7.0) to 9.0. When i open Vi(s) in LV2009 all seem OK (no break arrow) but when i run it, the vi don't do correct result. After few investigations, i have find the bug. It's arround "write to text file" Vi . When i look on help, i see that Vi is unsupport in LV2009.But don't generate error My question is: is there a way to automaticaly detect unsupport Vi , when i upgrade project. Eric
  9. Good idea to modify the background cluster color. Thanks
  10. Hi Is there a way to modify the native array selection color ? I have try with property node and look in Labview.ini file if there is parameter , but without succes.
  11. Yes it's near netsh commands, but difficult to parse because langage and perhapse os sensitive.
  12. Hi Is there simple way to get tcp/ip parameters (IP,Mask, DNS,WINS) ? I have try with netsh cmd, but it's a bit confuse for me. Eric
  13. Hi Ton Happy New year It's not a bug. When i look your video, you made UNDO and not delete action. For delete , you must select state and press del buttons (or use del in the right click menu). Cheers Eric
  14. After search in Labjack documentation i have find this : " 4.1.2 Multi-Threaded Operation This driver is completely thread safe. With some very minor exceptions, all these functions can be called from multiple threads at the same time and the driver will keep everything straight. Because of this Add, Go, and Get must be called from the same thread for a particular set of requests/results. Internally the list of requests and results are split by thread. This allows multiple threads to be used to make requests without accidentally getting data from one thread into another. If requests are added, and then results return LJE_NO_DATA_AVAILABLE or a similar error, chances are the requests and results are in different threads. The driver tracks which thread a request is made in by the thread ID. If a thread is killed and then a new one is created, it is possible for the new thread to have the same ID. Its not really a problem if Add is called first, but if Get is called on a new thread results could be returned from the thread that already ended. As mentioned, the list of requests and results is kept on a thread-by-thread basis. Since the driver cannot tell when a thread has ended, the results are kept in memory for that thread regardless. This is not a problem in general as the driver will clean it all up when unloaded. When it can be a problem is in situations where threads are created and destroyed continuously. This will result in the slow consumption of memory as requests on old threads are left behind. Since each request only uses 44 bytes, and as mentioned the ID's will eventually get recycled, it will not be a huge memory loss. In general, even without this issue, it is strongly recommended to not create and destroy a lot of threads. It is terribly slow and inefficient. Use thread pools and other techniques to keep new thread creation to a minimum. That is what is done internally. The one big exception to the thread safety of this driver is in the use of the Windows TerminateThread() function. As is warned in the MSDN documentation, using TerminateThread() will kill the thread without releasing any resources, and more importantly, releasing any synchronization objects. If TerminateThread() is used on a thread that is currently in the middle of a call to this driver, more than likely a synchronization object will be left open on the particular device and access to the device will be impossible until the application is restarted. On some devices, it can be worse. On devices that have interprocess synchronization, such as the U12, calling TerminateThread() may kill all access to the device through this driver no matter which process is using it and even if the application is restarted. Avoid using TerminateThread()! All device calls have a timeout, which defaults to 1 second, but can be changed. Make sure to wait at least as long as the timeout for the driver to finish. " Can you agree that i can modify UI tread option to Any thread option.?
  15. Thanks all I call Labjack support to know if their driver is "thread safe". Good week-end Eric
  16. Hi I try to write a software using Labjack library ( http://labjack.com/support/ud/examples/labview ). This library made dll calling. When i look the call library function node configuration, i see than the calling is on "Run in UI thread" and not "Run in any thread". Can you explain me the difference between "Run in UI thread" and "Run in any thread". Who is best when i made few calling in same time and speedily. I try to work with 5 Labjack U9E in same time. Actually when run my software, it take 50% CPU time. Eric
  17. Is there a way to use LVcompare with Labview Full Developement System ? I have try to use it with tortoise , but get below error (sorry in french). "Une erreur est survenue lors de l'exécution de LVCompare. Nœud de méthode dans LVCompare.vi <APPEND> Nom de la méthode : <b>User Interaction:Compare VIs</b>" Eric
  18. Hi is there somebody so friendly to convert this 8.0 library in 7.1 ? regards Eric Dossier Test com Millenium3.zip
  19. Have a look here http://zone.ni.com/devzone/cda/tut/p/id/11784
  20. Version 1.1.0 LV8.5

    793 downloads

    Convert_to v1.1.0 LV8.5 Copyright © 2010, BOBILLIER ERIC All rights reserved. Author: BOBILLIER ERIC LAVA Name: BOBILLIER ERIC Contact Info: Contact via PM on lavag.org LabVIEW Versions: 8.5 Dependencies: Nones Description: This tool is a right click framework plug_in. it's use to convert one or few elements ( control or constant) in one cluster. You can convert one element ( control or constant) in array. (if this element is one array, then add one dimension). You can convert too one array or cluster in this element(s). And that without moving anythings. Installation and instructions: This tool is package in .ogpb file. Please use VIPM for installation. Examples of use: http://www.screencast.com/t/NTk4MzY0Y Known Issues: Acknowledgements: To Dan_K for the start idea (http://decibel.ni.co.../docs/DOC-10621) Version History: v1.0.0: Initial release of the code. v1.1.0: Terminal and constant are correctly place in structures if need. License: Copyright © 2010, Eric BOBILLIER All rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the INRA. 4. Neither the name of the INRA nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY Eric BOBILLIER ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL Eric BOBILLIER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Support: If you have any problems with this code or want to suggest features: please go to lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the "Convert-to" support page. Distribution: This code was downloaded from the LAVA Code Repository found at lavag.org
  21. Name: Convert-To Submitter: Bobillier Submitted: 16 Sep 2010 File Updated: 15 Jun 2011 Category: JKI Right-Click Framework Plugins LabVIEW Version: 8.5 License Type: BSD (Most common) Convert_to v1.1.0 LV8.5 Copyright © 2010, BOBILLIER ERIC All rights reserved. Author: BOBILLIER ERIC LAVA Name: BOBILLIER ERIC Contact Info: Contact via PM on lavag.org LabVIEW Versions: 8.5 Dependencies: Nones Description: This tool is a right click framework plug_in. it's use to convert one or few elements ( control or constant) in one cluster. You can convert one element ( control or constant) in array. (if this element is one array, then add one dimension). You can convert too one array or cluster in this element(s). And that without moving anythings. Installation and instructions: This tool is package in .ogpb file. Please use VIPM for installation. Examples of use: http://www.screencast.com/t/NTk4MzY0Y Known Issues: Acknowledgements: To Dan_K for the start idea (http://decibel.ni.co.../docs/DOC-10621) Version History: v1.0.0: Initial release of the code. v1.1.0: Terminal and constant are correctly place in structures if need. License: Copyright © 2010, Eric BOBILLIER All rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the INRA. 4. Neither the name of the INRA nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY Eric BOBILLIER ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL Eric BOBILLIER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Support: If you have any problems with this code or want to suggest features: please go to lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the "Convert-to" support page. Distribution: This code was downloaded from the LAVA Code Repository found at lavag.org Click here to download this file
  22. Yes, i'm agree . But in my program, i want to run few vi dynamicaly. In normal case, all those vi's are stop cleanly. But in case of the main program crash, i want use this function to be sure that all those vi are stop. Eric
  23. Hi I want to know if this vi ,stop the labview run time engine. Eric
  24. Nice It's work for me too. and i upgrade my plugIn on JKI Forum Cheers Eric
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.