LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

2 array mismatch

Solved!
Go to solution

I know that the input and output need to be the same but I didn't know how to solve it. AND I want to understand if I will change the entity what consequences will come up for other VIs etc.

 

Indeed I implemented the Build Array but it shows up more and more errors.

 

If I changed to concatenate mode there are also more errors then before and it ruined all other code.

 

I tried EVERY solutions you gave me but the errors after the solution influence a lot of other VIs...therefore I ask my next question - see above - that another wire is not working.

 

PS: It's also frustrating to get the info "do the courses" and I do it again and again and have no clue what and how to change. But I will find another way to get to a solution.

0 Kudos
Message 21 of 25
(1,140 Views)

Hi Susanne,

 

Indeed I implemented the Build Array but it shows up more and more errors.

Your first picture shows some functions and (mainly) wires with 1D array data. Then YOU changed something and created 2D arrays instead. Then I told you how to implement code that will result in 1D arrays (as you seem to need) and you also failed in implementing that.

 

I told you "delete the wire and the corresponding UndbundleByName element" and you deleted the whole UnbundleByName node,. Then you claimed about unwanted problems…

 

All that could have been much faster when you would have attached some real VI instead of posting just images!

You know the basic (but unwritten) rule of a forum like this (or the German LabVIEWForum): When you write just text, you will get just text as answer. Providing images might result in just images as answer. Providing real code (aka VIs) will most often result in better VIs. Think about that…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 22 of 25
(1,136 Views)

No, I'm sorry, I wrongly expressed myself - I only delete the element of the UnbundleByName - of course not everything.

 

I fixed it as you said with concatenated array mode.

 

Yes, I know. I cannot post every VI - not because I don't want to - but the project is huge. When I post only one VI, you cannot run it because you need ctls, SubVIs etc. I tried to do a smaller one but I also need to post the database etc.

 

How can I post a VI (where there is a problem) which is able to run when it's calling other VIs, ctls you don't have? Perhaps there is a possibility I don't know yet.

0 Kudos
Message 23 of 25
(1,131 Views)

Hi Susanne,

 

you don't need to post your whole project. We don't need to run your simple calculation for applying a polynomial function on your measurement data - we have done this several times before…

 

It is sufficient to post just the part that you can't fix. And most often a small VI which just replicates the problem is more than enough.

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 24 of 25
(1,116 Views)

I will try the next time, thanks!

0 Kudos
Message 25 of 25
(1,113 Views)