All profiles run for 10 sec then flag Run over

[steeleh]

This project will do exactly what I am looking for_ if I can get it to work.

Profiles run under Simulate for c10 sec and then flag Run Over. I thought this might be a Door Open prob but even if I set door to CLOSED I get "Error reading sensor oven temperature not responding to heat" because the oven temperature never moves from 0 under Simulate.

I am learning (slowly) Python to try and tweek the code but struggling. I don't want to spend a load of time money on a set up if I can't get Simulate to demo code can do what I want (ceramic kiln control)

I see mention of a follow on project piciPID but cannot find and development etc . Has picoReflow and or picoPID development been halted?

[chron0]

If it's in sim, there should be no actual sensor influence. Also the sim has never been a full implementation of all HW, it was merely a tool to give devs some data to work with while developing. After all, picoReflow was a PoC Demonstrator by hackers for hackers to have something open and as a basis for adaptation. Therefore it's no end-user, turn-key solution but a basis to hack around and adapt to whatever you want to do with it. The Code itself has been kept simple so just hook up some switches and LEDs instead of your real thing and fire away. Once you feel confident that it reacts to your action and the leds turn on and off as your kiln heater should just replace the LEDs with SSRs and connect switches sensor to it. People have demonstrated on more than one occasion that they were able to build kilns and all kinds of thermal governing systems and the code has received numerous PRs and updates over the years.

As such picoReflow isn't abandoned but it is no longer actively pushed forward. Its logical successor is https://github.com/apollo-ng/governess. The client and the basic underlying structures are ready in so far but the daemon/control code for the host is still lacking as it's a complex thing which I'm not skilled enough to do on the side alone. I'd need considerable free time and no dayjob which distracts and sucks out mojo needed to wrap my head around some of the concept and language idiosyncrasys

[steeleh]

Thanks for the swift response. All understood. I fear my standalone hacking and Python skills are not up to the task of getting picoReflow to safely operate at kiln at 1300C. Shame because it looked like my dream solution.

…

On 5 Mar 2018 21:50, "chrono" ***@***.***> wrote: If it's in sim, there should be no actual sensor influence. Also the sim has never been a full implementation of all HW, it was merely a tool to give devs some data to work with while developing. After all, picoReflow was a PoC Demonstrator by hackers for hackers to have something open and as a basis for adaptation. Therefore it's no end-user, turn-key solution but a basis to hack around and adapt to whatever you want to do with it. The Code itself has been kept simple so just hook up some switches and LEDs instead of your real thing and fire away. Once you feel confident that it reacts to your action and the leds turn on and off as your kiln heater should just replace the LEDs with SSRs and connect switches sensor to it. People have demonstrated on more than one occasion that they were able to build kilns and all kinds of thermal governing systems and the code has received numerous PRs and updates over the years. As such picoReflow isn't abandoned but it is no longer actively pushed forward. Its logical successor is https://github.com/apollo-ng/governess. The client and the basic underlying structures are ready in so far but the daemon/control code for the host is still lacking as it's a complex thing which I'm not skilled enough to do that on the side alone. I'd need considerable free time and no dayjob which distract and suck out mojo needed to wrap my head around some of the concept and language idiosyncrasys — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjWvBKRBOU6cuN1oqYS6tOB7NLCM0Q9Fks5tbbMrgaJpZM4SckDB> .

[chron0]

Ah, if you feel that way, don't let your own "incompetence" stop you. It's perfectly normal to feel a little intimidated by something new, which seems hard to get/understand at first. Every time I encounter something new, I'm at that very same junction. The point is not to stop oneself because of lack of experience/confidence. I get and totally support your caution, because letting a little robot control systems, which can easily burn down houses, is nothing to take lightly. Having said that, I felt the same way when we started, so I did what I proposed, just use LEDs at first. They'll show you what the governing logic is doing and give you confidence that the system is actually doing what you think it should do. Once you're happy with that, you can go for the real deal and test under your supervision. In the end you usually end up with a custom solution tailored by yourself to your use-case and I guarantee that you learned something in the process. win-win.