NEW StrangeBrew Elsinore Thread

Here's the log from the running server:

[email protected] ~ $ sudo java -jar ~/BrewServer/Elsinore.jar
Nov 23, 2014 7:14:54 PM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
CFG IS NULL
Checking section general
Checking section pumps
Checking section timers
Checking section device
Nov 23, 2014 7:14:56 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Parsing XML Device: HLT
Not enough volume data points, 0 found
Nov 23, 2014 7:14:56 PM com.sb.elsinore.Temp <init>
INFO: Adding28-00043c9205ff
Nov 23, 2014 7:14:56 PM com.sb.elsinore.Temp <init>
INFO: 28-00043c9205ff added.
Nov 23, 2014 7:14:56 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding HLT GPIO is (GPIO27)
Nov 23, 2014 7:14:56 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
Nov 23, 2014 7:14:56 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
Nov 23, 2014 7:14:57 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding PID with GPIO: GPIO27
Nov 23, 2014 7:14:57 PM com.sb.elsinore.PID detectGPIO
INFO: Matches: 3
Nov 23, 2014 7:14:57 PM com.sb.elsinore.PID detectGPIO
INFO: Matched GPIO pinout for Beagleboard: GPIO27. OS: null
Nov 23, 2014 7:14:57 PM com.sb.elsinore.PID run
INFO: Running HLT PID.
Could not find definitions file at: extras/gpio_definitions_lookup.xml
No definitions file found, assuming direct mapping
Could not find definitions file at: extras/gpio_definitions_lookup.xml
No definitions file found, assuming direct mapping
Nov 23, 2014 7:14:57 PM com.sb.elsinore.PID updateValues
INFO: 0: 0: 0
Nov 23, 2014 7:14:57 PM com.sb.elsinore.PID updateValues
INFO: 100: 0: 0
Saving the information for HLT
Nov 23, 2014 7:14:57 PM com.sb.elsinore.OutputControl run
INFO: Fduty: 0
Using base node device with ID HLT
Checking section device
Nov 23, 2014 7:14:57 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Parsing XML Device: MLT
Not enough volume data points, 0 found
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp <init>
INFO: Adding28-00043e8f1aff
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp <init>
INFO: 28-00043e8f1aff added.
Nov 23, 2014 7:14:57 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding MLT GPIO is (null)
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
Checking section device
Nov 23, 2014 7:14:57 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Parsing XML Device: SSR_Temp
Not enough volume data points, 0 found
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp <init>
INFO: Adding28-000004f8cf27
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp <init>
INFO: 28-000004f8cf27 added.
Nov 23, 2014 7:14:57 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding SSR_Temp GPIO is (null)
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
Nov 23, 2014 7:14:57 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
Nov 23, 2014 7:14:57 PM com.sb.elsinore.LaunchControl <init>
INFO: CONFIG READ COMPLETED***********
Nov 23, 2014 7:14:57 PM com.sb.elsinore.BrewServer <init>
INFO: Launching on port 8080
Nov 23, 2014 7:14:57 PM com.sb.elsinore.BrewServer <init>
INFO: Enabled logging at level:WARNING
Language: en_NZ
Server started, kill to stop.

Warning: NLS unused message: CHANGE_SCALE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: DUTY in: com.sb.elsinore.nls.messages
Warning: NLS unused message: CALIBRATION in: com.sb.elsinore.nls.messages
Warning: NLS unused message: HIDE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHOW in: com.sb.elsinore.nls.messages
Saving the information for HLT
Using base node device with ID HLT
Saving the information for HLT
Using base node device with ID HLT
Saving the information for HLT
Using base node device with ID HLT

 

Found the issue, an incorrect comparisson was prevent the PID thread from doing anything. Updates have been pushed.

 

Doug you're a genius! That did it!!! Played around with the manual duty times and they all worked. Hooked up an output load and it did it's thing. I will do more testing when I get home after work...at the moment very happy that things are now on track. Cheers!

 

Hi Doug - I wrote to you on your github re: the DTO and kernels newer than 3.12.

I reinstalled with a 3.8 kernel (ubuntu), installed the JRE-7 and I think I have Elsinore running; however, I can't access anything via a web browser on port 8080/controller. I've tried all the ip addresses in ifconfig.

Here's what I get from issuing sudo ./launch.sh


[email protected]:~/SB_Elsinore_server$ sudo ./launch.sh
Starting Elsinore as root
Nov 24, 2014 2:52:57 AM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
CFG IS NULL
DOC IS NULL
No 1Wire probes found! Please check your system!
Creating element of pumps
Creating on configDoc base





ps aux:

[email protected]:~/SB_Elsinore_server$ ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.4 0.3 3416 2020 ? Ss 02:42 0:04 /sbin/init
root 2 0.0 0.0 0 0 ? S 02:42 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? S 02:42 0:00 [ksoftirqd/0]
root 5 0.0 0.0 0 0 ? S< 02:42 0:00 [kworker/0:0H]
root 7 0.0 0.0 0 0 ? S< 02:42 0:00 [kworker/u:0H]
root 8 0.0 0.0 0 0 ? S 02:42 0:00 [migration/0]
root 9 0.0 0.0 0 0 ? S 02:42 0:00 [rcu_bh]
root 10 0.0 0.0 0 0 ? S 02:42 0:00 [rcu_sched]
root 11 0.0 0.0 0 0 ? S 02:42 0:00 [watchdog/0]
root 12 0.0 0.0 0 0 ? S< 02:42 0:00 [khelper]
root 13 0.0 0.0 0 0 ? S 02:42 0:00 [kdevtmpfs]
root 14 0.0 0.0 0 0 ? S< 02:42 0:00 [netns]
root 15 0.1 0.0 0 0 ? S 02:42 0:00 [kworker/0:1]
root 16 0.0 0.0 0 0 ? S 02:42 0:00 [bdi-default]
root 17 0.0 0.0 0 0 ? S< 02:42 0:00 [kintegrityd]
root 18 0.0 0.0 0 0 ? S< 02:42 0:00 [kblockd]
root 19 0.0 0.0 0 0 ? S 02:42 0:00 [khubd]
root 20 0.0 0.0 0 0 ? S 02:42 0:00 [irq/70-44e0b000]
root 21 0.0 0.0 0 0 ? S 02:42 0:00 [kworker/u:1]
root 24 0.0 0.0 0 0 ? S 02:42 0:00 [irq/7-tps65217]
root 27 0.0 0.0 0 0 ? S 02:42 0:00 [irq/30-4819c000]
root 36 0.0 0.0 0 0 ? S< 02:42 0:00 [rpciod]
root 38 0.0 0.0 0 0 ? S 02:42 0:00 [khungtaskd]
root 39 0.0 0.0 0 0 ? S 02:42 0:00 [kswapd0]
root 40 0.0 0.0 0 0 ? S 02:42 0:00 [fsnotify_mark]
root 41 0.0 0.0 0 0 ? S< 02:42 0:00 [nfsiod]
root 42 0.0 0.0 0 0 ? S< 02:42 0:00 [crypto]
root 45 0.0 0.0 0 0 ? S< 02:42 0:00 [pencrypt]
root 46 0.0 0.0 0 0 ? S< 02:42 0:00 [pdecrypt]
root 53 0.0 0.0 0 0 ? S< 02:42 0:00 [OMAP UART0]
root 57 0.0 0.0 0 0 ? S< 02:42 0:00 [kpsmoused]
root 58 0.0 0.0 0 0 ? S 02:42 0:00 [irq/134-mmc0]
root 70 0.0 0.0 0 0 ? S< 02:42 0:00 [binder]
root 71 0.0 0.0 0 0 ? S 02:42 0:00 [kworker/u:2]
root 74 0.0 0.0 0 0 ? S 02:42 0:00 [mmcqd/1]
root 75 0.0 0.0 0 0 ? S 02:42 0:00 [mmcqd/1boot0]
root 76 0.0 0.0 0 0 ? S 02:42 0:00 [mmcqd/1boot1]
root 77 0.0 0.0 0 0 ? S< 02:42 0:00 [deferwq]
root 124 0.0 0.0 0 0 ? S< 02:42 0:00 [kworker/0:1H]
root 138 0.0 0.0 0 0 ? S 02:42 0:00 [jbd2/mmcblk0p2-]
root 139 0.0 0.0 0 0 ? S< 02:42 0:00 [ext4-dio-unwrit]
root 293 0.0 0.1 2224 804 ? S 02:42 0:00 upstart-udev-bridge --daemon
root 298 0.0 0.2 9856 1276 ? Ss 02:42 0:00 /lib/systemd/systemd-udevd --daemon
message+ 354 0.0 0.1 3284 924 ? Ss 02:42 0:00 dbus-daemon --system --fork
root 373 0.0 0.2 3360 1344 ? Ss 02:42 0:00 /lib/systemd/systemd-logind
syslog 376 0.0 0.2 29576 1324 ? Ssl 02:42 0:00 rsyslogd
avahi 394 0.0 0.2 2696 1320 ? S 02:42 0:00 avahi-daemon: running [arm.local]
avahi 396 0.0 0.0 2696 492 ? S 02:42 0:00 avahi-daemon: chroot helper
root 405 0.0 0.0 0 0 ? S 02:42 0:00 [flush-179:0]
root 572 0.0 0.1 1940 544 ? S 02:42 0:00 upstart-socket-bridge --daemon
root 583 0.0 0.1 2484 956 ? S 02:42 0:00 upstart-file-bridge --daemon
root 616 0.0 0.1 3376 704 tty4 Ss+ 02:42 0:00 /sbin/getty -8 38400 tty4
root 617 0.0 0.1 3376 704 tty5 Ss+ 02:42 0:00 /sbin/getty -8 38400 tty5
root 621 0.0 0.1 3376 704 tty2 Ss+ 02:42 0:00 /sbin/getty -8 38400 tty2
root 622 0.0 0.1 3376 704 tty3 Ss+ 02:42 0:00 /sbin/getty -8 38400 tty3
root 625 0.0 0.1 3376 704 tty6 Ss+ 02:42 0:00 /sbin/getty -8 38400 tty6
root 658 0.0 0.1 2256 736 ? Ss 02:42 0:00 cron
root 661 0.0 0.1 1348 520 ? Ss 02:42 0:00 acpid -c /etc/acpi/events -s /var/run/acpid.
root 716 0.0 0.0 0 0 ? S 02:42 0:00 [file-storage]
root 851 0.0 0.3 3976 2028 ? Ss 02:42 0:00 dhclient -1 -v -pf /run/dhclient.eth0.pid -l
root 947 0.0 0.1 1780 540 ? Ss 02:42 0:00 /usr/sbin/udhcpd -S /etc/udhcpd.conf
root 953 0.0 0.4 5024 2200 ? Ss 02:42 0:00 /usr/sbin/apache2 -k start
www-data 957 0.0 0.3 227432 1992 ? Sl 02:42 0:00 /usr/sbin/apache2 -k start
www-data 958 0.0 0.3 227432 2000 ? Sl 02:42 0:00 /usr/sbin/apache2 -k start
root 1033 0.0 0.4 5880 2140 ? Ss 02:42 0:00 /usr/sbin/sshd -D
root 1076 0.0 0.1 3376 704 tty1 Ss+ 02:42 0:00 /sbin/getty -8 38400 tty1
root 1077 0.0 0.1 1624 632 ttyO0 Ss+ 02:42 0:00 /sbin/getty 115200 ttyO0
root 1092 0.0 0.5 9708 3040 ? Ss 02:44 0:00 sshd: ubuntu [priv]
ubuntu 1111 0.0 0.3 9708 1548 ? S 02:44 0:00 sshd: [email protected]/0
ubuntu 1114 0.0 0.3 4100 1600 pts/0 Ss 02:44 0:00 -bash
root 1138 0.0 0.0 0 0 ? S 02:47 0:00 [kworker/0:0]
ubuntu 1146 0.0 0.3 4104 1592 pts/0 S 02:50 0:00 bash
ubuntu 1188 0.0 0.1 3944 968 pts/0 R+ 02:56 0:00 ps aux


does it matter that apache is running on port 80?

ifconfig -a:

eth0 Link encap:Ethernet HWaddr d0:5f:b8:ef:db:c6
inet addr:192.168.0.158 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::d25f:b8ff:feef:dbc6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5378 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1507048 (1.5 MB) TX bytes:9954 (9.9 KB)
Interrupt:40

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

usb0 Link encap:Ethernet HWaddr 62:b1:47:ce:06:2e
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::60b1:47ff:fece:62e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5035 errors:0 dropped:0 overruns:0 frame:0
TX packets:6890 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:461392 (461.3 KB) TX bytes:1166654 (1.1 MB)


what I type in a browser address:

192.168.0.153:8080/controller


Do you see what I'm doing wrong? Thanks in advance.

 

Hi,
first of all thanks a lot for your hard work on this project, looking for use Elsinore on my E-biab setup!

Just a quick question on volume measurement (hope is not offtopic), if i understand correctly you use the brewtroller bubbler setup, in this case Elsinore software factorize the gravity for volume measurement? I mean...for simple water is ok, but during and after mash the gravity must be considered or the measurement will be really off (something like half a gallon)

I've read something about HERE

Cheers and keep going :rockin:

Adriano

 

Elsinore will not start unless you have at least one temperature probe installed. Because otherwise it is useless

 

Added a new documentation page: http://dougedey.github.io/2014/11/24/Why_Cant_I_Use_Elsinore_Without_Temperature_Probes/
Which is linked to by Elsinore when it doesn't detect any temperature probes.

Also removed a lot of the debug output so it does to the logger and hence can be configured when there's an actual issue.

I'm not going to be brewing for a few months, so if anyone sees an issue please let me know.

 

Hi Doug, found an issue, I'm on the latest version (via a git pull.)

When you switch to hysteria mode, setup then press send the duty cycle goes to -100 and nothing happens no matter what settings you plug in. Switching to auto or manual, entering in values and pressing send updates the gui but doesn't fire the gpio. Only a ctrl-c and and restart of Elsinore server gets it back in working order. I can then use auto or manual mode without issue but as soon as I switch to hysteria, the same problem happens requiring a reset.

Let me know if you need more info.

Cheers!

 

You do need to actually explain what you mean by "set up"

 

Ah yes of course, apologies.

From memory it was:

Min = 60c
Max = 70c
Time = 10mins

Just for kicks I entered... 1/100/10min

Now both times were after a ctrl c reset, restart.

Can you suggest some proper values to test?

Thanks Doug

 

Do you get any exceptions on the server?

 

No exceptions are displayed in the running status log. Let me know if you want me to try something.

 

I had hidden an exception in my previous update, fixed and pushed.

 

Okay I'll update and give it another go and let you know - I'm at work at the moment so in 5hrs or so

 

There is a (simple ) way to output some basic information on 20x4 lcd display? I've one spare, verified that is rpi compatible and seems pretty simple to send it information like about temperature probe reading, hope there is a way to send duty cycle information or Pump status, it would be great.

Sorry if i went OT

 

No, it's not designed for that, you can write something that hits the getstatus page yourself to write stuff to a screen

 

Okay, updated via git and have just tested it.

What's changed: I can now operate auto/manual after 'using' hysteria.

What hasn't changed: hysteria does the same ie. Duty = -100 and nothing happens.

Here's the log:

[email protected] ~ $ sudo java -jar ~/BrewServer/Elsinore.jar
Nov 26, 2014 4:23:44 PM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl readConfig
INFO: CFG IS NULL
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section general
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section pumps
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section timers
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section device
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Parsing XML Device: HLT
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Not enough volume data points, 0 found
Nov 26, 2014 4:23:46 PM com.sb.elsinore.Temp <init>
INFO: Adding28-00043c9205ff
Nov 26, 2014 4:23:46 PM com.sb.elsinore.Temp <init>
INFO: 28-00043c9205ff added.
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding HLT GPIO is (GPIO27)
Nov 26, 2014 4:23:46 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
Nov 26, 2014 4:23:46 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
Nov 26, 2014 4:23:46 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding PID with GPIO: GPIO27
Nov 26, 2014 4:23:46 PM com.sb.elsinore.PID detectGPIO
INFO: Matches: 3
Nov 26, 2014 4:23:46 PM com.sb.elsinore.PID detectGPIO
INFO: Direct GPIO Pinout detected. OS: null
Nov 26, 2014 4:23:46 PM com.sb.elsinore.PID run
INFO: Running HLT PID.
Could not find definitions file at: extras/gpio_definitions_lookup.xml
No definitions file found, assuming direct mapping
Could not find definitions file at: extras/gpio_definitions_lookup.xml
No definitions file found, assuming direct mapping
Nov 26, 2014 4:23:47 PM com.sb.elsinore.PID updateValues
INFO: 0: 0: 0
Nov 26, 2014 4:23:47 PM com.sb.elsinore.PID updateValues
INFO: 5: 0: 0
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl savePID
INFO: Saving the information for HLT
Nov 26, 2014 4:23:47 PM com.sb.elsinore.OutputControl setDuty
INFO: IN: 0 OUT: 0
Nov 26, 2014 4:23:47 PM com.sb.elsinore.OutputControl run
INFO: Fduty: 0
Nov 26, 2014 4:23:47 PM com.sb.elsinore.PID run
INFO: off: HLT status: 32 duty cycle: 0
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl savePID
INFO: Using base node device with ID HLT
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section device
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Parsing XML Device: MLT
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Not enough volume data points, 0 found
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp <init>
INFO: Adding28-00043e8f1aff
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp <init>
INFO: 28-00043e8f1aff added.
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding MLT GPIO is (null)
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section device
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Parsing XML Device: SSR_Temp
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl parseDevice
INFO: Not enough volume data points, 0 found
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp <init>
INFO: Adding28-000004f8cf27
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp <init>
INFO: 28-000004f8cf27 added.
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl startDevice
INFO: Adding SSR_Temp GPIO is (null)
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
Nov 26, 2014 4:23:47 PM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
Nov 26, 2014 4:23:47 PM com.sb.elsinore.LaunchControl <init>
INFO: CONFIG READ COMPLETED***********
Nov 26, 2014 4:23:47 PM com.sb.elsinore.BrewServer <init>
INFO: Launching on port 8080
Nov 26, 2014 4:23:47 PM com.sb.elsinore.BrewServer <init>
INFO: Enabled logging at level:WARNING
Warning: NLS unused message: CHANGE_SCALE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: DUTY in: com.sb.elsinore.nls.messages
Warning: NLS unused message: CALIBRATION in: com.sb.elsinore.nls.messages
Warning: NLS unused message: HIDE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHOW in: com.sb.elsinore.nls.messages

 

Just found something. If I exit, unplug the load, start Elsinore and then setup hysteria it kind of wants to work! As in there's. A message 'waiting for minimum time.... ' and when the time is up in sets the duty to -100 again.

The log file does not show any further output than the above.

 

Can you please provide more information? What is the current temperature on the temperature probe? What is your minimum temperature? What is your maximum temperature?

 

Yep sure thing.

No load:
Current temp=40
Min = 50
Max = 60
Time = 3mins

Hit send...

Counting down message appears...then the duty cycle goes to -100.

Hit 'off' then send to reset.

2200w Element load:
Current temp=39
Min = 50
Max = 60
Time = 3mins

Hit send...

No message appears, duty cycle goes straight to -100.

No change in log output in both instances.

 

Fixed it this morning

 

Doug what you have built is amazing. I have used rpi for all kinds of fun stuff but this is next lvl.
I am someone with hardware not software guy back ground so this might be a noob question. Is there a offline way to use UI? Could I host it on PC? Or one USB stick on RPI? My garage where I brew has hit and miss internet. Thanks for all the updates

 

You could just set up a "network" between the Rpi and your laptop via a crossover cable, or use an old wifi router and just create network with no internet connection. Just hard code the ip info so that they are on the same subnet.

 

You could just plug a keyboard and monitor into the RPi and use the local web browser...

 

Thanks Doug!

Did a short retest just now and yes hysteria is now working, but...not in the way that I was expecting - can you confirm please??

Fresh boot, git pull, reboot, start Elsinore, choose hysteria and setup as per:

2200w load
current temp.=24c
min=45c
max=50c
time=1min

Hits 50c, duty gets set to -100, keeps heating until it hits 66c...no system message to say that it's waiting and nothing special output to the logs

Switching back to Auto or Manual works 100% now.

Also, unrelated...I can't seem to add two timers...one always seems to dissapear, not sure if it's between switching edit/lock mode or on server start...I will investigate further but thought I'd let you know just in case

Cheers!

 

Thought I would just add that in it's present carnation it's completely usable for me. Hysteria Mode will not be used (I've got a STC1000) as I primarily wanted Elisnore to perform PID duties after I gave up on my Sestos PID after a single brew day with it lol

Love your work Doug....Cheers!

 

Fixed a logic bug on the hysteria

 

Thanks Doug, appreciated.

Okay just done the following and Hysteria seems to be broken?? here's my highly unscientific data:

Fresh boot, git pull, reboot, start Elsinore, choose hysteria and setup as per:

2200w load
current temp.=27c
min=45c
max=50c
time=1min

duty gets set to 0, nothing happens...no system message to say that it's waiting and nothing special output to the logs

switch to off, then send

switch to manual

2200w load
current temp.=27c
d/cycle=20%
d/time=5secs

starts duty [email protected]%, temp increases accordingly

switch to off, then send

switch to auto

2200w load
current temp.=44c
set point=55c
d/time=2secs
P=5
I=1.5
D=0

duty gets set to 50, then decreases as temp. climbs towards setpoint

switch to off, then send

switch to hysteria

2200w load
current temp.=58c
min=65c
max=70c
time=1min

duty gets set to 20, nothing happens...no system message to say that it's waiting and nothing special output to the logs

switch to off, then send

 

Thanks, can you give it a go with the latest changes? I had an extra check that was un-needed and I've removed it

 

No problem...here's what went down:

Fresh boot, git pull, reboot, start Elsinore, choose hysteria and setup as per:

2200w load
current temp.=31c
min=45c
max=50c
time=1min

system message appears "waiting for minimum..." approx. 20secs of time elapses then duty gets set to 100?!, temp. increases to 64C then duty is set to -100 (when I assume the timer resets? hard to tell) system message still in top left corner "waiting for minimum...", duty still at -100, meanwhile temp has climbed to 75c and then slowly drops

switch to off, then send

switch to hysteria

2200w load
current temp.=73c
min=80c
max=85c
time=1min

system message appears "waiting for minimum..." duty is set to 100, and immediately heats up 'till it hits 85c, duty is set to -100, system message still in top left corner "waiting for minimum...", duty still at -100, SSR suddenly closes?! and the temp climbs to 98c before the SSR opens/is switched off, duty still at -100, temp is slowly dropping

switch to off, then send

nothing special output to the logs...

 

double post

 

Not sure what you mean by "SSR suddenly closes", do you mean it turns on? Because that doesn't seem right.

I've done some more changes to prevent the -100 Activation when there's no cooling output.

If you see more issues use "./launch.sh -d" to get debug logs. There will be a lot so use something like pastebin to put them in.

 

Thanks Doug - yeah by SSR closes I mean the element turns on...I was surprised it came on too as it definetely is not what I thought would happen, and strange that it was only on the 2nd run through and not the first.

I'll give it another go tomorrow morning when I get some time and report back

 

Okay looking better Doug...here's the latest.

Fresh boot, git pull, reboot, start Elsinore, choose hysteria and setup as per:

2200w load
current temp.=22c
min=45c
max=50c
time=1min

system message appears "waiting for minimum..." immediately duty gets set to 100 and temp. increases to 52C, then duty is set to 0, system message is removed, temp climbes to 65c and then slowly drops, left for 5mins to see what happens, nothing kicks in

switch to off, then send

nothing special output to the logs...

switch to hysteria

2200w load
current temp.=61c
min=80c
max=85c
time=1min

system message appears "waiting for minimum..." immediately duty gets set to 100 and temp. increases to 95C, then duty is set to 0, system message is removed, temp climbes to 97c and then slowly drops, left for 5mins to see what happens, nothing kicks in, wait for temp to drop to between min/max, temp hits 80c exactly, duty gets set to 100 and temp. increases to 92.5C, then duty is set to 0, system message is removed, temp climbes to 97c and then slowly drops, left for 5mins, nothing kicks in

switch to off, then send

nothing special output to the logs...

Auto and Manual quickly tested and are working fine.

 

Doug...what's happened to the graphs? as I was sure they were there when I first loaded and tested it a few days ago. I looked at your youtube clip earlier today to confirm and yes they are supposed to be there. Any ideas??

Cheers!

 

So it sounds like the Hysteria mode is working right. You're probably heating a small amount of water so since it needs to leave the output on for a minimum amount of time it will keep going past the max or min if needs be, then the element/heater itself may continue to heat the medium.

Hysteria is turn cooler on if the temperature is above the maximum, and off if it's below the minimum. Turn heater on if it's below the minimum, turn off when above maximum. But both are reliant on the minimum time being the minimum time the output is on or off.

 

Not sure what you mean? You have to enable the recorder (it's disabled by default to prevent peoples SD Cards from being used) in the Edit Mode.
You click the button that says "Show graph" and the graph shows.

I've just pushed a fix for the full graph page.

 

Yep I'm using a 2L kichen kettle with about 8 cups of water in it, so yeah it's probably not within spec. of a real HLT!!

Great work Doug!! and thanks for putting up with my musings...hopefully it helps put Elsinore in good stead for the future! speaking of which, I'm going to do a 40L batch tomorrow and can't wait to try it out in a real world environment!

Cheers!

 

Okay I'll give it a go later on and see - thanks again!

 

Found it Doug - couldn't see the checkbox in Firefox on my PC but could on my mobile. So up and running with it now and it's plotting away nicely.

A couple of questions please...is it possible to pause the graph?? as I would like to take my time in analysing the data in order to fine tune the PID. Also, where's the data kept and how easy is it to delete in case my SD card becomes full?

Cheers!