Right way to approach my project.

[xipxid]

Here I try to approach in a "right way" to understand the "right way approach" for my project.

From my posting history I understand that on this forum ONLY the LabVIEW approach have value and are accepted. Well I have no knowledge / experience in LabVIEW, but... I have a logic trained by 35 years experience in ELECTRONICS !!! For this reason, I don't post / give my opinion on another subject anymore. Also I understand that small joke are considered "off topics" (and erased) for somebody that have under 100K... I don't know what... well... no jokes anymore. 

Back to our business...

I modify a vi to make it in a "didactic" manner that I can understand and you (anybody that want and can ) help me, can understand what I want. I attach it together with an old vi that is work ok (from my point of view... but is not "right way approach") and I explain what I understand, and I attach the original vi. Also I attach a .csv file that this vi's it using.

For any other clarification here I am.

Thank you in advance to all that want and can help me.

[billko]

---

@xipxid wrote:

Here I try to approach in a "right way" to understand the "right way approach" for my project.

From my posting history I understand that on this forum ONLY the LabVIEW approach have value and are accepted. Well I have no knowledge / experience in LabVIEW, but... I have a logic trained by 35 years experience in ELECTRONICS !!! For this reason, I don't post / give my opinion on another subject anymore. Also I understand that small joke are considered "off topics" (and erased) for somebody that have under 100K... I don't know what... well... no jokes anymore. 

Back to our business...

I modify a vi to make it in a "didactic" manner that I can understand and you (anybody that want and can ) help me, can understand what I want. I attach it together with an old vi that is work ok (from my point of view... but is not "right way approach") and I explain what I understand, and I attach the original vi. Also I attach a .csv file that this vi's it using.

For any other clarification here I am.

Thank you in advance to all that want and can help me.

---

Let's take a step back and analyze what you just said:

• From my posting history I understand that on this forum ONLY the LabVIEW approach have value and are accepted.

No, not really.  Just as there are "best practices" in anything that you do, there are "best practices" for LabVIEW, as well.  While some of them are just "best practices" for programming in general, there are some that are specifically LabVIEW-related - but most of those do have their text-based language counterparts.  So, no, it's not really true that ONLY the "LabVIEW approach" is accepted, but it is encouraged because they are tried and true practices and if everyone does things in a predictable way, it leads to better understanding by a developer, even if they haven't seen the code before.

Think of it this way.  If you were in an electronics forum and someone showed a picture of their project that had wires that were twisted together and left bare, you would probably discourage that practice.

• Also I understand that small joke are considered "off topics" (and erased) for somebody that have under 100K...

Humor injected into a topic is fine, but when it becomes so prevalent in a post that you cannot really understand the intent of the post, it needs to be scaled back.  Off-topic posts are discouraged because it can lead to confusion as well.  (I am frequently guilty of this one.)

Unfortunately, my LV versions at work are too old to open up your VIs, so I cannot help you fix it.  BTW - one LabVIEW "best practice" is to use LabVIEW projects to help organize your files.  This is pretty much an essential thing for all but the simplest VIs.

[RavensFan]

Have you taken any LabVIEW tutorials?

You have 2 major data flow violations in your modified VI.

1.  Your lower while loop won't run until after your upper while loop stops because you have a wire leading from the top to the bottom.

2.  Your lower while loop will always operate on the same data and due it as fast as the CPU will allow (nothing to slow down that loop!), because once you have data at the tunnel for the pink wire at the left hand side of the loop, it will remain the same for every iteration of that while loop.

[crossrulz]

I think you would benefit A LOT from learning to use an Event Structure and Shift Registers.  When you press the Start button, you can read the file and generate the entire interpolation array and either display it or store it in a shift register.  You can also set all of the Enable properties in there as well.  You can do similar things in the Stop Value Change event.

[BowenM]

Take a look at the template I uploaded the other day. You're missing a couple of important points out of it.

• You need a queue (or something similar) to communicate between the loops.
• You are missing the entire point of the queued message handler start that I uploaded. You removed the Event Structure completely and (mostly) retained your old architecture.
• You still have problems like loading files every loop iteration, among several other problems already pointed out.

Now, to respond to the VI you just uploaded:

• Your implementation of master cluster isn't right. As I mentioned the purpose of the cluster is to store stateful information about your program.  If you are not retaining (or acting on) any kind of stateful information the cluster basically does you no good.
• You have multiple issues with your cluster shift register.
  • It is uninitialized, which will likely result in unexpected behavior each time you restart your program
  • It isn't connected on the left side at all. You aren't doing anything with the data from the previous loop iteration.
  • In the VI I uploaded for you earlier, I specifically commented that you want to use linked input tunnels to ensure data is retained between loop iterations. Instead you went ahead and did exactly what I told you not to do and used default value in your case structure.

What I uploaded for you earlier was ~70% done. You needed to fill in the run case (which should have been copy/paste) and a couple of other minor things and you were finished.

P.S.  While I can't be positive, I highly doubt the moderators are removing your posts. As someone mentioned already, you are likely triggering an automated spam protection system and your posts are getting added back when a moderator manually reviews.

[xipxid]

The labVIEW is need to be learned it in a right way, this take time. I have no time ! What I make was... learn / test plenty of example and adapt to my practical necessities. This is a unusual approach LabVIEW project but this is what I have at disposition. For somebody that NEVER EVER touch LabVIEW... I think that is pretty well... all this in 3 weeks (read a lot on this forum, help, learn from examples, test example, isolate what I need and port it to my vi). First problem that I have was automatic clear chart before new plot, here it help me altenbach. After that... start all things here, wrong approach. I analize what was wrong, I change them in how I think right and I try to continue the project. 

MainScreen_old.vi work well, work like as expected about them but... from what I understand from here (altenbach and another's)  IS NOT RIGT APPROACH !!! Well... I need to understand the right approach from an example connected to MainScreen_old.vi, I need to learn to do mthings in the right way before make more mistakes.

https://forums.ni.com/t5/LabVIEW/LabView-bug/td-p/4145743

here altenbach and BowenM try to help me with the right way, I understand about "Master Custer", ( I understand the importance and I think that a sensational way to go anywhere with all that you need) and I put it on zip (MainScreen_old_mod_MClust.vi) to somebody give me some opinions. but...

As altenbach not finish the job (i bet that it do not have time) I tank him for what is doing but... I can't finish his job because I don't understand the logic.

@crossrulz

thank you for your reply, if you can put a comment on a vi or make a commented change on the didactic vi, I think that I can understand or try to understand.

question... "store in shift register" are... 

or a new shift register ?

I don't understand.

[xipxid]

I try 2 days and a night to figured out, to finish from where you leave it without success. I not have your knowledge and your experience to make that. I can analize how you do what you do. I can't continue your job 😞

[xipxid]

I will give you an example that I'm sure that you will understand.

let say... that I have here close to me a very good LabView programmer. This guy... from I don't know what reason... at a moment want to repair a machine like this...

Alone... never ever will can repair this machine. But... I go with the guy at machine, I put at his disposition my Fluke oscilloscope an multimeter, my machine diagnosis interface and the laptop. I explain how to connect the diagnosis sistem, and we see some errors. Well let start to repair the machine (clearly he don't know from, where he need to start). I say to him... measure here... what you are measure ?! this or that value. measure there.. another point... and so on... after all measurements we conclude that a cable are in open circuit (broke). he search the cable where I say to search... IT FIND the cable, repair them and... the machine go to work.

Well... he repair the machine ?! yes. only he ?! yes, with my help. the second time when he want to repair same machine... well... will remember how I think to repair first machine and will be much easiest for him.

[AnalogKid2DigitalMan]

---

@xipxid wrote:

I will give you an example that I'm sure that you will understand.

let say... that I have here close to me a very good LabView programmer. This guy... from I don't know what reason... at a moment want to repair a machine like this...

Alone... never ever will can repair this machine. But... I go with the guy at machine, I put at his disposition my Fluke oscilloscope an multimeter, my machine diagnosis interface and the laptop. I explain how to connect the diagnosis sistem, and we see some errors. Well let start to repair the machine (clearly he don't know from, where he need to start). I say to him... measure here... what you are measure ?! this or that value. measure there.. another point... and so on... after all measurements we conclude that a cable are in open circuit (broke). he search the cable where I say to search... IT FIND the cable, repair them and... the machine go to work.

Well... he repair the machine ?! yes. only he ?! yes, with my help. the second time when he want to repair same machine... well... will remember how I think to repair first machine and will be much easiest for him.

---

xipxid- words from perhaps a wise old(er) carbon based lifeform:

Hence you can see the value in training, correct? Then invest the time up front to get proper training in LabVIEW before taking such a project on.

Regarding any project- do you have a documented project scope with defined hardware/software requirements, needed inputs/outputs, budget, timeline, validation plan, operator training, source code control, schematics, deliverables? If not then you may be doomed from the start, if not that then be prepared for 'feature creep' and a long hard road along the way trying to get back to the future. It will be much easier for you and your customer in the long run to have the project scope defined first before embarking up the wrong trees

Regarding your posts, well- personally not a fan (+6dB N/S ratio), but trying to assist you in seeing the bigger scope of a project.

-AK2DM

[xipxid]

I'm reserve the obligation to reply you in detail on my future website. Until there I can tell you that the noise that you make not have a S/N (yes you are reading well Signal to Noise) ratio, in fact... are only noise.

Following your advice... ALL that you see on this link, for about 30 years... are only GARBAGE, (only an expensive ($120.000 !!! one of them...) popcorn machine. The theoretical R & D planes... I make it on 2017.... for this project. Please if you can help... well please help if not... please do not post same jokes. Thank you.

Edited

and... please... if this that you name it is... such a project... I'm a monk.

Second Edit, I'm sorry

"It will be much easier for you and your customer in the long run to have the project scope defined first before embarking up the wrong trees"

you... understand that... I... am or (I try to be... a super specialist in LabVIEW and I have a customer that I make the program for his project... ) :))

No sir... you understand wrong, I'm one man show... on this project, and NO this project will not be sales with the program that I make... oh... no sir. this project are in a "alpha stage", I need to test very much things before that will be in "beta stage" after this stage... before that project will be a product... well... in this moment will search companies to manufacture the mechanical hardware, optics electronic hardware etc. and of course the software. No sir... I need to make this software for testing purpose... not for selling purpose !!! :))