From the Labview state machine to the production, consumption patterns, now work with the operator model, but this pattern feeling good complex, feeling is much more difficult than to learn c # multithreaded, trouble which god give some directions, be appreciated

CodePudding user response:

From several aspects to talk about my feelings,
One, introduction to ease: c # multithreaded will be simpler; And NI to follow up the AF maintenance is not enough, make a phone call to ask customer service will find that a lot of NI your application engineer's understanding of AF is also very obvious, even to zero, AF can check the online tutorials are those - official, fake official, NI English BBS, domestic technology blog with fork blowing fog... Eventually found that still have to depend on oneself slowly chew,
Second, in terms of function, both about the same, can realize the asynchronous, Timer, Background Worker, message is sent, the implementation complexity on each have advantages, c # OOP are pure, LV OOP is always feel a little raw,
Three, the operator framework can better compatible with NI hardware, use DAQmx interface, then use c # Measurement Studio, and it's not particularly friendly interface, and can't keep up with the latest. Net programming framework,
Four, from the perspective of the job don't ask, what to learn better, work need to, you learn right, work is not what you will, in the project needs, personal advice, chew framework to see whether the running effect and workflow, never mind is how to realize the function, after all, you are using, rather than development, and debugging, to try, only then own to solve many problems, there is communication and ask at that time, his is settled,