LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Help with SSH connection to a Raspberry Pi using LIBSSH2

Hi! I need help 🙂

 

I´m working on a slow control system for reading the power supply of some Silicon Photomultipliers through a SSH protocol from a Raspberry Pi, using LIBSSH2 toolkit. 

 

I´m getting two main errors, up to this point. 

 

  • Error 5300: SSH write timeout. That I get when after the program gets stuck in the write all.vi
  • Error -8100: [Execute Again Error] The operation has been marked for non-blocking I/O but
    the call would block.
    • This error gets solve when I increase the value of the timeout, but after one interation in the loop it re-apears. If I stop the program and without waiting for a moment I run it agian it also apears. But if I wait a minute before running it again the error is gone, util the first iteration. 

If anyone has any ideas on how to solve it I would really appriciate it ❤️

 


 

  • 1122334455
0 Kudos
Message 1 of 4
(182 Views)

What version of LabVIEW are you using? SSH only works on newer versions of LabVIEW.

 

Tim
GHSP
0 Kudos
Message 2 of 4
(144 Views)

Hi Tim, thx for answering!

 

LabVIEW 25, so it should not be a problem. 

0 Kudos
Message 3 of 4
(103 Views)

@Regina_Malfoy wrote:

 

  • Error 5300: SSH write timeout. That I get when after the program gets stuck in the write all.vi
  • Error -8100: [Execute Again Error] The operation has been marked for non-blocking I/O but
    the call would block.
    • This error gets solve when I increase the value of the timeout, but after one interation in the loop it re-apears. If I stop the program and without waiting for a moment I run it agian it also apears. But if I wait a minute before running it again the error is gone, util the first iteration. 

 


hi! can you trigger this kind of behavior any time, you run your code, or does it occur sporadically? 

so, do you run every time into that time-out you execute your .vi? 

 

as changing the time-out time does resolve this temporarily, the workaround is to execute the .vi once and wait long enough before starting another execution.

 

 

 

some wild guess

try to keep the reference (this is an asumption) in the shift register of another while loop around the one existing while loop

here

alexderjuengere_0-1778147518361.png

 

alexderjuengere_2-1778148338941.png

 

 

0 Kudos
Message 4 of 4
(41 Views)