21092014 I have made a minor change to TestProgram 3, the main arduino code, the pdf document (updated with code changes).
The code change is to remove the fast dew calculation routine and only use the more accurate one, as speed is not an issue and its probably better to just use the more accurate one anyway, so the faster one has been removed from the code and documentation and testprogram3.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had a chance today to do some current measurements.
Normal = 240ma, 0% pwm power to dew straps and fan off
With DN003 straps connected, oth channels at 100% PWM = 1Amp
According to DewNot, the DN002 straps should draw approximately 0.35Amps each, giving 0.7Amps for both dew straps.
So combining this with around 240milliamps for the controller gives about 940milliamps, very close to the measured current of 1 ampere.
As I will be using the DN007 straps, I will probably go with a lower fuse rating of 3 amps instead of the current 6A fuse that I have fitted to the controller.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have made a slight correction to the getpwr() routine in 255_loc and 280_winx (and then updated the pdf document). The correction involves removing the test at the start of the function for tprobexx == 0, as the getpwr() cannot be called if tprobexx is 0. Potentionally, having these tests there could be an issue if a probe was 0 and the function was called (which can not happen in the main loop anyway) - but just to remove a possible stuff up in case of a later code change?
At present the controller is fine, hardware is working fine, and software working fine, I dont expect any further changes unless there is something I have overlooked.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
20140925 I managed to run the controller live over an evenings imaging session and it has performed above expectations, no dew on the OTA's and no issues. Vibration of the cooling fan not an issue.
Now that the LCD2004 has arrived, I will mount everything in a larger enclosure and use the LCD2004 along with the blue tooth adapter and DHT21 sensor when it arrives. I will post some build pictures once its finished.
The prototype: LCD1602 + DHT11 - I think thats good enough
My final version: LCD2004 + DHT21 + Bluetooth - Overkill is a sort of understatement
Last edit: brownrb 2014-09-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have just created this and started to upload files.
Thanks for viewing.
Robert
21092014 I have made a minor change to TestProgram 3, the main arduino code, the pdf document (updated with code changes).
The code change is to remove the fast dew calculation routine and only use the more accurate one, as speed is not an issue and its probably better to just use the more accurate one anyway, so the faster one has been removed from the code and documentation and testprogram3.
I had a chance today to do some current measurements.
Normal = 240ma, 0% pwm power to dew straps and fan off
With DN003 straps connected, oth channels at 100% PWM = 1Amp
According to DewNot, the DN002 straps should draw approximately 0.35Amps each, giving 0.7Amps for both dew straps.
So combining this with around 240milliamps for the controller gives about 940milliamps, very close to the measured current of 1 ampere.
As I will be using the DN007 straps, I will probably go with a lower fuse rating of 3 amps instead of the current 6A fuse that I have fitted to the controller.
I have made a slight correction to the getpwr() routine in 255_loc and 280_winx (and then updated the pdf document). The correction involves removing the test at the start of the function for tprobexx == 0, as the getpwr() cannot be called if tprobexx is 0. Potentionally, having these tests there could be an issue if a probe was 0 and the function was called (which can not happen in the main loop anyway) - but just to remove a possible stuff up in case of a later code change?
At present the controller is fine, hardware is working fine, and software working fine, I dont expect any further changes unless there is something I have overlooked.
20140925 I managed to run the controller live over an evenings imaging session and it has performed above expectations, no dew on the OTA's and no issues. Vibration of the cooling fan not an issue.
Now that the LCD2004 has arrived, I will mount everything in a larger enclosure and use the LCD2004 along with the blue tooth adapter and DHT21 sensor when it arrives. I will post some build pictures once its finished.
The prototype: LCD1602 + DHT11 - I think thats good enough
My final version: LCD2004 + DHT21 + Bluetooth - Overkill is a sort of understatement
Last edit: brownrb 2014-09-25