Well, my cool idea is shot then. :-( So there is a connection for another probe inside that is not used?
No thats not me in the video.Is that your video? All I can think watching the little bit I did was that guys is tossing that thing round and pointing at stuff with a screw driver while he has mains power connected to it!
What was your idea. While the STC doesn't know if current is flowing through the relays it does know that it is allowing current to flow (and you can then assume that it is flowing given that you have correctly wired everything else)
I want to know what your plan is??????
The idea I have is for use with HERMS setups and two units are used in conjunction. One will power the heating element in the HLT and have its temp sensor in the HLT. The other will power the pump that circulates wort through the HERMS in the HLT to heat the mash and of course will have the probe in the MT...
...Another variable that could be added is MASH TIME. The 45 in my listed program could then be changed to MASH TIME -15. And that would only be set on the MT control of course.
Step mashes could also be added and variables setup for them. Programming (for the brewer) would be super simple as the only entries that would need to be made are the variables.
so I soldered a usb to uart bridge (CP2102) to a mini and I am a little confused. Got the drivers for the 2102 loaded but that is all that is showing up in my device manager. Not the mini. I guess that is ok? Seems like the sketch uploaded to the mini (or to somewhere). I will take a chance and try to program the STC now....
...
* buffer. If you should use another software that does not have this feature you may
* need to lower the baudrate significantly.
*
*/
/* Define STC-1000+ version number (XYY, X=major, YY=minor) and EEROM revision */
#define STC1000PI_MAGIC_F 0x196E
#define STC1000PI_MAGIC_C 0x2691
#define STC1000PI_VERSION 100
#define STC1000PI_EEPROM_VERSION 10
When I download picprog.ino from work branch the file show:
Code:... * buffer. If you should use another software that does not have this feature you may * need to lower the baudrate significantly. * */ /* Define STC-1000+ version number (XYY, X=major, YY=minor) and EEROM revision */ #define STC1000PI_MAGIC_F 0x196E #define STC1000PI_MAGIC_C 0x2691 #define STC1000PI_VERSION 100 #define STC1000PI_EEPROM_VERSION 10
But after flashing and doublepress the STC show 1.06 in display.. and the simulate html has other settings. Am I on wrong file?
Is it possible to give I and P more weight? Done some testing and end up with 999 and 99 (3-4l flow, 20kg, 2500w)
Ok, I will ignore the cooling led but the heat output doesn't seem to fire. I left the configuration that I programmed it with, with the exception of Setpoint 0. I set it higher than the sensor temp by 20 degrees and waited but the heat output relay didn't fire it seems. Should I just reflash in Celcius mode and do some testing? I would love the fahrenheit option but I can convert for now.
As a temporary workaround, would it be time consuming to modify a few lines of code in the + version (fermentation control) to operate in minutes instead of hours?
As far as the PID features, RIMS/HERMS system design contributes most of the potential errors imo. For example, placing a temp prob in the center of the grainbed for control of a RIMS heater would create such a wild temp swing potential that even a PID algorythm would have trouble "figuring" it out. Sensing the wort temp imediately leaving the heater would have a much tighter swing potential and should keep the grainbed at a pretty predictable temp.
I guess I am wondering if the PID capability is worth all the trouble?
Will be building a setup to help specifically with dev. I have an A400_P, the + firmware worked on it so I can only assume it will work on this...
Enter your email address to join: