11-30-2007 03:49 PM
12-01-2007 01:00 AM
robbieyang wrote "If I used the shift register, I need to wire the registers in all states."
I think in Labview 8.5 you don't need to do it... in previus versions
you need to.
12-01-2007 01:10 AM
12-01-2007 02:17 AM
This statement is a bit simplistic. If you want to share the data between different states, you need to wire it in all states. It does not matter if you use a shift register or a feedback node.
Pnt wrote:
robbieyang wrote "If I used the shift register, I need to wire the registers in all states."
I think in Labview 8.5 you don't need to do it... in previus versions
you need to.
12-01-2007 06:36 AM
12-03-2007 02:24 AM - edited 12-03-2007 02:25 AM
There is one more option to wire the shift registers pass throughs...
Write your program first without bothering much about unconnected tunnels in some cases, and then run the tunnel wiring wizard. it will wire them up for you.
You can find Tunnel wiring wizard here
<LabVIEW8
http://forums.lavag.org/index.php?act=attach&type=post&id=121
LabVIEW8>
http://forums.lavag.org/index.php?act=attach&type=post&id=2056
Tushar Jambhekar
tushar@jambhekar.com
Jambhekar Automation Solutions
LabVIEW Consultancy, LabVIEW Training
Rent a LabVIEW Developer, My Blog
12-03-2007 09:50 AM - edited 12-03-2007 09:51 AM
Here is an example of how to carry local variables in a cluster and pass them to each state using a shift register. Only unbundle and bundle the variables your need. If none are used in a particular state, just wire the cluster wire straight through. You can add as many variables as you want to the cluster. You don't have to put the cluster outside the loop. You can create a dummy state that never gets called (as was mentioned before), and put the cluster there, just wire the cluster output to the right shift register (no wires from the left). Even though it never gets called, the compiler will create space for these cluster elements.
