I have built several Adventure Bots and have not had any issues, but when I tried to build a custom 2 WD robot using IoTiny I've run into a strange problem.
Using the same "continuous rotation servo with Wheel" set from my Adventure Bot I found that they worked for about a minute before refusing to run any more.
I thought it might be just a coincidence, so I took another working set and first tried that with a EZ-B v4 controller in a Power Shell with the same "LiPo Robot battery" (after a full recharge) that I was using on IoTiny ... and those wheels worked fine
But, when I connected the wheels back to the IoTiny, the servos worked for a little while and then stopped working!
What's worse, is that I reconnected the servos back into the Adventure Bot and NONE of then worked anymore.
Any ideas?
Frank
@faengelm,
Can you post your project.
And the actions to replicate the issue.
i really don't have a saved project. I just use AdventureBot Bare
The only action is to click forward, stop and reverse on the servo movement panel
I try this with. V4 controller and then Iotiny. Servers work until IoTiny runs them
Have you put a meter on the voltage and ground of the servo ports to check the voltage there. It sure seems like head scratcher!
I'll do some testing on this today. I'll let you know what I find.
FYI My test was with the old resin gear 360 servos... Maybe there is a difference between the old resin gear servos and the new metal gear 360 servos? Anyway, I just ordered 2 developer's kits so I will test again when I get the new 360 metal gear servos...
@JustinRatliff That was a great idea!
I connected a voltmeter to the power and ground pins on a servo port.
During my v4 tests and found the readings to be stable, but very unstable when using the IoTiny
Here are some videos showing what I experienced using same battery and cable I used with the v4
Any ideas what could be causing this?
Regards, Frank
@Frank, That is head scratcher! One more test idea, what about meter testing it under no load? Scripting wise, still send the control signals, just don't connect a servo on the port.
And then maybe try a metered test on another I/0 port, again sending control signals to the port with no servo connected.
@Jeremie, is there a check list to check the I/o tiny with a meter for proper voltagages or continuity like there is for EZbv3? EZBv3 Diagnostics If not do you think you might be able to help us come up with one?
Hey guys,
I figured it out, but I gotta run. I'll let @DJ fill you guys in!
Oh and the IoTiny Datasheet is almost complete, it's just being edited and reviewed before release. It'll definitely help with diagnostics.