Jump to content

lraynal

Members
  • Posts

    68
  • Joined

  • Last visited

Everything posted by lraynal

  1. Looks like you want to use hexadecimal number ? Then you need to configure your numeric to accept HEX. For this, change your numeric to Integer (rather that Double...) U8 for example, then right click on the Numeric control and select "Visible Items" -> "Radix". A little 'd' will appear near the number. Click on it and select "Hex" (a little 'h' will apear). Then you will be able to enter number from 0 to F... (You can go to the control property to change the Range or anything else... right click on the control, then Properties...) Laurent http://forums.lavag.org/index.php?act=attach&type=post&id=5301
  2. QUOTE(Mikkel @ Mar 26 2007, 02:38 PM) You even can try: "..51" and "52.." You should read LabVIEW help, and especially the topic: "Creating Case Structures". There's plenty of information for "silly" questions!!!!
  3. It's pretty hard to answer you, as you pointed out the problem on the "numeric - value change - event structure". An event is generated everytime you modify the numeric... so as many event as modification... Depending on the king of program you are doing, you can use or not use this kind of event... personnaly, I use it sometimes, but not always because of this particular problem you pointed out! What you can do, for example, is a hidden button which appear on the "value change" event, and the action you want (ReConfigure) will be triggered only on this button (which will disappear until the next modification of the numeric...). You can think of other possibilities, like a delai between the first modification and the action... Good luck. laurent
  4. And if we could discuss about the first topic of this thread??? Congratulation Darren, you are far away from all of us... and I tried!!!! But, when I told about the arcade game, it was an example, of how far we can be traced (I don't care about people knowing as many time I'm playing as long as I'm doing my job correctly). I continue to think that some traces are not really "nice" to know or to see... OK the one telling who are looking at the same subject as us is quiet interresting... but some are definitely too much. But looking at your answers, I should be the only one not really appreciating this kind of behavior... So long life to Big Brother!!! or else, create a pool asking the "community" (which are not only the 10th people who are sending the maximum of post...) laurent
  5. Hi all! I love LAVA, I try to throw an eye every day and to help as much as I can... But every new update scares me! We can know who else is looking at the same page as us, we can see which members came to have a look at our profile, we can trace almost everything,... and especially things we would like to be able to do without a trace!!! If we use the Arcade game, everybody knows at what time and how many time did we spent on it (luckily I'm the only one from my firm using LAVA...) I'm now afraid to go through the entire LAVA, and to check things... Am I the only one? Is there a way to lower these capabilities (which are good for the moderator, but not really good (I think) for the others!). Don't want a Big Brother LAVA, do you? laurent
  6. The "Blinking" property is not for a particular Cell of a Table, but for the whole table. To change the color of a row, you need a Property Node, with on top the "ActiveCell" (row will be a constant, and column will be conneted to the itération of the For loop representing all the column), and just under the "ActiveCell" a "CellFGColor" to change the color. And if you really want something to blink, you can add all around a while loop (in a parrallel task) where you change the color every X seconds! Good luck! laurent
  7. QUOTE(TiT @ Mar 12 2007, 01:19 PM) I've just modified a few (very little) mistakes! Seems good!!!
  8. Thanks for both of you! Indeed, after changing the "active" input with FALSE, I get a very quick answer! (1,54 seconds for a 1.7 Mo file, which is good enough for now!) As for the 8.2, sadly I need to stay in 7.1... So next project, perhaps! Thanks guys! Laurent
  9. Hi, I need to transfer file in both ways between a computer with LabVIEW RT inside and a computer with Windows and LabVIEW 7.1. I tried the Internet Toolkit, but the transfer speed is pretty slow... (4.54 seconds to transfer the NI-RT.INI file !!!) I tried a quicker way (0.054 seconds !) using the FTP command (via the SystemExec.vi), but can't copy directly my RT file to my D: drive ! Does anyone has experience in FTP Transfer with RT target ? What is the best solution? Thanks for your precious help! Laurent
  10. Why don't you use a functional or global variable ? You can send the Error in this variable when it occur (in "A" or "B"), and read this variable in you main VI "C" (in the Timeout event, or somewhere else). Try this link to learn about Functional Variable: http://zone.ni.com/devzone/cda/epd/p/id/3124 You can use a Queue as well, if you don't want the last error to erase the previous one... Go through the LabVIEW functionnalities and librairies to discover what is existing!
  11. What do you need exactly to secure? - Your VI? In this case you can go to the "VI Properties" and, by selecting the "security" part, you can add a password, so no one else will be able to open the diagram without the password. - Your program? You will need to develop some functionalities to read a word, encrypt or decrypt, then let the user go or not go further in the program!
  12. Hello! I have a program developped in LabVIEW 7.1 and running on a remote computer with LabVIEW RT (but I suppose it could be the same question for a PXI, Fieldpoint controller, ...). I need to be able to stop and close my LabVIEW program, then to shut down the computer. In fact, if an electrical blackout occur, the computer is on a safe electrical system, but the program need to stop properly and shut down the computer to avoid using to much of the safety power. Thanks for your help! Laurent
  13. OK! Here is the bug! Nice to get a fresh mind on this kind of trouble!!! Thanks a lot. (and by the way, I've posted this "bug" to NI via the support, as well...) And thanks to the idea of keeping the array. Cheers, Laurent
  14. For those who like to resolve strange bugs... Here attached is a library where the main VI contains a Tree. The "bug" is quite simple, I create a Tree with Cycles and SubFolders. Each Cycle has a number of executions (written in the Tag and the Item of the Tree. Example "Cycle A - 5 executions"). Select a CYCLE, then change the number of executions (via the numeric control). When the value reach 1, the Selection (of the ligne) is lost... It's only when the value is above 2 that the Selection is kept! I would be really happy if some of you would like to put an eye over this problem! Thanks in advance. Laurent Download File:post-6600-1167924107.llb
  15. And why not creating your own "task killer" in LabVIEW? With VI Server you should be able to know which task is which, and then to kill it!
  16. That's only a clue to try (not sure if it's enough...): Check to save/export the MAX configuration (usually configData.nce) And load this configuration at the start of your software.
  17. Hi, What you can do is: When the customer starts the software, if the password is wrong, the software ask to contact you and to give you the serial number of the computer (accessible via the registry). You create then a password regarding the serial number, and send it to the customer. Then, when the software starts again, the customer enters the password, and the software check it regarding the serial number... Do you follow me?
  18. A second interesting thing about this place is, if by mistake you get a car crash in this place (which strangely doesn't happen so often!) the insurance doesn't search who is right and who is wrong! It will be 50/50... There is only 2 places like that in France! And we can understand why! Anyway, I'm happy to see that some of you are found of France! Nice to hear that, for my french ear...
×
×
  • Create New...

Important Information

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