- Joined
- Oct 25, 2008
- Messages
- 146
- Reaction score
- 22
I found the issue. The was a pin inside the sensor that was touching the housing causing a short.That reads around 40F with a 100ohm resistor.
I found the issue. The was a pin inside the sensor that was touching the housing causing a short.That reads around 40F with a 100ohm resistor.
Sounds about right. 40 F is pretty close to 0 C.That reads around 40F with a 100ohm resistor.
Sounds like you are setting up a full multi-media experience with Brucontrol and ESPN3I recently acquired an ESP 32. My router, from X Finity, does not allow static IP address. From a Google search it looks like I can reserve an IP address. Will they reserved IP address be good enough for an ESPN3 to connected via Wi-Fi to my PC?
Just a rambling on the use of connectors for RTDs... one of the risks of using connectors is that they can add incremental (or worse, variable) amounts of resistance to the circuit. RTD loops are REALLY REALLY sensitive to small resistance variations, and ideally are wired directly back to their amplifiers/controllers. But, it really makes a system hard to build and work on when the sensor wire needs to be hard-wired all the way. So if you are going to use connectors, make sure to use quality ones (legit gold plated, etc.) from reputable brands like TE, Amp, Molex, etc. Skip the Amazon/Ebay/Ali-whoever choices for these.I found the issue. The was a pin inside the sensor that was touching the housing causing a short.
Should not be an issue - should connect on both configurations. Please make sure its set up and enabled the same on both.How do I (or can I) use the same interface in two different configurations? When I tried it, it connected on one of them, but not the other.
One more question on heating element setup. From the user manual I think I am drawing these conclusions:
For a HLT with and a RIMS using heating elements and SSR, set up as Deadband device to control temperature.
For the BK since we want control boil rate, not temperature and eliminate boil-over, set up as Duty Cycle device and control it through scripting.
For a proportional valve, set up as a Deadband device with PWM output based on flowmeter input.
Does this seem reasonable?
I do this in a way with a global value. I set the global element for my valves and a script sets the valves according to the plan.I think I saw this before, but a feature request is arrays in scripting. Really just an indexing variable. I would like to configure elements like valves based on a step in the brewing process. It would be great if I could set a variable array of valve states by step.
My comment was more around arrays in general being much more efficient for coding. If you have 10 devices and 10 steps, it takes at least 100 lines of code to set them individually. Looping with an array would be 10 at most. Much less error prone too.I do this in a way with a global value. I set the global element for my valves and a script sets the valves according to the plan.
I can set the global element in any script and then start my scrValveOperation script which if self resetting
Since it is a global element, I can also set it manually. I do have some buttons and "Water" worksheet that also use this. As an example, I have a 1/2 silicone hose with a Kent Connector on the outlet side so I can connect to a part of the manifold or use it as a cleaning hose. I have a button that has a 10 second delay the a 20 second water flow. Very handy when cleaning by myself.,
I’d recommend shielded cable, grounded back to the chassis/control panel.Question on 1-wire temp sensors; as I'm setting up the upgraded brewhouse, I will have 2 X 1-wire sensors that will be a little less than 20 feet long each. I know this is beyond the recommended 10 feet max, but can it still work?
Agreed. We need to add this.My comment was more around arrays in general being much more efficient for coding. If you have 10 devices and 10 steps, it takes at least 100 lines of code to set them individually. Looping with an array would be 10 at most. Much less error prone too.
OK, flushed my temp sensor elements and started from scratch; 1st one, reset, 2nd one, reset - all good. When setting up my 3rd element in the same fashion, it starts reading 1 st sensor... again!!1-wire sensors are indexed upon bus reset, which happens at power-up or if manually reset. You can use the reset button on the MEGA instead of unplugging. Indexing happens in an arbitrary, but consistent manner… meaning the same devices will always index in the same order. So once your devices are wired-in, they will always fall into the same slot (0, 1, 2, etc.) until a sensor is added or removed from the bus.
Make sure you have different indexes set up on each different port, otherwise two different ports will report the same temp. For example, port 200 has index 0, port 201 has index 1, and port 202 has index 2. You can change the indexes without changing the ports later, once you know where each probe is physically located.
The volume sensor that I just received from BruControl has 4 wiresWiring Scematic and other info about using a BruControl volume sensor ?
There are 3 wires
Red: VCC1
Yellow: GND
Blue: Out
Assume (for Mega)
Red: +12 vdc (can take up to 30 vdc)
Yellow:GND
Blue: Analog Pin (A0-A15) and ASSOCIATED Analog Port (100 -115) (0 to +5 vdc )
OK, flushed my temp sensor elements and started from scratch; 1st one, reset, 2nd one, reset - all good. When setting up my 3rd element in the same fashion, it starts reading 1 st sensor... again!!
My Ports and Sensor indexes: Port 200/index 0, Port 201/index1, Port 202/index 2... I'm obviously missing something here. I understand the virtual ports 200-209, but I wonder what's the Sensor Inde
They changed the wiring on the recent batch. Red-power, black-ground, blue-signal, and silver is the shielding.The volume sensor that I just received from BruControl has 4 wires
Thoughts on what each wire is? How to wire to Uniflex v2?
- Red
- Blue
- Black
- Silver (metal w/no cover)