{"id":3740,"date":"2019-11-25T00:09:37","date_gmt":"2019-11-24T23:09:37","guid":{"rendered":"http:\/\/dronesonen.usn.no\/?p=3740"},"modified":"2019-12-05T08:22:14","modified_gmt":"2019-12-05T07:22:14","slug":"haptix-week-47","status":"publish","type":"post","link":"https:\/\/dronesonen.usn.no\/?p=3740","title":{"rendered":"Haptix week 47"},"content":{"rendered":"\n

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

Because of my issues with the input system I went and talked to Steven about possible solutions, he ended up giving me new ideas and perspectives. <\/p>\n\n\n\n

I ended up redoing the cube completely because of this and after 3 days compared to four weeks of work, I have a working prototype, which is frankly better in all ways compared to the old one. For a rough outline on how my thought process went:  <\/p>\n\n\n\n

First, Steven and I categorised the options: <\/p>\n\n\n\n

9 layers x 2 for + – = 18 options <\/p>\n\n\n\n

27 total pieces, including middle piece <\/p>\n\n\n\n

If we exclude middle because it can’t be seen, therefore should not be touched:  <\/p>\n\n\n\n

6 layers have 9 pieces <\/p>\n\n\n\n

3 layers have 8 pieces, these three layers are the center layers, and are the only three layers which exceptions may be made for. <\/p>\n\n\n\n

Middle pieces never change their parallel position compared to each other, which means we can use them to identify which pieces are currently in the vicinity. <\/p>\n\n\n\n

I\u2019m gonna simplify the solution a lot for right now, both because it\u2019s very difficult to explain and because I still need to do some more testing, which means it might change, I\u2019ll do a full code walkthrough later. Anyways so: <\/p>\n\n\n\n

Give each middle piece a large layer sized box collider. <\/p>\n\n\n\n

This box collider can be used to gather the surrounding pieces. As well as register touch. <\/p>\n\n\n\n

The remaining pieces (20) will be kept in the main parent and not used before they must be. <\/p>\n\n\n\n

For the touch solution: <\/p>\n\n\n\n

Movement will only be allowed on the last layer parallel to the two others touched. The last layer can be turned by touching it and rotating any angle(x,y,z) by more than 45 degrees while still having one finger touching the side to be turned, the rotational direction is decided by whether the change is pos or neg or just tightening the fist and rotating it +-45 degrees. <\/p>\n\n\n\n

Parallel layers can be hard defined in code and the layer ready to be turned is highlighted. <\/p>\n\n\n\n

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

I am now done with the tutorial part in Unity (On how to solve a Rubiks Cube). The scoreboard is still beeing worked on. <\/p>\n\n\n\n

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

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

The communication between the master hub and the slaves at\nthe gloves is somewhat complete. For test purposes I have used led diodes for\nthe vibration motors. Here it parses the information given and checks if it\u2019s numeric.\n It reads it as bytes and check for \/n as\nthe end bit. <\/p>\n\n\n\n

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

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWhen\nthe system sees the start bit (0) it starts to check if the message wants to\nact on a finger that do exist, here we have numbered them 2-11 after which pins\nit connects. So, if it is the right hand (2-6) it will send the message forward\nto unit 1, or if it is the left hand (7-11) it sends the message to unit 2\n\n\n\n<\/p>\n\n\n\n

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

If an error occurs along the way it sends back an error code to the unity script. <\/p>\n\n\n\n

The scrpit for the gloves are base on the same idea, only here we remove sending the message further and rather execute the \u201cdigitalWrite(data_buf[FINGER_ID], data_buf[FINGER_ACT]);\u201d line <\/p>\n\n\n\n

What is missing now is to adjust it\nfor wireless connection and to add more measurement to ensure that nothing fails\nduring use, such as timers for timeout from unity, if the motors are still\ngoing when it shouldn\u2019t and so on. <\/p>\n\n\n\n

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

Assembled and wired up the glove. To further optimize spacing, I\u2019ll look into designing a pcb for the circuit. <\/p>\n\n\n\n

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

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

For this week I have continued on the Unity test application for the Haptic gloves. Where I have enlarged the environment in the main scene, both by implementing new objects and music. My idea was to create a narrative of being in the American Old West.

In order to achieve this, I figured that I could carry on with the Low Poly graphics. Upgraded the scene with some assets for a Low Poly Western Saloon<\/a>. Added some clouds<\/a> in the background and imported some music into the scene.<\/p>\n\n\n\n

As the user of the application you are placed into a chair in the saloon. From there on out, you will hear some Western music in the background. While also being able to both look around with the VR headset and interact with the nearby objects.<\/p>\n\n\n\n

\n