Skip to content
Snippets Groups Projects
Commit f0fe3e18 authored by ybarhoush's avatar ybarhoush
Browse files

images fix for week08

parent 1aa1dcba
Branches
No related tags found
No related merge requests found
Pipeline #194572 passed
...@@ -23,7 +23,7 @@ It allows for *parametric modelling* where modifications at anytime and reflecte ...@@ -23,7 +23,7 @@ It allows for *parametric modelling* where modifications at anytime and reflecte
Modify > Change parameters Modify > Change parameters
![0](../images/week08/design/0.png) ![0](../images/week08/design/0.jpg)
* Create 1st Side (Sketch) * Create 1st Side (Sketch)
...@@ -301,6 +301,8 @@ Animation shows 2D Contour Settings ...@@ -301,6 +301,8 @@ Animation shows 2D Contour Settings
#### Simulation #### Simulation
![sim](../images/week08/design/sim.jpg)
Generate the .nc file Generate the .nc file
ACTION > Post Process ACTION > Post Process
......
...@@ -400,7 +400,7 @@ void loop() { ...@@ -400,7 +400,7 @@ void loop() {
!!! note !!! note
A pull-up resistor was used in the Arduino code: a high state was needed as default (to match with the Unity implementation) and then changed to Low by the Unity Script Interaction. This can also be flipped, but modifications on Unity's are also needed. A pull-up resistor was used in the Arduino code: a high state was needed as default (to match with the Unity implementation) and then changed to Low by the Unity Script Interaction. This can also be flipped, but modifications on Unity's are also needed.
Additionally, the numbers for defining the *threshold* are arbitrary. Since the values coming from the Joystick are Analog, and the input in Unity is defined to be Digital. A future implementation should define inputs as Analog on Unity's Side. Additionally, the numbers for defining the *threshold* are not arbitrary. Since the values coming from the Joystick are Analog and the input in Unity is defined to be Digital, couple values were experimented with till the *threshold* was found. A future implementation should define inputs as Analog on Unity's Side.
Connect the controller to PC using the FTDI cable. Then, modify the SampleMessageListner to work with CustomDevice.cs. The msg in the SampleMessageListner.cs Script is the packets sent from the board to the PC via the FTDI cable! Connect the controller to PC using the FTDI cable. Then, modify the SampleMessageListner to work with CustomDevice.cs. The msg in the SampleMessageListner.cs Script is the packets sent from the board to the PC via the FTDI cable!
......
docs/images/week08/design/0.jpg

94.5 KiB

docs/images/week08/design/sim.jpg

345 KiB

File added
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment