LabVIEW
NI VISA having error
Hi guys , when im trying to save the permission in NI - VISA , it pops up this error message and im not sure how to solve it. Please help me as i need to solve the problem asap. Thanks in advance for any advice.
Hi alex,
@alexTan132 wrote:
Please help me as i need to solve the problem asap.
Please explain what exactly you are trying to achieve!
Why do you need to change/save security permissions in the VISA server settings?
@alexTan132 wrote:
Ok so i was using VISA to communicate with my motors through RS485. When i run my program , i couldnt get any command in , but when i use a calibration software that the brushless motor company provide, i was able to send in the commands and make the motors move. By the way the code that i used was working the week before , and i didnt do any changes to the code, so i think we can safely assume that the code is not the problem.
So here's a summary of what might not be the problem:
1) Brushless motor working fine
2) Code working fine3) Connection cable also ok
You can't "safely assume" that the code is not the problem. Especially in the area of communications, you could've just been "lucky" that it was working before. What I mean is, it could've been correct enough to "usually work", but not correct enough to "always" work. More evidence of this is that the provided application works but yours doesn't. Anyway, the easiest way to determine this is to either link to, or provide, the product manual with the communications protocol, and upload the code that may or may not be working. (Not a picture, but the VI.)
And, last but not least, make sure the other application is closed as only one application can access a serial port at a time.
One thing that you might check, though
@billko wrote:
@alexTan132 wrote:
Ok so i was using VISA to communicate with my motors through RS485. When i run my program , i couldnt get any command in , but when i use a calibration software that the brushless motor company provide, i was able to send in the commands and make the motors move. By the way the code that i used was working the week before , and i didnt do any changes to the code, so i think we can safely assume that the code is not the problem.
So here's a summary of what might not be the problem:
1) Brushless motor working fine
2) Code working fine3) Connection cable also ok
You can't "safely assume" that the code is not the problem. Especially in the area of communications, you could've just been "lucky" that it was working before. What I mean is, it could've been correct enough to "usually work", but not correct enough to "always" work. More evidence of this is that the provided application works but yours doesn't. Anyway, the easiest way to determine this is to either link to, or provide, the product manual with the communications protocol, and upload the code that may or may not be working. (Not a picture, but the VI.)
And, last but not least, make sure the other application is closed as only one application can access a serial port at a time.
One thing that you might check, though
Sorry about leaving you hanging like that. I don't remember what it was I was going to say. Let's see what we have here.
The drive robot vi is missing a lot of subVIs, but it seems fairly innocent to me. There are some things I would do differently, and things that are maybe unneeded. Something that bothers me is I don't really see error handling so who knows what's going on?
