peteski

Yeah, all we need is a "score" on the top of the screen while we are programming. We might Never be intelligible again! -Pete Liiva

Just for that, I just gave you one, Mike! -Pete

"Wired" ought to be one! Where it should fit in the hierarchy is the *real* question... ;-) -Pete Liiva

QUOTE (empstar @ Jun 9 2009, 07:45 PM) The first four bytes might be a u32 or i32 indicating the array size? Besides that, what Rolf just said is likely the reason the rest of it is all zeros.

QUOTE (jdunham @ Jun 4 2009, 04:00 PM) To show this more explicitly for your VI:

QUOTE (Minh Pham @ Jun 3 2009, 03:35 AM) Actually, that depends on how much hardware labviewnoob has. If he only has a DC motor and nothing else, he is missing an important piece of the puzzle, namely the motor control electronics. labviewnoob, Do you have any control electronics for the DC motor? If so, you would need to provide info as to what those control electronics are before anybody here can help. If you don't know what I'm talking about, then start browsing at this link: http://sine.ni.com/nips/cds/view/p/lang/en/nid/3309 Hope this helps, -Pete Liiva

QUOTE (i2dx @ May 30 2009, 07:38 PM) Express Vi's? Express VI's?!?! We don't need no $^!&*!&% Express VI's!!! REAL LabVIEW programmers start with a blank VI... and previous to that has deleted or hidden ALL Express VI pallets... Or at least refuses to acknowledge their presence on the palette!! Mind you, in all honesty, I haven't touched scripting yet... is the time now? -Pete Liiva

QUOTE (PaulG. @ May 28 2009, 01:02 PM) Ditto on that. Back in the early 90's I went to SF for a week and a half for work, and back before web browsers I inquired on usenet news on some group (rec.food.<something I forget now>) I asked for restaurant suggestions. The replies I got, when compiled and dupicates filtered out, then put to nine point font and single space, gave me about 50 pages of suggestions complete with testimonials! I've found the SF area to be a great place to visit over the years - lots to do and see. -Pete Liiva

QUOTE (ShaunR @ May 23 2009, 04:18 AM) I've taken a quick look through the documentation and examples, and it looks like it should be doable by combining the "Gen Dig Pulse Train-Continuous-Pause Trigger.vi" with with a "Gen Dig Pulse Train-Continuous.vi". First start the first counter with "Gen Dig Pulse Train-Continuous.vi" which will be the "clock pulse" for the second counter, then start the second counter with the code from "Gen Dig Pulse Train-Continuous-Pause Trigger.vi". The code from "Gen Dig Pulse Train-Continuous-Pause Trigger.vi" would have to be modified to tell the second counter to use the output from the first counter as its sample clock. This I think should be doable using the "Sample Clock" instance of the "DAQmx Timing" function in the DAQmx palette. BTW, the "Gen Dig Pulse Train-Continuous-Pause Trigger.vi" calls for a digital line for the Pause, that would imply to me that it is a little more hardware driven then software driven. I don't really have the time right now to try to verify any of this, though. I'm taking a 3 day course on how to write engineering requirements. Hope this helps, -Pete Liiva

QUOTE (Gary Rubin @ May 22 2009, 07:46 PM) I've got to dig through the documentation to trigger my memory on that. When I get a chance I'll have a look. -Pete Liiva

QUOTE (ShaunR @ May 22 2009, 04:13 PM) Nice catch, ShaunR! That should be able to make it work. I forgot all about the Gate functionality. Getting rusty in my old age! -Pete Liiva

QUOTE (for(imstuck) @ May 22 2009, 11:08 AM) No worries! Dang... I was 25 when I first started to use LabVIEW, so in one way of looking at it you have a head start on me! -Pete Liiva

QUOTE (Gary Rubin @ May 12 2009, 10:27 AM) Hmm, If I remember correctly, there are 4 counter timers on that board. Would it be possible to add a third counter in the mix, so that: Counter 0 is the constant clock Counter 1 is the pausable counter Counter 2 is triggered off of Counter 1 I have not played with the Pause trigger in any way, shape, or form, so I'm not (yet) familiar with its behavior. I have found that the counter timers can be very useful and versatile on these boards and on the MIO boards, but I almost always have to "re-learn" things when I dive back into them. -Pete Liiva

Gary, I have had a wide variety of experience with NI technical support and IMHO it sometimes really boils down to the person you interact with. Sometimes I've had better luck starting with the local reps I know then calling and asking for "random" support. I'm finally coming back to this forum after a long and exhausting project, I've had some experiences playing with the PCI-6602 cards in my applications, is it too late for me to bother looking at what you had posted? -Pete Liiva

QUOTE (rahul @ May 22 2009, 12:32 AM) Rahul, One thing I've noticed over the years is that sometimes screen saver and power saver options can cause problems with hardware drivers that are unstable. Quite often for test computers I will completely disable all screen saver and power saver options. If that doesn't help, another couple of things that come to mind, do you know if this is a problem you only see with multiple cameras as opposed to using only one? I've had success using a single firewire cameras over long periods of times using LabVIEW 7.1.1, in different test setups using a Point Grey Research Scorpion in some cases and a Sony XCD-v50 in others, but I have not done simultaneous camera work with firewire (yet). I do admit the firewire setup is a bit flaky and takes some care to get working properly. You may need to check your code to make sure it is not doing odd things, like multiple inits and/or closes of the firewire camera references within the acquisition loop or things of that nature. Hope this helps, -Pete Liiva

QUOTE (for(imstuck) @ May 21 2009, 07:07 PM) Just a little bit of trivia, way back in the dark ages, like before LabVIEW had the "Undo" feature, this is the only way "while loops" worked. I wonder if this example has some old heritage to it? -Pete Liiva

QUOTE (JohnRH @ Mar 7 2009, 11:34 AM) IMHO, having an oscilloscope on hand for debugging a test system is just short of a fundamental requirement. HOWEVER, that does not mean that it has to be an integral part of that test system. If you already have a "floating" (uncommitted) oscilloscope on hand, you could potentially use that for troubleshooting, while you have nicely tucked into the test system a set of PXI based digitizers to do the heavy lifting after everything has been verified to be working properly. If you have the time to do it, you can develop some on-board diagnostics with the PXI equipment and verify those diagnostics with an external oscilloscope. And that would be my $0.02. -Pete Liiva

QUOTE(Norm Kirchner @ Oct 19 2007, 09:49 AM) I just feel like I've just "listened" to my 8 year old son... kind of... maybe... Huh? -Pete Liiva

QUOTE(ASTDan @ Aug 13 2007, 05:15 PM) Isn't there another one along the lines of "if it don't fit, use a bigger hammer" ? -Pete Liiva

Toaran, In what you've posted, If you already had opened a session to your serial port, you definately closed it before configuring, which doesn't really make much sense. You "got no errors nothing" because you aren't even wiring up the error hanling cluster. You are probably geneating an error but basically ignoring it. If you select "find examples" in the following location: http://forums.lavag.org/index.php?act=attach&type=post&id=6114 Then search for serial to find the following: http://forums.lavag.org/index.php?act=attach&type=post&id=6115 You can then get an example of a reasonable way to handle serial communications. Then modify that to your needs: http://forums.lavag.org/index.php?act=attach&type=post&id=6116 Hope this helps, -Pete Liiva

QUOTE(TiT @ May 29 2007, 11:09 AM) TiT, I have a couple of quick comments (I've been swamped recently, not much time to contribute to this forum, unfortunately!) Beware of the voltage levels on the RS-232, if this is a "standard" RS-232 device! (and standard can be a very difficult term to apply to RS-232!) I've measured voltages of +/- 11 volts using an oscilloscope. If you use a standard DIO at TTL levels, you may need some circuitry or a box to properly handle the mismatch between TTL and RS-232 levels. BTW, why not just listen using the computer's RS-232 port and copy down the byte stream to a file, then spit that file back through the RS-232 port when you want to simulate? It might be faster, better, and cheaper that way. Is there something particularly "interesting" you expect to need to do that an RS-232 port may not quite be able to facilitate? -Pete Liiva

QUOTE(dsaunders @ Mar 16 2007, 01:32 PM) Maybe Alfa is implying that he likes all trips in n dimensions, were n is any given integer. Maybe even positve. I must say I agree, since I'd personally find it hard to fathom a trip in a rational, non-integer dementia (oops, I mean dimension) or worse yet, some "irrational" dimension... -Pete Liiva

QUOTE(yen @ Mar 8 2007, 02:53 PM) IMHO, definately the one on the left! The frozen look on the face is simply "perfect" for the caption! -Pete Liiva

Umm, it will reflect the microwave background radiation? -Pete Liiva