{"id":3708,"date":"2019-11-18T00:04:00","date_gmt":"2019-11-17T23:04:00","guid":{"rendered":"http:\/\/dronesonen.usn.no\/?p=3708"},"modified":"2019-12-05T08:22:14","modified_gmt":"2019-12-05T07:22:14","slug":"haptix-week-46","status":"publish","type":"post","link":"https:\/\/dronesonen.usn.no\/?p=3708","title":{"rendered":"Haptix week 46"},"content":{"rendered":"\n

Petter:<\/strong><\/p>\n\n\n\n

\n\nI\u2019m continuing the work on the input system of the cube. It was more comprehensive than anticipated so I have spent my time, discussing and trying out different options as well as gathering info from more experienced users of unity. \n\n<\/p>\n\n\n\n

William:<\/strong> <\/p>\n\n\n\n

\n\nI have done research on how to implement a scoreboard from Unity to a database. Also been working on the scoreboard in Unity, I have an idea how I want it to be implementet and lookwise. We had a meeting on thursday where I had futher discussions with Even. \n\n<\/p>\n\n\n\n

Herman<\/strong> & Tom Erik:<\/strong><\/p>\n\n\n\n

We\u2019ve been discussing the specifics of the physical design elements and obtain all necessary tools. Work is still being done on refining the sensory circuitry of the system.  <\/p>\n\n\n\n

This week Herman and Daniel set up the link between Arduino and\nunity with protocols for communication. We decided that the easiest way was to\nsend a string with several digits to decide which finger that is doing what and\nwhat to do. The first digit describes the finger and the second the Boolean action\nof on or off.  The most natural way to order\nthe fingers would either be between 0-9 or 1-10, but we decided to order them\nafter which pin the corresponded to and therefore scales between 2-11. Example of\nthis would be if you where to say that finger 8 where to touch something the Arduino\nwould receive a message like 9 1 \/n and when the finger detach the Arduino would\nreceive 9 0 \/n. <\/p>\n\n\n\n

The system has been made with some \u201csecurity\u201d measurements,\nwhere it\u2019s a timer in place to shut off the vibration if loss of connection and\nmeasurements to track whether the message was a valid message meant for the Arduino.\n<\/p>\n\n\n\n

Daniel:<\/strong><\/p>\n\n\n\n

For\u00a0this\u00a0week\u00a0I have\u00a0updated\u00a0the\u00a0code\u00a0I\u00a0did\u00a0for\u00a0the\u00a0serial\u00a0controller\u00a0in\u00a0the\u00a0previous\u00a0week.\u00a0Where\u00a0I\u00a0cleaned it up\u00a0through\u00a0such\u00a0as\u00a0PascalCase,\u00a0clear\u00a0naming\u00a0and\u00a0the\u00a0removal\u00a0of\u00a0unecessary\u00a0code.\u00a0Switched\u00a0from\u00a0Queue.synchronized\u00a0to\u00a0ConcurrentQueue. Even\u00a0though\u00a0both\u00a0are\u00a0thread\u00a0safe,\u00a0the\u00a0ConcurrentQueue\u00a0is more\u00a0modern\u00a0and a bit faster (thanks Steven!).\u00a0Furthermore, I\u00a0also\u00a0added\u00a0some\u00a0standarized\u00a0protocols\u00a0for\u00a0the\u00a0communication\u00a0between\u00a0the\u00a0Arduino\u00a0and\u00a0Unity.\u00a0<\/p>\n\n\n\n

The serial controller program can be seen here: <\/p>\n\n\n\n

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

I also bought some white gloves that can be detected by the Leap Motion. As well as write a little .ino program for the Arduino, which could be tested on the debug platform<\/a> I built with LED lights. In order to test the scripts that were written for Unity application. A video for this can be seen here:<\/p>\n\n\n\n

\n