Hobbyist Toolkit

cancel
Showing results for 
Search instead for 
Did you mean: 

Device interrogation failed: unable to connect to the target

Solved!
Go to solution

Fresh PC worked with no problem

Dumpit_0-1647006843305.png

Did get a crash when I closed it down though.

 

Have now removed all traces of Labview, including Silverlight, Rabbit & Erlang from the desktop- Will see what happens

 

0 Kudos
Message 11 of 18
(324 Views)

Ok, so uninstalling everything from the Desktop PC still didn't work - At least I now have a working system to compare with & I know what the problem is - I just don't know how to "Downgrade Visa 21.5 to Visa 20.0 - I guess more research is required'

 

Dumpit_0-1647065060464.png

 

0 Kudos
Message 12 of 18
(313 Views)

@Dumpit wrote:

I just don't know how to "Downgrade Visa 21.5 to Visa 20.0


That is removed if you uninstall everything.  Or you should be able to uninstall just VISA.  You do that through NI Package Manager.

David Wilt
The New Standard LLC
0 Kudos
Message 13 of 18
(307 Views)

Visa is not an option in NI Package Manager - I tried to delete the individual files, couldn't as they were open in NI-Max. Renamed them. Un-installed everything via NI Package Manager. Uninstalled NI Package Manager, then uninstalled National Instruments Software, Silverlight, Erlang OTP, RabbitMQ Server. Re-Installed Labview 2020. When I opened NI Max, it initially showed Visa as 21.5, but changed to 20.0 almost immediately. Now shows exactly the same as the laptop, but still won't connect?

Dumpit_0-1647198027539.png

 

This is really frustrating, but it looks like my only option is to format my Desktop PC

0 Kudos
Message 14 of 18
(292 Views)

@Dumpit wrote:

Visa is not an option in NI Package Manager


You do not see NI-VISA like this in NI Package Manager?  This is from LabVIEW Professional so it may be different if you are using a Community Edition.

 

Screenshot 2022-03-14 113544.jpg

 


@Dumpit wrote:

Re-Installed Labview 2020. When I opened NI Max, it initially showed Visa as 21.5, but changed to 20.0 almost immediately. 


The fact that MAX showed a different version initially proves that not everything was removed.  If everything had been removed it would not be able to know 21.5 was ever installed on the PC.

 


@Dumpit wrote:

This is really frustrating, but it looks like my only option is to format my Desktop PC


Unfortunately this has been my go to when wanting to remove all NI software from a system.

David Wilt
The New Standard LLC
0 Kudos
Message 15 of 18
(282 Views)
Solution
Accepted by topic author Dumpit

Hi,

The LINX target configuration vi connects to the RPI using ssh. If you are able to ssh to the RPI from puTTY then its possible your firewall settings are blocking the LabVIEW application. 

Message 16 of 18
(277 Views)
Solution
Accepted by topic author Dumpit

Thanks for the info - Not sure if it actually was the Firewall (Couldn't find anything) but it got me thinking. I removed everything I could think of (again) but this time, I went big - Also searched the registry for anything to do with National Instruments, Visa, PXI, and PAL. Deleted anything that had the letters ni in the string (Figured I'm going to have to format anyway) - Installed Labview 2020 Community Edition, and still couldn't connect. Was about to throw my toys, when I remembered your post - Checked the Firewall & couldn't see anything obvious.

I then decided to disable my Anti-Virus (Avast)

Dumpit_0-1647627589323.png

 

I'm In - Thanks so much.

 

Appreciate all the help.

 

0 Kudos
Message 17 of 18
(242 Views)

So this has been fun - Successfully connected to Target, but Labview installation Failed. Wasn't really looking forward to starting a new thread. Saved the log file for it, but decided to fumble around with the Pi side of things first. Went to Raspberry Pi Imager & loaded the latest version, with recommended software. After setting up the Pi, Labview successfully connected, and I updated (Installed?) the software successfully. Thought I was finally done - Tried to run the example & the deployment completed with errors. Example VI would not run. So far I'm batting 3 out of 3 - Not sure what I did at this point, seeing as I had started playing with Avast Firewall rules & Bouncing between Labview & Pi. Bottom Line is that I am now able to run the example, with my anti virus active. (It's weird though, as the "fresh" laptop that I loaded, already had Avast installed & never gave me a single problem connecting) - I can only assume that I had the remote GPIO disabled on the Pi (No idea if this required to run the example, but it seems logical as Labview on the PC is controlling the output on the Pi) - Final Outcome is Labview 2020 Community Edition, Raspberry Pi Bullseye (2020) - After many attempts, is finally able to run the example with the Pi Config below.

 

Dumpit_0-1647800617187.png

 

0 Kudos
Message 18 of 18
(226 Views)