|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Maxbotix US "digital" example. (XL EZ1)
Here's a funny situation. We run the example and it works perfectly. But when we copy the code into our robot code, or create itvmanually, it's no longer works. We have the address's is set properly, but still no go.Has anyone else ever experienced this?
|
|
#2
|
|||||
|
|||||
|
Re: Maxbotix US "digital" example. (XL EZ1)
How are you copying it to your robot code? Make sure you understand what parts of the example go into which VIs in the robot project. See Tutorial 7 - Integrating Examples into Robot Code.
|
|
#3
|
||||
|
||||
|
Re: Maxbotix US "digital" example. (XL EZ1)
Quote:
It is quite perplexing! |
|
#4
|
||||
|
||||
|
Re: Maxbotix US "digital" example. (XL EZ1)
We switched over to Analog sampling and now have reliable sub inch accuracy.
I still don't know why the "Digital" Pulse width sampling only works in the example. At this point in the build season, as long as we have a reliable measurement, we are satisfied. Maybe after the build is finished we will have time to investigate further. |
|
#5
|
|||
|
|||
|
Re: Maxbotix US "digital" example. (XL EZ1)
Please let us know if you figure out what it was.
Greg McKaskle |
|
#6
|
||||
|
||||
|
Re: Maxbotix US "digital" example. (XL EZ1)
Quote:
This time around, I built the code from scratch using the example as a guide, not my student. Obviously he did something incorrectly, but I watched him do it and it looked correct to me....at the time. The only thing I can think of is, he might have used a Digital Set RefNum instead of a Timer Set RefNum. Oh well, at least we now have two reliable ways to measure distance. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|