Commit 31840352 authored by Philip Hozier's avatar Philip Hozier
Browse files

Week10 - final 3/5

parent f70f5ade
Pipeline #228266 passed with stages
in 13 seconds
......@@ -168,7 +168,7 @@ So I need to compare the 2 different micro-controllers and translate what the 45
**BOM**
TO be ultra safe have as much support as possible, its probably best to try and source the components from the [Fab Academy electronics inventory](https://docs.google.com/spreadsheets/d/1U-jcBWOJEjBT5A0N84IUubtcHKMEMtndQPLCkZCkVsU/edit#gid=0)
To be ultra-safe and have as much support as possible, its probably best to try and source the components from the [Fab Academy electronics inventory](https://docs.google.com/spreadsheets/d/1U-jcBWOJEjBT5A0N84IUubtcHKMEMtndQPLCkZCkVsU/edit#gid=0)
| **COMPONENT** | **DESCRIPTION** | **DATA SHEET** | **SPECIFICATIONS** |
|---|----|---|----|
......@@ -241,27 +241,35 @@ Overall, the soldering was the easiest and least 'mistake' prone part of this pr
![Individual Assignment](../week10/week10-hero2.jpg "Board Testing")
A visual test with a loupe could only see how neat the soldering was. There looked to be no accidental shorts due to excessive solder use. But impossible to see under the sensor. Continuity testing of all the tracks and pins of the components that i could see showed that the soldering was successful. Next to the sensor the tiniest of pads was visible so i tried to see if they were connected properly with the probes. The SDa and SCl tracks and pins ran up the board underneath the Attiny412, so I knew that no accidental connection had been made across from one side of the sensor to the other. Those meant to be connected from one side of the sensor to the other connected fine. *UPDATE* HOWEVER! Pin 3 on the sensor that shouldn't be connected to anything, made a beep :( when one probe touched other tacks on the board. So it look all my steps to use the minimal amount of solder didn't quite work (or the positioning isn't quite straight) and a short is present under the sensor.
A visual test with a loupe could only see how neat the soldering was. There looked to be no accidental shorts due to excessive solder use. But impossible to see under the sensor. Continuity testing of all the tracks and pins of the components that i could see showed that the soldering was successful. Next to the sensor the tiniest of pads was visible so i tried to see if they were connected properly with the probes. The SDa and SCl tracks and pins ran up the board underneath the ATtiny412, so I knew that no accidental connection had been made across from one side of the sensor to the other. Those meant to be connected from one side of the sensor to the other connected fine. *UPDATE* HOWEVER! Pin 3 on the sensor that shouldn't be connected to anything, made a beep :( when one probe touched other tacks on the board. So it look all my steps to use the minimal amount of solder didn't quite work (or the positioning isn't quite straight) and a short is present under the sensor.
I even had a look at the board under the microscope camera to see any problems. Fascinating to see, but shows me nothing to concern me.
![Individual Assignment](../week10/microscope-camera.jpg "microscope camera view")
*UPDATE*
I will try to reheat the sensor with a heat gun again and see some solder will flow away. Otherwise it looks like I will have to remove, clean and re-attempt to re-attach the sensor to the board.
Attaching my board to a UPDI and another USB device for the power lead. Used Apple System profiler to look at the USB connections. I also double checked these by running the this command in Terminal.
> ls /dev/tty*
Reheating the sensor with a heat gun again to see if some of the very small amount of solder use can flow away. This worked as a continuity test 'sounded' that there was no connection between the sensors pins any more. :)
Only the UPDI and Serial device giving the power to the board confirming that they can be seen, and any problems i have are restricted to the new board.
To check if the IDE could see the ATtiny412 on the board anyway I worked through the list of ports that Arduino IDE could see on my computer (**Tools** > **Port**) and tried to see what information it would give on the attached device with 'Get Board Info' (**Tools** > **Get Board Info**).
In preparation for a working board, When i can measure some data coming out of the sensor. I downloaded and installed the [Adafruit ADXL343 Accelerometer library](https://github.com/adafruit/Adafruit_ADXL343 "Adafruit ADXL343 library") to my Arduino IDE.
It showed that an ATtiny412 chip was present. :)
To check if the IDE could see the ATtiny412 on the board anyway I worked through the list of ports that Arduino IDE could see on my computer (**Tools** > **Port**) and tried to see what information it would give on the attached device with 'Get Board Info' (**Tools** > **Get Board Info**).
In preparation for a working board, When i can measure some data coming out of the sensor. I had downloaded and installed the [Adafruit ADXL343 Accelerometer library](https://github.com/adafruit/Adafruit_ADXL343 "Adafruit ADXL343 library") to my Arduino IDE. This would be used in the programming once the board had successfully responded to me in Serial.
Due to the lack of serial (and any output feedback functionality), I borrowed some special probes from Henk to attach directly to the Rx and Tx pins of the ATtiny 412.
I uploaded a sketch to test if there was any Serial communication coming out. And there was!! :)
![Individual Assignment](../week10/3Axis-serial.jpg "Serial Ouput")
Alas nothing for my new board (as expected at this time).
The values were very close together no matter what axis I shook the board in. From 1016-1018, which was at the high end of an analogue value. I could find nothing in the data sheet of the sensor to give me any clue as to what output to expect, so I assumed it would mean something when used in conjunction with the Adafruit library. ( I know now that its probably more to do with not using the right protocol and physical pins).
I opened up the example sketch that comes with the installation, I modified the 'defined' pins (MOSI, MISO, CS) to correspond with my ATTtiny412 communication (SDA/ SCL and CS). Once i have tried to fix the board I will start testing the code.
However, I could no replicate the results of the serial output again. The board had effectively stopped talking serial for some reason. I was advised to 'move on' to the current assignment as i had effectively got some reading out of the input as the assignment required. Just it wasn't going progress much further.
So here is the code i had tried to modify from the example that came with the Adafruit library, if the board had worked.
I modified the 'defined' pins (MOSI, MISO, CS) to correspond with my ATTtiny412 communication (SDA/ SCL and CS). Once i have tried to fix the board I will start testing the code.
![Individual Assignment](../week10/3-axis-sketch.jpg "Accelerometer sketch")
......@@ -273,6 +281,8 @@ I opened up the example sketch that comes with the installation, I modified the
- Probably used a fresh new copper board that is more likely to be flat than using a half used one from the box of part used boards.
- Added some serial output pins to debug.
---
## Mistakes & Issues
---
......@@ -343,6 +353,13 @@ I thought i had overcome the bad luck and all the possible problems you could ha
See [week 4](../week4/ "Week 4") for more milling problems.
*UPDATE*
**Adding serial pins to the design**
I was wrong in the assumption that 'communication' tracks could be used between different protocols. Especially a Rx UPDI line could be used as a serial Rx line if assigned in the embedded programming.
**SPI or I2C**
With my knowledge at the time (or lack of networking and communication protocols to be exact), I didn't know that the sensor would need special pins for communicating. I thought serial output would be enough. It spoke in SPI or I2C, which I was advised to wait for that teaching week before i go down that rabbit-hole. which meant, unbeknownst to me, I was going to fail that week whatever i tried.
---
## CONCLUSION
---
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment