curruscanis
Active Member
- Joined
- Dec 7, 2015
- Messages
- 39
- Reaction score
- 8
Your probably right I never tried it that way since I already had it off... I'll try that tomorrow. Thanks.
I confirmed that putting the jumper back on did work.
Your probably right I never tried it that way since I already had it off... I'll try that tomorrow. Thanks.
What firmware version are you running, what scripts version are you running, what do the logs say, what kind of power supply are you using for the Arduino?
Or is this the version of the script?Ok now I see this in the log file:
Terminating due to fatal serial error
2019-09-25 01:55:08 Starting BrewPi.
Terminating due to fatal serial error
2019-09-25 08:30:08 Starting BrewPi.
Terminating due to fatal serial error
2019-09-25 11:10:08 Starting BrewPi.
Terminating due to fatal serial error
2019-09-25 12:25:08 Starting BrewPi.
Terminating due to fatal serial error
2019-09-25 18:50:08 Starting BrewPi.
Terminating due to fatal serial error
2019-09-25 20:45:08 Starting BrewPi.
The firmware version is brewpi-arduino-uno-i2c-0.2.12 and were can I find the version of the script?
The Arduino Uno is connected to the RPI with a USB cable for power.
First, you’re going to have to get the firmware which supports it. Then you will have to follow my instructions for a starting point, then we can talk about what to modify.
Physically, you will use a beer probe only, and control your pump via the controller. If you want a probe to monitor your glycol your will use the “room” sensor.
I have a Firmware version for you to use, I need to get it where it’s available to you.
Yes. There’s a new version. Nobody has done this before because you will be the first one to whom I will deliver this version of the Firmware.
When you are in Beer constant and don’t have a chamber sensor, the chamber sensor will use the beer sensor (which we want in this case.)
Inside your BrewPi directory, execute:
sudo git tag
The highest number is the current version.
Also, I need to see what the log says before that error.
It appears that either the Arduino/cable is bad, or the port is misconfigured or incorrect. Have you done any "tweaking" to the config file?full error log see attachment stderr.txt
There's an alpha build in the devel branch of firmware that has this glycol support. Be sure to grab the right one for your shield, you'll have to flash manually for now:Sounds great, I am up for the challenge.
It appears that either the Arduino/cable is bad, or the port is misconfigured or incorrect. Have you done any "tweaking" to the config file?
What happens when you issue the command 'sudo systemctl status left'?
SUBSYSTEM=="tty", ATTRS{serial}=="75533343336351208261", SYMLINK+="left"
lrwxrwxrwx 1 root root 7 Sep 27 03:55 /dev/left -> ttyACM0
sudo /home/brewpi/left/terminal.py
Type the string you want to send to the controller: n
Sending: n
N:{"v":"0.2.11","n":"af7545e","s":2,"y":0,"b":"s","l":"3"}
We can check some additional things before replacing parts:
Running 'sudo cat /etc/udev/rules.d/99-arduino.rules' should give you something like this (serial number will be different):
Then, 'ls -al /dev/left' should look like this:Code:SUBSYSTEM=="tty", ATTRS{serial}=="75533343336351208261", SYMLINK+="left"
Assuming those look ok, you can run a serial monitor to see what you get:Code:lrwxrwxrwx 1 root root 7 Sep 27 03:55 /dev/left -> ttyACM0
Enter 's' to allow you to enter a command, then enter a safe command like 'n'. You should see something like:Code:sudo /home/brewpi/left/terminal.py
Enter 'q' to quit.Code:Type the string you want to send to the controller: n Sending: n N:{"v":"0.2.11","n":"af7545e","s":2,"y":0,"b":"s","l":"3"}
If that works, it would be handy to see the contents of the stdout.log corresponding to the errors.
The stderr.txt is interesting because of the frequency of the errors, especially networking errors. There's even some from eth0 which I would have expected to be filtered out. What's your network setup?
There's an alpha build in the devel branch of firmware that has this glycol support. Be sure to grab the right one for your shield, you'll have to flash manually for now:
0.2.13 (alpha)
Do not use this in production, it is an alpha commit only. The glycol variant may burn up your compressor if you use it on a standard refrigerator setup.
This change enables compiler macros to set parameters suitable for glycol use. This means there are two new firmware versions; a "glycol" variant for both I2C and RevC. When using the glycol, zero out the PID values (`Kp`, `Ki`, `Kd`) in order to make "Fridge setpoint" equal to "Beer setpoint." Use only the beer sensor, the refrigerator temperature will get its value internally from the beer sensor. If you wish to monitor the glycol temperature, use the "room" sensor. Control the pump as "cool" via the relay.
Features
- Add support for Glycol control
Enhancements
- Update to atmelavr 1.15.0 from 1.14.0.
Incidentally, someone else reported the exact error you were having flashing the firmware so I'm going to push a fix for that as soon as I get my dev Pi working again.
I have flashed my Uno manually now to modify the brewpi-remix settings.
There's an alpha build in the devel branch of firmware that has this glycol support. Be sure to grab the right one for your shield, you'll have to flash manually for now:
0.2.13 (alpha)
Do not use this in production, it is an alpha commit only. The glycol variant may burn up your compressor if you use it on a standard refrigerator setup.
This change enables compiler macros to set parameters suitable for glycol use. This means there are two new firmware versions; a "glycol" variant for both I2C and RevC. When using the glycol, zero out the PID values (`Kp`, `Ki`, `Kd`) in order to make "Fridge setpoint" equal to "Beer setpoint." Use only the beer sensor, the refrigerator temperature will get its value internally from the beer sensor. If you wish to monitor the glycol temperature, use the "room" sensor. Control the pump as "cool" via the relay.
Features
- Add support for Glycol control
Enhancements
- Update to atmelavr 1.15.0 from 1.14.0.
Incidentally, someone else reported the exact error you were having flashing the firmware so I'm going to push a fix for that as soon as I get my dev Pi working again.
doUpdate is sort of like rebooting a Windows server. Always a good idea to run it when you have issues.
So you’ve got it running at least?
No I didn't so I stopped the script and run the commands again:Did you stop the script first? If not, do that please. Sorry if I did not mention that.
What does the status text (LCD) show? In what mode is the controller set?I am having an issue with the relay firing upon cooling call.
I don't think the call for cooling is happening.
It does look like there may be a loose connection there. On the other hand, it's not completely out of the blue for a sensor to sporadically not reply in time which generates that output. All in all, not a comprehensive data set.Debug message received: WARNING 2: Temperature sensor disconnected pin 14, address 28AAC5124F1401A5
Is there a problem with the Temperature sensor address 28AAC5124F1401A5?
Did not had the time to check which sensor this is.
/usr/share/arduino/hardware/tools/avrdude -F -e -p atmega328p -c arduino -b 115200 -P /dev/left -U flash:w:"/home/pi/brewpi-arduino-uno-i2c-0.2.13.hex" -C /usr/share/arduino/hardware/tools/avrdude.conf
- sys.stdout = open(logPath + 'stdout.txt', 'w', 0)
+ sys.stdout = open(logPath + 'stdout.txt', 'a', 0)
The LCD is reading idleingWhat does the status text (LCD) show? In what mode is the controller set?
Would you please post your stddout.txt and stderr.txt?The LCD is reading idleing
The mode is beer constant.
I woul be happy to... Working from my phone at the moment but I can vpn in... Is there a good way to do that from the interface or only ssh? If so can you explain, please pardon my ignorance.Would you please post your stddout.txt and stderr.txt?
Best I can do with my phone quickly...Would you please post your stddout.txt and stderr.txt?
LBussy, thank you so much for your work on this...
I am having an issue with the relay firing upon cooling call.
I don't think the call for cooling is happening. I have successfully flashed my unit and updates my brewpi-remix. I have set the PID ( KP, KI, KD ) values to "0". I have the devices setup as shown here:
View attachment 645907
I have the device 1 temp probe in ice water for testing... the device 0 "beer temp probe" is in ambient air.
I have the brewpi-remix set to beer constant with a temp setting of 50.0 F
But I do not get a cooling cycle...
If I invert the pin type of the device I do get the correct relay to fire so it is wired correctly.
You need a chamber temp sensor. I only see a beer sensor and a room sensor...
My apologies for the derail... I should have assumed @LBussy and @day_trippr had you on the right track!Yes that is true, I am using a new "alpha" glycol firmware as discussed earlier in this thread.
This configuration is appropriate for that seanario.
My apologies for the derail... I should have assumed @LBussy and @day_trippr had you on the right track!
To easily send logs, you can issue the following commandI woul be happy to... Working from my phone at the moment but I can vpn in... Is there a good way to do that from the interface or only ssh? If so can you explain, please pardon my ignorance.
$ cat /home/brewpi/logs/stdout.txt | pastebinit
$ cat /home/brewpi/logs/stdout.txt | pastebinit
This *looks* okay so far, but I'd need to see the rest of the logs.Best I can do with my phone quickly...
That's a good idea - give that a shot as well.Edit 2: Sorry, I missed that you are running in Beer constant. If I were you, I'd reassign the Room Temp as your chamber temp and test that way. (to rule out not having a chamber temp as a problem)
To easily send logs, you can issue the following command
orCode:$ cat /home/brewpi/logs/stdout.txt | pastebinit
{you will probably see some warnings here}Code:$ cat /home/brewpi/logs/stdout.txt | pastebinit
The output will be a URL you can share like this one: http://paste.debian.net/1103085/
This *looks* okay so far, but I'd need to see the rest of the logs.
That's a good idea - give that a shot as well.
Not quite - he said change your "room" temp (which is your glycol) back to a "chamber" temp device.But I did try changing it to chamber mode... Same result.
To easily send logs, you can issue the following command
orCode:$ cat /home/brewpi/logs/stdout.txt | pastebinit
{you will probably see some warnings here}Code:$ cat /home/brewpi/logs/stdout.txt | pastebinit
The output will be a URL you can share like this one: http://paste.debian.net/1103085/
This *looks* okay so far, but I'd need to see the rest of the logs.
That's a good idea - give that a shot as well.
Enter your email address to join: