US Customer Issues by 05 March 2018

[SzymonDzw]

Here's your list of issues regarding the rover interface that was noted by our US020 and US021 customer.

• There was a problem with understanding that you need to place your finger on the crosshair and then move it to the direction you want. Cannot push where and how fast you want to go.
• Rover should be driven using WASD or arrows when used on laptop.
• Robotic arm seems buggy, shakes and moves really slow - inverse kinematics is too buggy. Reimplement inverse kinematics #20
• After switching to robotic arm and turning advanced interface on, there are frozen '0%' parameters near the crosshair (see attached).
  
• Sometimes camera doesn't turn on streaming when logging in, rover needs restarting.
• It's hard to know when the rover records video and when not, there's no difference in the icon and no notification. Bring back video recording #21
• There's a certain position when the arm can be jammed (see attachment).
  

[Mictronics]

Regarding your remarks, some input from my side:
2) You may implement game pad support and recommend this to your customers. This is a much more comfortable control experience than keyboard or even touchscreen.

3. and 7) Pick up software development of your rover hat board again. Implement a ramp up/down function for motors and servos. Let the control device only provide desired set points to the rover hat. Maintain control loop timing, limitation etc. in the hat's microchip. This way your rover hardware is independent from the control device and connection.

[stsdc]

This way your rover hardware is independent from the control device and connection.

I also thought about this, need to discuss with the team.

But if possible could You please write every single proposition in separate issue?
Here is a repository for embedded Turtle software