Trouble with NI USB-9162 Measurements

[El_Markador]

Hi ColterM,

Have you taken a look at this KB in troubleshooting that error? What other steps have you done and what resources have you looked at? Also, it would be helpful if you could answer some of Bob's questions above explicitly on this forum post so that others can get more context and information on your current issue. It's difficult for me and others to come up with next steps when we lack information about important details.

[Henrik_Volkers]

Just a guess: Maybe the software needs a (MAX) configured task?  With exactly the same name?

[ColterM]

Thank you for posting,

I went ahead and talked on the phone with Bob, one of the reasons why that information is not here.

I believe the solution now is to find a way to reinstall the configuration manager? Also, if this route does not work, it may be easier to just create a new exe. for our lab to start running our tests again. What we use is a compression gun to compress connectors to cables and we would like to analyze its compression force once it has reached a certain amount of compressions. Since I am new to this whole exe. building environment, is there a route we can take to build a new exe. for us since we are in a bit of a time crunch? If not, is there a route I can take to teach it to myself? It shouldn't be too difficult to create, since we are just measuring the force from this compression gun with a NI 9215 piece of hardware to read that data.

I appreciate the responses!

ColterM 

[El_Markador]

Hi ColterM,

Building an EXE from a LabVIEW project is actually really easy. There are only a couple of steps that you have to manually configure, but LabVIEW takes care of everything else for you. Take a look at this resource for a step-by-step tutorial on how to create an EXE:

"Building a Stand-Alone Application"

http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/building_a_stand_alone_app/

[ColterM]

I am receiving a Procedure Entry Point Error, does that make sense to anyone? I have attached the picture of the error message.

Thanks,

ColterM

[ColterM]

This occurs when I try to start up a new Labview Project.

[El_Markador]

Hi ColterM,

Can we get a higher resolution screenshot or could you post the actual text of the error message? It looks like there is some useful information in there but I can't read it!

[ColterM]

I am sorry, here is another picture with better resolution as it would not let me copy the text for some reason!

[PezDeSpencer]

Hello,

Does this error get thrown before the LabVIEW splash screen or upon creating a new project file? Does it occur when just creating any VI? When did this error begin occurring? What version of LabVIEW is this happening in (I’m assuming 2011, as earlier in this thread you said you uninstalled 2016 and installed 2011)?

If this is true, there could be some dependencies that were not created correctly, and the new 16.0 and newer drivers may not back support LV 2011.

This specific error appears to be a windows error, not finding the NI executables correctly. My best guess is that this would have to do with what software you have installed and in what order you installed it all. 

If this is a time sensitive project, uninstalling and reinstalling software can be a lengthy process, so if in the meantime you have another development computer that you could work on that may be faster.

A force re-install of your NI software, paying attention to compatibility may be a good next step to help narrow down the issue. The link below should be helpful.

LINK: Force Reinstall NI Software from the Command Prompt in Windows

http://digital.ni.com/public.nsf/allkb/ADD22E807D5A12AD862579EC00760F79

Best,

Spencer R | NI

[ColterM]

Thank you, and yes this error pops up when I try to create a new labview project, but not before. However, It allows me to create a new VI without the error. This error started occurring after re uninstalled the 2016 version and installed the 2011 version. This is happening in LabVIEW 2011 I will try and re-install everything, paying attention to the compatibility order. Thank you again for your support.

ColterM