PicoStill lock in priming steam generator #315
Comments
|
I start the still process from the PicoPro UI. I get the data logged on the WebUI. I am still in 0.30 firmware (no upgrade proposal) |
|
|
|
|
|
|
MORE ...
|
MORE ...
|
|
Hrm. I don't have a Pico small device series associated with my PicoStill (only Z). From those access logs (appreciate that!) there isn't an obvious error that is happening, though there could be an invalid response structure returned to the PicoStill device, though from how I understand how the Still and the Pico communicate is via a direct network connection. How is your network for the Pico devices setup? Are you simply using the community RaspberryPi setup we provide or something more custom? |
|
The server is an EspressoBin ARM64 with OpenWrt 21.02 with docker. |
|
Do you know if the ip addresses of the PicoStill and the Pico C/s/Pro can communicate to each other? |
|
The PicoBrew server is starting the PicoStill. The server shows an empty embedded PicoStill data |
|
|
|
|
That happens if the Server can't communicate outgoing/egress to the detected IP address of the PicoStill. Sorry I don't have further debug help, from what I've seen so far it is pointing to that the devices on the 10.4.2.x subnet aren't able to communicate to each other. |
MORE ...
|
|
It looks like the server get values from the PicoStill ?! |
May be it is a client side problem ? |
|
I have modify he DNS redirection from only picobrew.com to *picobrew.com and the PicoStill had correctly upgraded to the specified version 0.35. I have now the PicoStill IP automatically sets to the PicoBrew server IP. |
|
What is the correct sequence/procedure for Distill ? |
|
Starting the PicoStill monitoring on the PicoBrew server only populates the graph, there is no need to do this to create distillate. Starting the PicoStill process is done via either the main Pico device connected to it and/or from the embedded UI of the PicoStill itself (turning on the pump and fan, etc which is needed to be done for Zymatics). Currently "start monitoring" simply starts a background polling job on the server that periodically will ask the PicoStill via an internal API what the data points are (as seen from the following lines taken from your access logs). |
|
thanks for the advice... It looks like that this is the PicoPro which is not heating at all... The pump is working but the "prime steam process" never end because the heat stay cold ! |
|
@erdoukki but when you said it would work when connected to the main Picobrew servers? Does that still work now if you connect back to your main WiFi? |
|
@tmack8001 Do you mean with the official PicoBrew servers ? I will try, because I was thinking that the main servers were now offline... |
|
The main Picobrew servers are infact not offline (mentioned several times in various places). They simply have an expired ssl certificate... |
|
What I want to figure out here is if there is a bug in the offline server solution or if your machine is truly not functioning as it should. Sorry I don't have the same setup as you so can't test that specific configuration. |
|
Sure, I'll try it and report... |
|
Same with Officials servers...
The PicoPro and PicoStill looks to communicate with PicoBrew servers... |
|
I have tried to reset the PicoStill... still stuck ! |
|
Basic question are you filling the top reservoir with RO or distilled water? Are you able to simply brew in the Pico unit? |
|
Some test with my PicoPro get nowhere ! The problem looks to be with temperatures censors... I get some access to the factory test menu but no success and no errors reported... Still need some help of experimentend users. Sorry to noise your repository with this issue, but I do not know anywhere else to ask for help. Thanks again for carring of, for clues, and help... 😉 |
I will check the brew alone... |
|
Still same ERROR. Still blocked with the "PRIMING STEAM GENERATOR" which never end. I have applied all PICO tests of the SERVICE MODE. All tests are fully OK. But, in MANUAL BREW and in PICOSTILL, I always get stuck at the verry first step with the fatal error message PRIMING STEAM GENERATOR. I can post more (debugs, ...) I can also add and play with the JTAG... But if anyone have any advice, clue, tips or... idea ! |
|
Hello there. I have had this issue often. Generally after I have not used my Machine in a long time. (few months). I always do 2 deep cleans after a brew with the finish tablets. Before brewing ( after it sits for months) I always run mock brew and monitor if it is heating. If I do not see it raise in temperature after 15-20 mins I know I have a clog in the heater output hose. I have tore apart my other unit and have seen the that heat output hose has a Metal nozzle in it with a small hole to let the heat out. It is easily blocked. I don't recommend taking the whole thing apart like I did as after 3 years it is still sitting in parts waiting to be reassembled. I have 2 other units working and have occasional similar issues with them the procedure below has worked every time for me. What I do to unclog the hose. I fill the keg with Hot water (about 200 F) and run a mock brew with a finish tablet. The water temp will generally start dropping for a while and if your successful in clearing the clog you will start to see the temp rise. The heat from both sides of the clog generally loosen up whatever is in there causing a clog. Another thing if after you brew and you deep clean and you still see particles in your keg. it is not clean, Keep repeating until your water does not have any particles in it or they can create a clog. Any beer with oats or other starchy grains tend to hang around in the system and create clogs after it sits for a while they can be really stubborn cloggs. Also for support you can try the picobrew Facebook page. I am not on Facebook so I am not a member but I believe it is the only place your going to find an active picobrew user base, Last I heard it was invite only. |
|
@msav72 @ALL... Still not working but I get a new turn on it... Some (English language) terms were hardly understandable at first. The only part I have still keep away from unmount and direct clean is the metal nozzle you point as the source of the problem. I may still have the problem of the clog. What make me thinking about a software issue.
What I may try now.
What I will try
So, stay tuned...And if any advice came in mind, free it from you and share it... |
|
morning tests; same problem ! Then, here, stuck... no more access... still in pumping or something noisy... |
|
Héllo all, The server is ready in a docker with another container for piHole for the dns redirect. The PicoPro contact my home server and I tried to force update... Looks I may have put a PicoC in my PicoPro firmware. I get a huge characters screen, also get black screen... I also get my TTY serial debug in console mode and get some read access (never success to write to console...) I tried another FTDI like adapter to get the cc32tool working. I get one time a factory firmware reset, but cannot reproduce... I am not sure what I can try now. I may search for the full firmware flash from the binary file (actually an ascii content file)
Can someone share its dump (full dump) from a working PiCoPro please ? thanks in advance for all... PS: tips about FB members, it is private, it is closed access, it is fu#k irrespectuous process about unbrain users, so any other trusty, respectuous, minded, network ? (or do I need to code one ?) / HUMOUR, but not only... / |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have get some success with PicoStill which is detect, like my PicoBrew pro, but when I start a PicoStill session, the PicoStill start to apply the correct PSI, the server and PicoStill WEBUI reports correct temperatures and psi, but the distillate process never start !
The PicoBrew screen get lock in the first step with the message :
Priming steam generatorIn the past, with the cloud PicoBrew, I get success in distillate…
Is there anybody who can help me in my distillate adventures…
;-)
The text was updated successfully, but these errors were encountered: