Re-engineering a Labview VI written in 2010 it measures potentiometer nonlinearity.

[Argonath60]

Hi All,

I need some help.

I inherited a labview platform running a calibrator which was written in 2010.

During the Pandemic, sadly, we lost the programmer. I have some experience with labview, but the complexity of this is currently above my pay grade right now.

I could do with some help to look over the vi and tell me what I need to do to get it working.

Any one out there interested in helping out?

Thanks in advance.

[santo_13]

You can attach the code to the post so anyone can add their thoughts to achieve your goal.

Or are you looking for a consultant or hire someone on contract to help you out privately? it is less likely that a professional would be able to spend private hours to help you out for free.

[Argonath60]

Thank you Santo_13.

The company is small and has no budget to fix this, so unless I can, I'd say we are about to sink.

I'm looking to make a connection with someone who speaks LABVIEW, because it's not my primary skills set, who knows enough to tell me which way I need to go. If I had a budget I'd be asking for a consultant instead.

[billko]

---

@Argonath60 wrote:

Thank you Santo_13.

The company is small and has no budget to fix this, so unless I can, I'd say we are about to sink.

I'm looking to make a connection with someone who speaks LABVIEW, because it's not my primary skills set, who knows enough to tell me which way I need to go. If I had a budget I'd be asking for a consultant instead.

---

Can you give us a some detail on when it stopped working?  Is it like, "One day I ran the VI and it didn't work any more," or something to that effect?

[Argonath60]

It didn't stop working, it just started acting up..So I checked the NI-USB-6212 Multifunction I/O and could not fault it. Then I checked the hardware and didn't find anything wrong with that either.

The process checks three Pots simultaneously for resistance nonlinearities .

The unit has a human move the pot slider across all three pots at the same time with the same speed within set parameters. They could never get a human to do this reliably, so a stepper motor and ball screw drive was added, but the implementation was never finished. And that is where it has rested for the past couple of years. I came to fill the engineering hole created by the pandemic, but the Labview vi behind this is rather more complex than my experience can handle at the moment.

I added a stepper motor drive controller vi, though tying it into the current vi is proving to be a bit too much at the moment for my current skill level. I know I need some help but it's probably just a conversation with someone who knows what  they are doing. 

[BertMcMahan]

Since you've already said there's no budget to fix this, then basically no one is going to be willing to chat with you in private for an hour or two to get things moving.

If you upload your code here though someone might be willing to take a peek at it and give you some suggestions.

Then again, if the company is so close to folding that they can't afford a few grand on a consultant, then you might have some bigger problems to worry about. Hopefully you can get it sorted though 🙂

[Bob_Schor]

Hello, Argonath60.

     You seem to be a relatively new member, so you may not be aware that you have a Private Message capability attached to your account.  If you "log on" to your NI Account when you browse the Forum, you can see if anyone has sent you a PM (it should also show up if you "echo" your Forum traffic to your e-mail).

     There are a number of Forum members who are basically "academicians" (i.e. who work for schools or other "non-profits") who might be willing to look at your code, and who might reach out to you through the Forums.  I'm letting you know about this both to alert you to look out for such messages and to alert my "academic" colleagues on the Forum to consider reaching out to you, possibly by PM.

Bob Schor

[Argonath60]

Thank you, appreciated.

[Argonath60]

Thanks Bert, I didn't take this approach lightly. I'm not worried for myself, I can just retire and call it a day.. It's our other employees who's futures rest on the outcome on this problem right now. It's not even the money, it's knowing where to go to get help, and I mean, the real help kind of help, not the smoke up the butt kind that eats up any budget that might have been available. This is how we got here in the first place.

Anywho...I'll keep plugging away until it's either solved, or sold! 

[LLindenbauer]

You've been offered to upload the code right here for others to have a look, but haven't commented on that offer. It's OK if you don't want to make the code public - I just think it would be a shame if you missed the offer. From the cursory description, the scope seems limited enough for someone to be able to at least give some advice on the way forward.