Page 47 of 47 FirstFirst ... 37454647
Results 461 to 463 of 463

Thread: The Development Log

  1. #461
    TVWBB Platinum Member Bryan Mayland's Avatar
    Join Date
    Apr 2010
    Location
    Tampa, FL
    Posts
    4,060
    Only the last low and high peak are displayed on the graph, and only when your mouse is close enough to the peak. The extra values on there are to help you tune your PID, which would use the period of the oscillation (the time from one high to the next high, or the low to the next low). The "half" number is the last half of the period (the last low to high or high to low) which can be compared to the overall period to see if your low to high is short but high to low is long which would indicate you're giving it too much power and overshooting or you can't damper the fire enough to bring the temperature back down. The "deg" is the gain from the last period's high-low to this one. If you've got perfect oscillations where each time the high and low are the same, this is 0. If it is a positive number things are getting more out of control over time, if negative, they are dampening around the setpoint.

    Edge and IE don't support server-sent event streaming so they poll HeaterMeter every 10 seconds, Chrome, FF, Opera, Safari all stream the data which updates every 1-5s as it changes. Therefore you and end up seeing more "noise" in the graph because it contains up to 10x more data. Edge has had this web standard "under consideration" for development for like 3 years now.
    I'm that HeaterMeter guy what ruins everybody's free time.

  2. #462
    New Member
    Join Date
    May 2017
    Location
    Australia, NSW
    Posts
    5
    Excellent, thanks Bryan!

    rgds,
    Vic

  3. #463
    TVWBB Platinum Member Bryan Mayland's Avatar
    Join Date
    Apr 2010
    Location
    Tampa, FL
    Posts
    4,060
    I've pushed out a new snapshot release of just the AVR firmware. This build adds support for longpress handlers in the menu system so it fundamentally changes some of the underlying button detection code that we love to break so much. That's why I need some testers before this gets rolled into the wrt/lede firmware as the default!

    The way it works is that each menu state can declare that it supports a long press of a button (>1 second). When a button is pressed down, HeaterMeter sees if the current state has a longpress for that button. If it does not, the handler fires immediately so press is responsive as possible. If it is held down then it will start a repeat count which accelerates things like quickly changing the setpoint in 5, 10, or 20 degree increments. If there is a longpress handler, then HeaterMeter waits to see of you hold it for the full 1 second. If you release before 1 seconds, the short press button handler fires. For longer than 1 seconds, the long press handler fires. If a longpress event occurs, or a state transition (via shortpress) occurs into a state with a longpress handler for that button, the button must be released before that button will function again.

    This is hard to describe so I've also added the first longpress handler to give you something to test with: PID Output Off mode. A left button longpress from the device's "home" state (the one that displays the temperatures or -No Pit Probe-), will toggle the HeaterMeter output on/off. This provides an easy way to turn off the HeaterMeter output when a cook is done without setting the setpoint to a very low value to effectively disable it. An often-requested feature finally makes it in!



    • A left longpress while in auto output mode will disable output, LCD home will display [Off] as the output
    • Left longpress again will return to auto mode with the original setpoint
    • Left short press in auto mode still toggles Lid Mode on and off, but only functions if not [Off]
    • A left longpress in manual mode will set the output to 0% (this is not a toggle, always 0%)
    • Left short press in manual mode lowers the manual output by 1% (as it had before)
    • Pressing left from any of the device menus should immediately return you to the home screen, even if you hold the button down and NOT toggle on/off even if you continue to hold it for 1 second, you must release it after entering the home state and then press and hold again to trigger on/off
    • Setting a setpoint or manual output automatically turns PID control back on
    • The [Off] state is not persisted across device power cycles, but most likely will be


    This also fixes a couple small bugs in the AVR firmware:
    • Pressing "back" (left button) from the menus would not update the display with the home screen for up to 1 second if there were no food probes detected. This has been fixed so exiting the menus updates the display immediately.
    • If a setpoint of just "C" or "F" was sent via the webui, HeaterMeter would enter manual mode. It now stays in whatever mode it was in and just updates the units.


    To test, just go to LinkMeter -> AVR Firmware from the webui and select "Online Repository" and flash
    Code:
    Location: snapshots/trunk/heatermeter.hex
    MD5: 136d1bcb469398f32cc3d183e4748c95
    Version: 20170722B
    You may return to the regular firmware if you experience any difficulties by flashing the "bundled firmware " hm.hex from the same page. If you do test and you do have problems, please report back with what menu state you were in, what button you pressed, what was supposed to happen and what did happen. Also include which probes were plugged in, and if you were in auto or manual mode, and any other details you can provide to help me reproduce it.
    Last edited by Bryan Mayland; Yesterday at 01:43 PM.
    I'm that HeaterMeter guy what ruins everybody's free time.

Page 47 of 47 FirstFirst ... 37454647

Similar Threads

  1. Development Update: 1Hz updates
    By Bryan Mayland in forum HeaterMeter DIY BBQ Controller
    Replies: 6
    Last Post: 09-02-2012, 04:29 PM
  2. Flavor development
    By Gary Bramley in forum Q&A #1 with Jamie Purviance
    Replies: 1
    Last Post: 03-28-2007, 02:31 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •