LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Wire enumeration conflict

This is just a picture, not a VI and completely useless to troubleshoot.

 

Why show unbroken code if you problem is with the broken code?

 

So, what changes did you make? Did you edit the items of the enum? If you would have made it a typedef from the beginning, you would not be in this mess.

0 Kudos
Message 11 of 29
(315 Views)

Sorry I am new to this software 

Do you mean Main VI software file not picture ?

I have showed unbroken code by mistake from other source ( original one before changes made)

I have started to add  in parallel new Pattern with new Type definition.

 

 

0 Kudos
Message 12 of 29
(309 Views)

Thank you this works .I have removed and create a new constant

0 Kudos
Message 13 of 29
(296 Views)

I have another one same type error . What can I do ?

przemo1526_0-1719933031835.png

 

0 Kudos
Message 14 of 29
(291 Views)

@przemo1526 wrote:

Sorry I am new to this software 


Then you should not dive into the deep end! Learn the basics first!

 


@przemo1526 wrote:

Do you mean Main VI software file not picture ?


Yes, attach your VI and its dependencies Preferably saved for LabVIEW 2020 or earlier.

 

 


@przemo1526 wrote:

I have started to add  in parallel new Pattern with new Type definition.


I doubt your edited a type definition, because there are almost none so far. Do you even know what a type definition is? The only type definitions I can see on your picture are the diagram constants on the very left ("Hide", "Dialog") as indicated by the black triangle in the upper left corner). Also all your equal comparison (with the red coercion dots!) show that you compare apples and oranges.

0 Kudos
Message 15 of 29
(290 Views)

@przemo1526 wrote:

I have another one same type error . What can I do ?


You need to start with the basic tutorials!

 

Your subVI connector is a different data type compared to what's wired to it. They need to be the same.

0 Kudos
Message 16 of 29
(289 Views)

@przemo1526 wrote:

I have another one same type error . What can I do ?

przemo1526_0-1719933031835.png

 


You make sure you use the Type def in all constants and Connectors so they all follow any definition changes.
TypeDef | FRC LabVIEW Tutorials

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 17 of 29
(274 Views)

I have watched Tutorial, but still not able fix this issue.

I use Type def. for all constants

przemo1526_0-1720020658872.png

 

0 Kudos
Message 18 of 29
(234 Views)

@przemo1526 wrote:

 

I use Type def. for all constants


 

You need to use the SAME typedef for ALL constants, controls, and indicators. Don't forget the control assigned to the connector of the subVI.

 

We can give much more specific help if you would attach your VI (and dependencies, such as the typedefs). Showing us truncated stamp size images is not useful! Go to your toplevel VI and do a "save for previous", 2020 or below, the zip up the resulting folder and attach it here.

0 Kudos
Message 19 of 29
(224 Views)

To get us the LabVIEW files we need to see in order to be maximally helpful, please do the following:

  1. Find the "Top-Level VI" (the one you run when you want to run "everything" in your Project).
  2. Open it, click the File Menu, and choose "Save for Previous Version, and choose LabVIEW 2019 (which most of us can open).
  3. You should get a Folder with the VI you saved and copies of any TypeDefs, Sub-Vis, or other LabVIEW "stuff" your code needs.
  4. Right-Click the Folder, choose "Send To", choose "Compressed (zipped) Folder", give the folder a name, and attach it to your reply.

We'll take a look and help you understand what is going on.

 

Bob Schor

0 Kudos
Message 20 of 29
(213 Views)