Tetris for TS100, scripting system and more!

joric

Wrote Tetris for TS100: https://github.com/joric/ts100tris
There's also a scripting branch I just started and I'm currently trying to figure out how to implement screen autorotation. I need some help with an accelerometer - it seems that coordinates other than X don't change at all (Y and Z are static in 2.17), also there's a problem how to differentiate left and right tilt. I think there's a bug in the accelerometer handling code. Has anyone managed to get proper 3d values from it? Also I know I can switch between screen orientations in the menu but I'd love to see the accelerometer-driven autorotation feature in the stock firmware, will it ever be rolled out? Thanks.

joric

[i = s] posts by joric in 2017-7-9 23:40 Edit

[i = s] posts by joric in 2017-7-9 23:13 Edit  

Found accelerometer mod that correcly shows all three coordinates (replace stock MMA8652FC.* with its ones): Firmware of TS100 single button operation(accelerated sensors application). Looks like tilt can be determined using its Get_XYZDrt function, e.g. own_sprintf(str,"%d %d %d", Get_XYZDrt(AXIS_X), Get_XYZDrt(AXIS_Y), Get_XYZDrt(AXIS_Z)) shows "1 1 0" with left tilt and "1 0 0" with right tilt. I suggest adding these accelerometer fixes in the next firmware release. I've personally got a working screen autorotation in this branch: https://github.com/joric/ts100tris/tree/autorotate

joric

After examination looks like all the difference is riight here:

1. @@ -170,8 +185,8 @@
   
2.                  gY_value.Byte.lo = value[3];
   
3.                  gZ_value.Byte.hi = value[4];
   
4.                  gZ_value.Byte.lo = value[5];
   
5. -                return 1;
   
6.              }
   
7. +            return 1;
   
8.          } else
   
9.              return 0;
   
10.      }
    

复制代码

This teeny tiny change enables all the 3 dimensions. There's no change in initialization or the reading sequence, just that. I guess someone has broken it by mistake a long while ago.

joric

Forgot to add, axis direction (e.g. Y) can be obtained as "return gY_value.Byte.hi>0x7f ? 1:0;" The mod above uses it as a separate function but the stock firmware just ditches it. I guess it would be much more convenient to work with signed values but ofc it's up to Celery@minidso.

ny!

You're very creative!  The (x, y) coordinates that are being obtained are to determine whether or not to move it, so the value that you get is just an approximate, it's not exactly a 3d value.

ny!

joric 发表于 2017-7-10 01:18
Forgot to add, axis direction (e.g. Y) can be obtained as "return gY_value.Byte.hi>0x7f ? 1:0;" The  ...

Well, it's something that can be tried by approximations.
Some processing is done through the coordinates to determine whether to move left or right.

joric

Not when someone has deliberately removed the sign from the number, no. There's no possible way to determine if you touched the zero and turned back right after or crossed the zero and went to the other side. Aanyway, there's no need to guess because signs are obtainable it's just API that's shitty.

ny!

The acceleration sensor model is MMA8652FC