Asked — Edited
Resolved Resolved by Dunning-Kruger!

Sensors Dont Works On Robot (Bioloid)

i know this is not ez robot but i though to ask to understand why they are not working. i f you set sensors like in the videi separt they do works.


ARC Pro

Upgrade to ARC Pro

Unlock the true power of automation and robotics by becoming a proud subscriber of Synthiam ARC Pro.

#9  

That's weird.... so you get feedback from the IR in the software... ? Since I am not familiar with bioloid I can only guess.... Do you need to do any programming to make him turn or do whatever when he sees an object or is he already programmed to do it automatically? Have you tried re-booting everything including the bioloid robot? Not sure what else I can suggest...

#10  

Ok... try changing the code a little.... sorry not that familiar with this type of coding... but You have your code >=40 and >=50 What happens if you change it to <=50 and <=40 instead?

PRO
Belgium
#11  

in the pic.you see the distants50 and 40 and 40 the lower value the further away is the object. the higher the value ,the chorter is the object.

50 is about 20 cm away from the sensor.

the program itself says the sensors are not good for precies distands. also have alot influance whit chades&lights

but my exsperiance telling me,its not working at all on a robot. as you see the above video,they work only separt. reason more to choose EZ ROBOTS haha

PRO
Belgium
#12  

i did try all from lowest value to highgest value .from 10 to250 value.

PRO
Belgium
#14  

no i didn see this one. due to that ax-s1 is connected like any servo.it dont have a port. but am gonna check it for sure

under the number 40 or 50 you see jumpto left or right,that what he chould do. its preprogrammed allreddy in the software.

#15  

Is there a way to put break points in your code that would allow you to step through the code and check the variables one step at a time? If so, I would start there. If not, I would start a new project with only one command to check a single sensor and return the value. Most of the time that things like this happen, it is a silly mistake and verifying that the sensor is actually working will help diagnose if it is a coding issue or a sensor issue.

#16  

Also, you may not be retrieving the data before trying to take an action on it. I don't see all of the code so I don't know. Also, I am unfamiliar with this product. Just trying to help point you to something that could be helpful.