Is your DC - bus connected to your AC ground?NTC 10k Probes Calibration
I am using a few NTC 10k probes and throughout my brewery and I find them unreliable. I find myself constantly calibrating them, adding various offsets at start of each brewday. The max total offset range is anywhere from +10 to minus 10.
One of those probes is the same as used with my BCS-482. My BCS-482 as been working reliably so far.
Could this issue be linked to some EMF pollution? I find it quite difficult separating my DC and AC wires in my control panel..
So hooking the 2 DC - to one grounding stud and the AC bus to another stud?Yes it does, your EMI may be induced via something noisy on the AC ground. Try connecting the 2 DC - together and isolating them from the AC ground.
So my control panel would have 2 grounding studs like this..?Yes it does, your EMI may be induced via something noisy on the AC ground. Try connecting the 2 DC - together and isolating them from the AC ground.
As mentioned above keep the AC and DC grounds isolated. If the 2 ground studs you have pictured are attached to the side of the control panel or have a common connection then you haven't isolated them. What I did with my panel was to use the AC supply ground via supply cable and have that terminated on a series of terminal blocks which I only attach AC grounds to. This termination grounding block is isolated from the rest of the panel. My electrical panel is grounded via steel rod driven 9' into the ground. I then ran a separate ground from my copper water pipe (street side) to the side of the control panel and used a star pattern to connect my DC ground termination block for all things DC related. In other words I have 2 ground sources (1) ground from 4 wire supply AC and (2) water pipe separate path to panel and DC termination array. Both are isolated from one another. There are other ways of doing this but this was more convenient for my application.
In my case the water supply street side is copper to the water meter then PEX pipe after that so no bond/connection between the copper pipe and the main electrical panel. This situation provides 2 different paths to ground ( steel rod and copper water pipe) so yes it would meet criteria for isolation of grounds.Typically home copper water pipes would be grounded to the AC ground, even if the main AC ground is through a steel rod into the ground from the main panel. Would this still meet your isolation for EMI purposes?
No, we are trying to eliminate potential intrusion of AC signals on the DC - bus. Simply tie a wire between all of your DC - terminals and see if that eliminates your EMI you are seeing in your temperature probes.I just checked city water pipe inlet with AC panel ground and they are indeed bonded…
Perhaps I should use install a dedicated grounding Rod for my DC..?
NTC 10k Probes Calibration
I am using a few NTC 10k probes and throughout my brewery and I find them unreliable. I find myself constantly calibrating them, adding various offsets at start of each brewday. The max total offset range is anywhere from +10 to minus 10.
One of those probes is the same as used with my BCS-482. My BCS-482 as been working reliably so far.
Could this issue be linked to some EMF pollution? I find it quite difficult separating my DC and AC wires in my control panel..
Shielding your thermistor wires can help too. Would need a metallic shield/sleeve with it tied to ground at the enclosure side only.No, we are trying to eliminate potential intrusion of AC signals on the DC - bus. Simply tie a wire between all of your DC - terminals and see if that eliminates your EMI you are seeing in your temperature probes.
I have traced my wires and rechecked the connection. I also purchased a 0 to 5 v analog voltmeter.I am trying to trouble shoot an issue with Hysteresis and the Unishield, ----
River City is correct to get you up and running. Don't fix it if it a'int broken. For upgrading to v46,The biggest change will be with Analog Ports A1-A15 if you have used them. You will need to delete the "old" Elements and recreate "new" ones for any analog ports.Forgive me if I missed this, been busy running the brewery lately and have not kept up around here. Mega just burned up on me (Brewery is down!!) and I need to flash firmware on the new unit purchased. I see version 46 was released last month and the note says "This version requires new interface definition files in BruControl" I'm fairly certain I was on 45O because I had not yet changed over any interface definition files associated with 45Q.
Can someone give me a rundown on what this means (pros/cons) and the tasks/effort that are in front of me so I can better decide whether I should stick with 45O or run the new 46? I'm currently running BruControl 1.1 Build 22 which I believe pretty much confirms I was on 45O.
Steve
I did upgrade from V45 to V46 with the mindset that with any future updates I wouldn't have to mess around with the Analog port conversions on top of the actual update. Not all updates in V46 affect my situation but some have had some very useful improvements,. I figured do it now and not prolong the inevitable, just my 2 cents worth. You mention you have purchased additional MEGA's, why not install the new firmware on them, do the Analog conversion and have everything set in case the existing board goes down, this way you have a updated board to swap out in the event of a toasted board. You wouldn't have to take your existing system offline unless something happened to your production board. It's proactive insurance the way I see it.I got everything changed over and back up and running. I purchased a few extra Mega and Sunfounder Ethernet boards. In theory I should be able to install same firmware and Ethernet settings for a quick swap out in the event of another failure? Should I use same MAC address or a unique one?
What are the advantages of the newest firmware?
Tartan has a great idea. Just save your configuration and give it a name beside .....copy.brucfg and choose it as your configuration under settings. You could then upgrade at your own pace and switch boards between FW 45 and FW 46 (or Just reflash them).I got everything changed over and back up and running. I purchased a few extra Mega and Sunfounder Ethernet boards. In theory I should be able to install same firmware and Ethernet settings for a quick swap out in the event of another failure? Should I use same MAC address or a unique one?
What are the advantages of the newest firmware?
Hi thanks,Tartan has a great idea. Just save your configuration and give it a name beside .....copy.brucfg and choose it as your configuration under settings. You could then upgrade at your own pace and switch boards between FW 45 and FW 46 (or Just reflash them).
Go between configurations and FW 45 and FW 46
Here is a link to what @BrunDog said when FW 46 was released
https://www.homebrewtalk.com/thread...ntrol-automation-software.624198/post-9307818
Here is a link to how I converted:
https://www.homebrewtalk.com/thread...ntrol-automation-software.624198/post-9310064
Most firmware updates haveHi thanks,
but upgrade at this point of time brings nothing, or am I wrong?
Sorry I was away for longer time, I didn't see any new version of the software? Did I missed it :-S
Br
Earlier posted was the this question about the relay current draw;720ma total draw is also How I see it
grounding... and isolation... the sudden change in current to the start or stop of the motor and/or relay is causing an actual change in voltage on your RTD, and the RTD smoothing algorithm takes a while to return.. research: "flyback diode"When I toggle the relay for the pump, the RTD measurements drop out to negative and then come back. Any suggestions on what to consider for this problem?
So true. Definitely look into playing around with the RTD software filer algorithm. In my case the dropouts seem to come from the relay cycling of the 24VAC transformer I have in my control box for the burner (yes, I am gas fired). Several ways to fix this, but since I have the software filter engaged the impact of a random event (0-3 times during the brew) getting through is not worth worrying about. I really am glad to have moved over to the stability and accuracy of the RTDs, since the 1-wires were a bit persnickety.grounding... and isolation... the sudden change in current to the start or stop of the motor and/or relay is causing an actual change in voltage on your RTD, and the RTD smoothing algorithm takes a while to return.. research: "flyback diode"
I got the Giga R1 Wifi boards in, I know there is no BC firmware yet, so just tinkering... of course the usb port doesn't work with standard win10 or Win7 drivers
Probably nothing to do with globals but I did find that I had some comments that might be causes some issues.I am having an issue again with too many Global Elements. I use globals for lots of things like labels and to store things that do not change between brews (such as flow rates between vessels). I also use Globals to store Setpoints that I can change and then update the Target of an Element.
Once I reach the "limit" the program stops being logical (if and endifs do not function properly, among other things). I took the same script from a "funky" Configuration and went back to saved Configuration and the same script placed in the old configuration worked fine.
Attached is my main brewery Screen where I have 31 Globals, not of which I need for any data.
If you look, you can see that 1,2, & 3 are stacked(you cannot see 2 or 3). I have to have 3 because I use colors to "guide" what I am doing. For Example. a Blue Background means to Wait and the program will auto advance. The same is true for 7,8,&9. If I was able to just use a path for background 1, I would go from 6 to 2 globals with more functionality with endless Backgrounds.
1 to 10 are simple Text boxes where I can change the value of the text.
11 is where I can manually enter a value and save it to a different Global (on my Data Exchange workspace) that I do want to save, such as OG, or the Volume of the Brew Kettle pre Boil.
12 to 22 are just for display. I tried using an Inspector for this but they "Blink" continuously.
23 to 26 show the status of my Heating Elements. They simply become hidden when the heater state = false.
The background of my pumps (27 to 31) change depending on the state.
32 and 33 have a Script that allows me to quickly change the Mash and Boil Timer when I am testing the program. This are normally hidden and only set to visible when I am testing some scripts.
34 is an incremental global where I branch the program and skip steps if I need to go down a different line. Some of the Texts in 1-10 can also be set in the same script depending on the value of 34 (gBrewStatus)
The program works fine until I exceed the undocumented limit on Globals, then it slows down and scripts that were working no longer do so properly. It is hard to describe what happens when that limit is exceeded.
I have a lot more globals than this for importing a BeerSmith xml file and to store things like volumes and transfer times on other workspaces,
View attachment 827761
1. An Element that is just like a Global except that it is not hit to transfer to the database would solve the issue I think. I do not use the localDB because it gets very large (gigibytes) very quickly.
2. Paths for background and fileIndex where I could leave on Image 1 (or Index 1) and just change the path in the box would be super and make it much easier. The choice of 3 is not enough. I think I have something like 20 alarms because I want different sounds (Lots of Text to Speech)
3. Global that hit the Local DB should have the option of Never, a Time Choice, Once, Forced save (script command). I am not sure if setting to "Never" would solve my issue as the program is still "looking" at the Global to see that status. I do not know how the internal program "looks" at Globals, but I think the problem lies there.
I spent the past 4 weeks rebuilding the program from scratch, but it looks like I am going to have to go back to one that works properly(from last week to be sure I go back far enough) It will not have the automation I wanted because I used globals to manipulate and save data. I tried using variables but every time I crashed a script in testing, I lost my variables. And many scripts use the same global to get or save data which makes them much better suited to do that.
Any issue with I/O conflicts for the 1-wire or anything else??Been working on a fermentation controller using a Lilygo 8 relay board I bought last year. The embedded ESP32 loaded fine and I have been able to test functionality of the 1-wire temperature probes, LCD screen, and relays to control Heat/Cool of two fermenters and power to their chiller. I split the supply power to the box, one power cable furnishes AC to the relays and the other furnishes 12VDC to the board. I did this to reduce the load on my UPS (have done the same for my brew stand). If (and when) the grid goes down, my controllers and computer will run until I am able to get backup power going.
I have hacked in a level converter to control the 1-wire and LCD which I power with 5VDC that the onboard regulator puts out from the 12V.
Yes, but not for the 1-wire.Any issue with I/O conflicts for the 1-wire or anything else??
I think you would have to get @BrunDog to add that to the program. Right now the Input is on the PID Element and that single Probe Provides the Temperature for the Probe. When I was using the BCS early on, you could do that, but after using it for a while, I decided it was a bad idea. I was using it with a HERMS system and averaging the Temp IN vs Temp OUT. I soon realized that the Temp IN was TOO hot. When I went back to not average and only use the Temp IN, the Mash got to that temp and eventually the Temp OUT matched the Temp IN.How would I go about averaging inputs for a PID control? Lets say I have 2 temp probes I want to use as an average input for my PID for my mash temp.
Probe 1: 150
Probe 2: 160
I want my PID to know its currently 155 and use that as its input.
Enter your email address to join: