Scott Carlson

QUOTE (4bestlife @ Jan 3 2009, 12:37 AM) How about getting a lot more specific. Think about your audience.. How do we know what you mean by "can not open" and "other network" and "the vi" etc.. We could infer / or assume that we know what you mean. That never works. I'm just saying, you are not going to get any help with a post like this. The "help quickly plz" subject also won't speed the process up. Post all important information. Is this rush time for your final school project?!? -src

Its just an uninitialized shift-register. Only can be hard to decypher if your not used to them. QUOTE (Anders Björk @ Sep 16 2008, 03:39 PM)

Norm -- I found the above post, completely appropriate. I have no idea, why you are "flipping out". "Get off it"? Did you write the clean-up routine? Are you personally offended? I agree, the clean-up routine isn't a replacement for writing clean code. -Scott QUOTE (Norm Kirchner @ Sep 10 2008, 03:24 PM)

QUOTE (Scott Carlson @ Aug 1 2008, 10:33 PM) There were a couple of flaws in this library,.. I will post a more recent Library soon, possibly in the code repo. I am also working on a Multi-peer Encrypted Video Phone, which will initially use ARC4. -Scott

QUOTE (b_subhasis @ Sep 2 2008, 02:11 AM) Download a PDF Printer (i.e. CutePDF).. Then write a Labview program to Print the HTML to the PDF Printer.. Done. -Scott

QUOTE (manikanth @ Sep 2 2008, 02:29 AM) Will you be using transistors or relays to power your circuit? Really man, how can we answer a question without you providing one with substance? -Scott

QUOTE (Giseli Ramos @ Sep 2 2008, 07:26 AM) I definitely don't think you should leave the TCP behind. This sounds more like an OS issue than a Labview issue. #1 What Flavor of Linux are you using. (I can be more helpful ) #2 My first suspicion is that you have a firewall blocking ports... Have you looked into this? -Scott

QUOTE (Gabi1 @ Aug 25 2008, 03:37 PM) I am not sure about the IR interface, but have you looked at the Price Point for Labview PDA Module? That would be an expensive Universal Remote!! (Fun project though)

QUOTE (Norm Kirchner @ Aug 25 2008, 12:41 PM) Maybe the search string could be piped to google. google search: $string site:lavag.org That would be a cheap fix -Scott

QUOTE (JustinThomas @ Aug 25 2008, 08:57 AM) Hey Justin -- Create small files.. Transfer the finished ones while you are measuring, that way, at the end of your 20-25 minute test, you have your data as well. -Scott

QUOTE (normandinf @ Aug 12 2008, 09:02 AM) Subversion and TortoiseSVN . If you take this route, we are around for further questions. -src

QUOTE (Tomi Maila @ Jul 31 2008, 04:58 AM) Here is an ARC4 Stream Chipher Library as requested.. I'd like to add more later, but it is late, long drive in the morning. This was made with Labview 8.5.1 -src

QUOTE (rolfk @ Aug 1 2008, 03:59 PM) Rolf -- I hope you didn't take my above statement personally! I had no idea that LabPython even existed until this morning! Very cool. -Scott

QUOTE (Gerod @ Aug 1 2008, 11:46 AM) Gerod -- This may be way off base but, have you tried calling the decontructor method for your object at the end of your program? i.e. d.del() ? Try that? It appears that the guy who wrote the LabPython may not be properly cleaning up after execution and exit, I don't think its a Labview issue per say, as much as it is a LabPython issue. Also, try to comment out the instantiation line before you execute a second time (comment the d = canvas.Canvas line) and see if that works.. The object may already be there? If these suggestions don't work, I'll install LabPython tonight after work, and give it a shot locally. -src QUOTE (Gerod @ Aug 1 2008, 11:46 AM) This is the vi i run (once) to call the script. No loop, no run continuously, only click twice the arrow. I forgot. I tried also to add p=None at the end of the script but without success. The only way to run twice is to close LabVIEW completely and load again the vi, these suggests me that there is some resource reserved by LV. Gerod -- This may be way off base but, have you tried calling the decontructor method for your object at the end of your program? i.e. d.del() ? Try that? It appears that the guy who wrote the LabPython may not be properly cleaning up after execution and exit, I don't think its a Labview issue per say, as much as it is a LabPython issue. Also, try to comment out the instantiation line before you execute a second time (comment the d = canvas.Canvas line) and see if that works.. The object may already be there? If these suggestions don't work, I'll install LabPython tonight after work, and give it a shot locally. -src

QUOTE (Gerod @ Aug 1 2008, 10:41 AM) Gerod -- The fact that you can run the code several times from a command-line and only once in LV, tells me that there may be some sort of "house cleaning" required. In the command-line environment maybe things are being destroyed (canvas object 'd') after it is ran, in LV maybe this is not happening. You are instantiating a canvas object. Is there a method for destroying it when finished? I see that when you do not include the canvas calls in your code, ir runs just fine.Are you running this code in a loop? How are you executing this. Do you hit the play button, run once, hit the play button, run twice etc? I only ask this because, you should only need to instantiate the canvas object once. If its the case where you are not instantiating repeatedly, refer back to the first paragraph..I hope this helps. -src

QUOTE (rolfk @ Aug 1 2008, 05:05 AM) I agree with Rolf -- (and there is no way I'm installing mysql just for fun . Separate the problem, test your code in a pure python interpreter first, and deduce whether its your code, some component your code uses, or the environment you are executing your code in. -Scott

QUOTE (Poormanphysics @ Jul 31 2008, 11:57 PM) poormanphysics -- Could you provide us with the snippet of mathscript code you are having issues with, specifically a couple examples of the types of 3d vector calculations you are attempting? -Scott

QUOTE (Ed Dickens @ Jul 29 2008, 05:20 PM) I'm there. Monday Night: Partying. Tuesday Night: BBQ/Partying. Wednesday Night: Partying. Thursday Night: Partying. (Going home the next morning). -src