Leaderboard

That was only the start... Attached what it was created with. No description, no comments, no even icons - I warned you. wired-wires.zip

Download LabVIEW 2009 (755 MB) Download LabVIEW 2009 (64-bit, 822 MB)

Hey I had a play with it and at first is frustrated me too, but I found a bit of a hack. The format code you need to use to force text is @ However if you write your text before you format the cell and a cell has 11E6 then Excel will auto format it because there is no format set, then if you format it to text you just get 11+E6 as text. But if you format the cell before anything has been written then the cell essentially doesn't exist or hasn't been allocated and the toolkit throws an error. The way to do it is write an empty string constant to the desired cells, write @ as the format code then write your cell ie 11E6 The following is an example that demonstrates this.

I'm not trying to rain on anyone's parade here (I think it's a good tool and you've obviously put a lot of work into it), but since you asked... Did you develop it to a documented ISO audited and approved process? I need something that I know the vendor used an approved quality process, so I can be confident that the artifacts that it produces are complete and correct, and my customers can too. That's why I need to stick with Requirements Gateway for the time being - my customers can defend it because I can defend it because NI can defend it Also, we do a lot of TestStand work and RG can dive into that too...

Done: However cross calculation algorithm slowed it down quite much. And highlight execution drops "bounce" on crossings...

Right - when it's an emergency (hence the name) you need it in hardware, not software. I wouldn't call it "immediate stop", because that suggests it's the same as an emergency stop. Also, it gives the operator 2 options, so if there's an emergency, they need to think and make a decision on which button to press (SW or HW), and decision making is difficult and unreliable under emergency situations. Stick with having a HW stop, and monitor it with a digital input so your software can react appropriately.

If this is an Emergency Stop Button, shouldn’t it be implemented purely in HW? What if your UI computer goes down? When you have a motor, I'm guessing you will need emergency stop buttons at the motor itself and by the work station, at least.

Here is a quick demo of an x-control I threw together. There is an issue with changing the value and being able to change the state (Pressed or Unpressd) If you want both operation to be done by a left mouse click. I’ve thought of 2 way to maybe solve this issue. The first way would be to create a click zone and when the user is ready to change states he left clicks in that area. The click zone needs to be reasonable distance away from the knob pointer so the proper operation will happen. The second method would be to use a left click to change the value and a right click to change the state. I’ve implemented both methods in this xcontrol. Xcontrols are a bit of a pane to work with if you are new to LabVIEW so I also included the basic code in the demo. Use the best one for you. Let me know how it works out Mark Click and rotate.zip

Just to prove that it is technically possible: Yes, programmaticly: Sorry for not closing references, etc.