Updated the jpeg file and README
This commit is contained in:
parent
2cbd3fff2f
commit
89dc55bf44
@ -21,3 +21,5 @@ The hardware should be reasonably self explanatory. A few notes:
|
|||||||
- The outputs PB3, PC0 and PC4 are used to control the backlight of the LCD, which gives us 8 luminance values. Some resistors are put in series, the reason was availability of the specific values. A single PWM output could also be used instead, but it wouldn't work during sleep of the microcontroller.
|
- The outputs PB3, PC0 and PC4 are used to control the backlight of the LCD, which gives us 8 luminance values. Some resistors are put in series, the reason was availability of the specific values. A single PWM output could also be used instead, but it wouldn't work during sleep of the microcontroller.
|
||||||
- The LED (connected to PB5) is also used as a light sensor and can be used to control the LCD backlight intensity. This is achieved by pulling the normal LED output PB5 to LOW, the PE2 output to HIGH, so that the LED is connected in reverse. Then the voltage is taken away and the ADC of PE2 is used to measure how much the voltage has dropped in a certain amount of time (5ms). The more light, the faster the voltage drops. This works best with red LED's, and worst with blue LED's. A blue LED can be used but it will already give a "dark" output in twilight.
|
- The LED (connected to PB5) is also used as a light sensor and can be used to control the LCD backlight intensity. This is achieved by pulling the normal LED output PB5 to LOW, the PE2 output to HIGH, so that the LED is connected in reverse. Then the voltage is taken away and the ADC of PE2 is used to measure how much the voltage has dropped in a certain amount of time (5ms). The more light, the faster the voltage drops. This works best with red LED's, and worst with blue LED's. A blue LED can be used but it will already give a "dark" output in twilight.
|
||||||
- The microcontroller does not use a crystal but instead uses its own internal oscillator. ***Be very careful if you set the fuses / upload a bootloader, if you set the oscillator/clockspeed to EXTERNAL you brick the ThermalOptimizer!*** The external crystal outputs are left unused in this design, so in theory it should be possible to connect a temporary crystal to unbrick the microcontroller, but it will be very difficult as the board is not designed for this. The clockspeed should be (at least) 4MHz to reliably read out the digital temperature sensors. Higher clockspeeds than 4MHz offer no advantage in the existing software applications but just consume more power.
|
- The microcontroller does not use a crystal but instead uses its own internal oscillator. ***Be very careful if you set the fuses / upload a bootloader, if you set the oscillator/clockspeed to EXTERNAL you brick the ThermalOptimizer!*** The external crystal outputs are left unused in this design, so in theory it should be possible to connect a temporary crystal to unbrick the microcontroller, but it will be very difficult as the board is not designed for this. The clockspeed should be (at least) 4MHz to reliably read out the digital temperature sensors. Higher clockspeeds than 4MHz offer no advantage in the existing software applications but just consume more power.
|
||||||
|
- Starting from version 1.3 there is a provision to add a crystal to the PCB but it is normally not installed (ask us for options if you need it). A crystal would be useful if you want to use reliable RS232 communications.
|
||||||
|
- Starting from version 1.3 there is an option to connect a 3 or 4 pin computer fan, to control the RPM and to read it back, but it uses the serial port pins so you can not use it simultaneously with the serial input and output.
|
||||||
|
|||||||
Binary file not shown.
|
Before Width: | Height: | Size: 174 KiB After Width: | Height: | Size: 212 KiB |
Loading…
Reference in New Issue
Block a user