tkristof
Hello!
We are a hungarian father and his son (sorry for my poor english). I bought a EZ-Robot Hexapod for my son, who is interested in it. I bought it from ebay. Unfortunatelly the seller suck me in - as it was advertised as new, and what we got was opened original box and 2 pcs. cracked house servos. It was the begining of our story.
I'm a hardware development engineer, so I understand what the Hexapod does and why it is working and how ...
There are several problems what we don't understand, I list it:
We power on the Six, we connecting - it is working. After a simple movement/action the Six's 1 servo frequently vibrate and give rattling sound - not always the same. If I touch it with my finger I feel which one is vibrating. Is it normal? If I fine tuning the servos for 90, then the problem still exists. What can I do with this?
I try the tracking function of the camera. I trained an object by Six, and if I try Six tracking this object it is locking the object and sometimes Six turn away about 30-40 from the locked object. What I do wrong?
Mobile app We have mobiles and tablets with several screen LCD resolution, but the deafult mobile app doesn't display perfectly on the screen, for example the left, forward, reverse, right buttons and main background image is not square rather rhombus. What do I wrong? OR why I can't change the main's width and height 800x480 pixels?
Can the servo's fine tuning values loading on power on to the Six? We tried to calibrate the servos, but 2-3 couldn't set by mechanically, only by fine tuning.
So, that are the first problems for us. Could you help us?
PS: we live in Hungary/Europe, how can we buy servo for good price? The price is ok, but the shipping charges are very high, for example from Brookstone the shipping and custom charges are 3x more then the servo's price!
Best regards: Zsolt Tóth
Guys!
I ask who was Hexapod: what time it can play with till battery discharging at 6,6V? It seems to me that this time is 1/2h appr.
Dear Alan!
Mobile devices we have problems: Jiayu G5 mobile phone (4.5 "IPS OGS HD (1280 × 720, 326PPI) Gorilla Glass 2), Vido N70HD tablet ( 7" IPS HD (1280 × 720)), Teclast X98 Air 3G tablet (9.7-inch IPS IGZO Retina display with a resolution of 2048x1536)
On our devices we couldn't reach the right side of the application, because it oversized the screen, we can only scroll up and down but not left or right: Mobile app
Here are my devices:
Any idea?
Thank you.
Due to lack of standardization of android devices, it is impossible ez-robot (or any app developer) to verify compatibility. As you can see from using this product and joining the community, no one has ever experienced a similar issue. This leaves the issue isolated to your device.
I would recommend verifying the device has not been modified and settings to the display DPI is original state. If you are unsure, a factory reset to default settings is recommended.
Thank you for your answer. I tried to change the DPI earlier but no resolution...
That is unfortunate - i will add a note to see if there is anything that can be done from our side for the next release of ARC mobile.
@tkristof Hello, and welcome.
Have you tried pinching in on the image to insure it is not accidentally expanded?
As a temporary solution you could resize the layout of the mobile window. Every component is fully adjustable, including the font. The only thing that is not is the background image. This image gives the direction buttons that blue diamond shape background. You can delete that. That way the background will not be off in relationship to the buttons.
After that you can make all the other controls smaller and bring them closer together so that they can all appear within the screen area of the tablet. Of course you don't want to make things too small, but a little off each can add up. To keep from making the font too small to read in smaller button boxes you could abbreviate some of the longer texts. Plus you can make some two lines instead of one, making the buttons more like a square than a rectangle.
The Camera screen area can be made smaller and the sliders could be moved under the buttons in the upper right area. That would allow you to move the buttons in the lower right area under the video screen area. Some of those buttons could also be moved under the sliders to allow the mobile window to be smaller in height. And, naturally, you can simply eliminate some buttons you are not that fond of.
Just a few suggestions. I'm sure you can figure it all out. Basically, make things fit whatever the screen resolution is for each device.
I believe each device can have it's own, individual copy of the mobile screen, so you could upload a different one for each tablet.
@wbs - that's what is strange... the screen resolution that is returned by the device is used as a multiplier for all objects. The dimension of ARC mobile apps is 800x480. No matter what the resolution is of the mobile device, the code uses a multiplier.
so if your button is 100x100 pixels in ARC, and the resolution of your device is 1600x960, the multiplier would be 2, which makes the button 200x200 on the device.
It's a very simple calculation that is performed on all objects - which is why the same mobile app works across most mobile devices and tablets... and why this is the first time anyone has had this experience.
The only thing i can think of why this particular Android device is displaying incorrectly is due to the driver returning the incorrect size of the display - which should be impossible. However, who knows what issues exist in that particular android version because there is absolutely no requirement/control of android distributions. That's why mobile developers have a difficult challenge supporting android devices.
I'm mostly confused of how this can be displaying so strangely on two separate devices... confused
@DJSures
I see. So it should be adjusting itself to whatever the resolution is (or says it is). But, does that explain why the direction buttons are offset from the blue diamond background? Regardless of what it says vs what the real resolution is, should it not have adjusted itself such that they would stay in alignment?