Convert a normal number to binary?

[RavensFan]

I think when you copied it, the stop button on your original code was lost and you have a different stop button on the new code.  In your event structure there is a case 1 which isn't associated with anything.  I am assuming that was the Stop button mouse down event (or something like that.).  Go to Event case 1, right click the event case and select "Edit events handled by this case".  Give it an event such as stop button mouse down.

When I did that on my machine, the broken run arrow became solid.

[Vr6Fidelity]

I swear I dont have that as an option.

How do I just delete the other unsed case?

[RavensFan]

I don't think you'd want to delete that case.  I think you want a case to handle the press of the stop button.  Otherwise you have no way of stopping the loop that contains the event structure.  I'm also not sure why you have a Stop Program Button and a Stop Program LV indicator.  The indicator just seems to provide a local variable that you are using in the broken event 1 of the event structure.

Attached is a picture of the menu option.  Make sure you are on the border of the event structure or that top title bar saying 1 when you do the right click.  Attach it to Stop Program Mouse down.  You can get rid of the Stop Program LV indicator and its local variable in the event structure.  Just wire a true constant to the terminal going out of the event structure.

Message Edited by Ravens Fan on 08-03-2007 03:59 PM

[Vr6Fidelity]

Im using LV 8.0 and my choices are not even remotley similar.

HELPPP!!!!

[Dennis_Knutson]

That's because you have LabVIEW base. The base version allows you to run VIs with the event structure but does not allow you to create or modify.

[Vr6Fidelity]

Ok so we have Identified the problem. A good start.

How do I fix it?

[altenbach]

Didn't you say you only had LabVIEW base. Maybe you should eliminate the event structures and use plain polling instead.

You also have way too much duplicate code.

[minnellac]

We kinda zipped past this, but I think you say here that the signal that you are monitoring is changing at ~2kHz (meaning a 2000Hz periodic signal, right?). If you are only sampling this a 4Hz, your aren't just violating the Nyquist criterion, you are brutalizing it. The signal that you are getting is probably heavily aliased. What you really want is a low pass filter in the analog domain (before digitizing). A moving average is a low pass filter, but after digitizing it, you are filtering the aliased signal, so the output is unpredictable. I guess there could still be some value here, particularly if you know the signal frequency doesn't waiver away from 2kHz. I'm afraid to ask, but what are you trying to use this signal for?

Also, you can strike the previous comments if you just meant that you are monitoring a DC signal that is being updated at 2kHz.

Chris

[Vr6Fidelity]

Well Since the potential of this signal floats at 1000VDC above ground and has an AC component of 175A and 480V pk to pk I think ill stick with the digital data. Filtering is not really feasible.

Seriously, can somebody with event structure capability fix the issue and re host it? Pretty please. It is soo close and i have been battling this for a week.  

[RavensFan]

Chris isn't talking about filtering a high voltage signal.  He is talking about the filtering of whatever 2000 Hz signal you are currently reading in at 4 Hz into your DAQ card.

Attached is your VI with the stop button reattached to the event structure.

(#120)

Message Edited by Ravens Fan on 08-03-2007 05:14 PM