I have a case where I connect a switch and it never turns true, this is inside case 3 of the while loop.
the folder structure where the spreadsheet will be saved is Mapeo\Inputs\Honduras\Metadatos, in the application directory.
I wrote a comment where I am having the error.
Please someone help me.
Geologia - ESNACIFOR is the txt file you need to load.
A latch action switch (e.g. your OK button) turns back to the default state once the terminal is read by the code. If it does not reset, it in in a code section that is bypassed (e.g. a case structure where the other case executes).
Your other switches receive data from local variables, so all bets are off. Why do you read from a local varaible if the terminal is right there?
Also, an "equal FALSE" is just a logical NOT, right? Keep it simple!
(I don't have a 10ft computer screen, so I cannot really see what's going on. Sorry.)
From what I see, that architecture is a mess, and there is no way anyone else is going to be able to help you sort it out.
You need to use the tools available to you such as break points, probes, conditional probes, and highlight execution to you can progress throught he code and figure out why sections of your code aren't executing like you think, or that boolean values aren't the values you think they should be.
The thing is that both statemets should be true whe I click agregar datos.
You can elimnate the equals, replace the AND with an OR, and swap the cases of the case structure. Much simpler.
Still, this has probably nothing to do with your problem. As I said, your code is full of race conditions, so all bets are off. For example in the sequence frame to the left, you are writing a FALSE to "aggregar datos" while you are reading the same boolean in parallel. There is no way to tell what happens first. Most likely the local is written first and the value read from the terminal connected to the case structure is never TRUE.
Wow, you REALLY need to completely re-factor this before anyone could hope to help you. There are just too many basic mistakes that need to be corrected. The HUGE block diagram that stretches wires all over, the local variables and the unbundling clusters without names makes the logic impossible to follow. You need to at least break down some of the large sections into SubVIs so we have a clue what's going on.
This looks like code that would be easier to re-write than repair. If you are the one that wrote it, you have the best chance of making it work. At least you know what it's supposed to do so you can use the debugging tools to follow through the logic.
I had to try the Clean Up Diagram tool and it actually does wonders in this case. I still can't figure out what's supposed to be happening but you should try it and see if it helps you get any further... Good Luck!
Edit > Clean Up Diagram