Glad it works
I built the App using my Motorola Moto G, I really need that type of feedback to polish the code
and make it fully usable for other brands with different screen sizes
do you have a paypal account can I buy you a coffee???
I don't drink coffee
Thanks for this kind offer anycase
hi Kas ,
a quick question ,
in your android app what is the cube scan order ? (F THEN R THEN B Etc...)
do i need to set the cube orientation in a particular color order? (put red color in front ,blue color to the left,green color to the right etc...)
Thanks
a quick question ,
in your android app what is the cube scan order ? (F THEN R THEN B Etc...)
Yellow > Red > White > Orange > Blue > Green then back to Yellow
Colors are only for showing scan moves order
Pay special attention to Top & Bottom faces orientation
do i need to set the cube orientation in a particular color order? (put red color in front ,blue color to the left,green color to the right etc...)
i just went through all 22 pages of this project and i wanted to say thanks kas!
your project is totally inspiring. i just got a new arduino kit for my 10 year old son and your cube project is something we're definitely going to work towards.
i might even try to build a 2x2x2 cube solving robot, as i have never seen one of those before!!
i think the programming for it would even be easier than one for a 3x3x3. it uses the same sort
of standards as your project; basic singmaster notation, and has only corner pieces.
thanks again for the great project and inspiration.
Hey Kas. I'm trying to build a similar robot. The only problem i have now is that my servo's do not turn exactly a 90°. They turn like 90° in one direction and 75-80° in another. I'm using a digital Tower Pro MG995. I've seen that you are using Hitec HS-422 which are analog and should be more precise (from their description). Is there any difference between analog and digital. Are HS-422 precise enough? Will they give me a complete 90° turn?
I suspect that your servo's are not covering the full 180° range
Apparently the MG995 can be used as a 'pinch' servo, but is not adequate as 'wrist'
Any 180° servo will be suitable as 'wrist', Hitec HS-422 fits the bill
@WitherKun
Really need more info :
Please post the video as per post #267
First it was giving me this type of error. And i resolve it by adding an arduino.flushInput() string like that. Which i think is some kind of interrupt.
It works perfectly fine and scan all the cube, except the D-face. Even though i've added the same flush.input string.
kas:
"flushInput()" flushes Serial input buffer and discards its contents
This python function is renamed "reset_input_buffer()" in Python V3.x
which Python version are you using ??
which RubikKasBot (python) version ??
which CubeMover (arduino) version ??
You mean you can scan all faces except the last one ?? :o
I'm using CubeMover_13, RubikKasBot V1.3 and Python 3.4.2.
Yes. By adding a flushInput it start scanning, but now it stops on U-face instead. And i did't change nothing from yesterday. And if i change all flushInput with reset_input_buffer it's says that it was not defined, so does inputflush*. So it's a little bit confusing how it works*