{"id":1674,"date":"2020-10-24T09:17:32","date_gmt":"2020-10-24T08:17:32","guid":{"rendered":"https:\/\/ofalcao.pt\/blog\/?p=1674"},"modified":"2020-10-24T10:47:16","modified_gmt":"2020-10-24T09:47:16","slug":"committed-to-pybricks","status":"publish","type":"post","link":"https:\/\/ofalcao.pt\/blog\/2020\/committed-to-pybricks","title":{"rendered":"Committed to Pybricks"},"content":{"rendered":"\n

So I committed 2 files<\/a> to the Pybricks<\/a> project:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

not really to the project code but with a demo project that shows how to use the new ‘getchar’ function to pass commands from the Pybricks Chrome IDE to the hub in runtime.<\/p>\n\n\n\n

‘getchar<\/a>‘ works like the standard ‘input’ function but is doesn’t wait for ENTER so it is non-blocking. I already used ‘input’<\/a> to send commands to the Top Gear Rally Car and from the ‘client’ side (my EV3 python script) the only difference is not having to send a carriage return any more but from the hub side the responsiveness of the code should be now much better.<\/p>\n\n\n\n

from pybricks.experimental import getchar\n\nwhile True:\n    c = getchar()\n    if c == ord('a'):\n        print('You pressed a! Now drive forwards...')\n    elif c == ord('b'):\n        print('You pressed b! Self destruct in 3, 2, 1...')<\/code><\/pre>\n\n\n\n
Another advantage of ‘getchar’ is allowing me to use Nordic nRF Toolbox UART tool to send commands to the hub:<\/p>\n\n\n\n
\n
https:\/\/cyberxstuff.tumblr.com\/post\/632845645520175104<\/a><\/div>