Labview Program changes behavior after looking at (not changing) the Block Diagram -
my labview program works charm, until @ block diagram. no changes made. not save. ctrl+e , ctrl+r.
now not work properly. restart of labview fixes problem.
my program controls 2 scanner arrays laser cutting simultaneously. force parallel working, use error handler , loops wait signal scanner. loops run more should.
what majorly happen in labview when open block diagram messes code?
edit: hard tell happening without violating non-disclosure agreement.
i'm controlling 2 independent mirror-arrays laser cutting. while 1 running 1 cutting-job, other supposed run other jobs. fast. when first finished meet @ same position , run same geometry @ same slow speed. jobs provided *.xml , stored .net objects. device runs recent job , overwrites when getting new one.
i can check if job still running. while true run while loop other jobs. loop runs few times , ignores wait-blocks degree. skips part reads xml job file, changes speed part fast again , saves it. runs 1 time fast.
@joe: no not. runs once well. afterwards not.
youtube links
there 1 thing can think of changes solely opening block diagram.
when block diagram opens, commented-out or unreachable-code-compiler-eliminated sections of code load subvis. if 1 of commented out sections of code somehow interfere running code, might have issue.
there 2 ways know of interfere... both of them improbable. a) have sort of "check vis in memory" or "check types in memory" you're using plug-in system. when commented-out sections load, change vis in memory. such systems not uncommon when parsing xml, maybe. b) using run vi method dynamically invoked vi execute top-level vi, loading diagram, discovers subvi of current program. vi cannot simultaneously top-level , subvi, call run vi returns error.
that's it. can't think of else. both ideas seem unlikely, given claim , lack of block diagram, figured i'd post hypothesis.
Comments
Post a Comment