I will have to go through the script and C code to give you an idea. I can say that the JS I provide works - you can copy that code as a starting point.
Ok, thanks!I will have to go through the script and C code to give you an idea. I can say that the JS I provide works - you can copy that code as a starting point.
I will have to go through the script and C code to give you an idea. I can say that the JS I provide works - you can copy that code as a starting point.
Thank you. I am working on a debug version to collect additional information and I should have that available in a few hours.It happened again
ThanksThank you. I am working on a debug version to collect additional information and I should have that available in a few hours.
This also helps - the debugging will still help, but now at least you know testing will involve drinking.Looks like issue happened on time of pouring beer
Dan I found something that leads me to believe the fix I intended to be in .6 did not make it. This specifically prevents connecting to MQTT by name. If I am right, your fix for that will be in .7 when I can wrap a couple more things up. If it's working for you now, the new debug probably will not work for you.But the console log on Alpha 6 makes it look like it's not making the connection:
Here:Can you please point where the "Checking handleTapPost" handler implemented?
It isn't (so I'll look forward to the next release), but I'm just using the KegCop display for now rather than rPints.If it's working for you now, the new debug probably will not work for you.
/flowdebuglog.txt
and share the information it returns.I am torn on that - while we are using it a lot here, I wonder if we leave it as a hidden "ninja switch" when we get things working well.Just flashed to Alpha 7. Nice to see there's a link to /fs/ on the About page.
Yeah ... well I needed to get that debug version out there to get some data collected. I did just finish the re-work on the upload, and I am considering another release with just that change.Not so nice to see this when trying to upload the config files:
... said nobody nowhere.Fortunately, JSON isn't hard to read, and it isn't all that much to reenter.
I mean, sure, I'd rather not have to do it, but I'd downloaded them anyway (did you intend that people be able to just browse to /appconfig.json? Because you can--which makes it convenient to download that and flowconfig), and it's easy enough to get the necessary information out of it for this purpose.... said nobody nowhere.
Is this something that's created only in the event of a crash? Because it's 404 for me.navigate to/flowdebuglog.txt
and share the information it returns.
Just for you (and me, if I am honest), here is Alpha 8 which restores the file upload. Actually, it's a new file upload but the same thing for you:I mean, sure, I'd rather not have to do it, but I'd downloaded them anyway
I could secure it by "secret," but I don't want to make things harder on anyone while chasing this darned bug. It is a bit of a security issue, as we've addressed, however, it's not a state secret and it's unlikely to create any more havoc than someone changing your tap info.(did you intend that people be able to just browse to /appconfig.json? Because you can--which makes it convenient to download that and flowconfig), and it's easy enough to get the necessary information out of it for this purpose.
Yes. It will only be created in the event the controller tries to load the flowmeter (taps) file, and the file is not there or the data is gone. The choice there is the core of my issue, to address it I'd like to know why it's happening. Either one will result in a default file being created which is what wipes out your details.Is this something that's created only in the event of a crash? Because it's 404 for me.
/flowdebuglog.txt
in the event of a tap information loss. That information will guide my next steps.Alpha .9 is ready for testing
https://web.brewflasher.com/fw/135
This is nearly the same as .8 except for some documentation I needed to complete. If you are using .8 there is no reason to update.
Right now I am at a stopping point until I get some feedback on the information in/flowdebuglog.txt
in the event of a tap information loss. That information will guide my next steps.
That is perfect, thank you. If I can get a couple more reports, and hopefully they are the same, I can put in a fix.This is from the .7 firmware but the flowdebuglog.txt file only has this -
[DEBUGFLOW] Failed to deserialize file.
John Guest PM450813E Female Connector, 8 mm x 3/8" BSPP (Pack of 10) John Guest PM450813E Female Connector, 8 mm x 3/8" BSPP (Pack of 10): Amazon.com: Industrial & ScientificDoes anyone have a part number for the connector that goes on the breakout for attaching to the swissflo connector? There is some talk a while back that mentions various connectors but none seem to be correct.
In @Thorrak post, Keg Cop: Keg Monitoring and Control, there is a picture showing what appears to be the correct connector. Or is this just a modified incorrect connector?
Sorry I wasn't clear, meant the white "molex" connector that gets soldered to the breakout board.John Guest PM450813E Female Connector, 8 mm x 3/8" BSPP (Pack of 10) John Guest PM450813E Female Connector, 8 mm x 3/8" BSPP (Pack of 10): Amazon.com: Industrial & Scientific
Ohh, got it. Yeah, it’s the correct connector.Sorry I wasn't clear, meant the white "molex" connector that gets soldered to the breakout board.
Part Affected | |
---|---|
Manufacturer | MOLEX, LLC |
Description | CONN HEADER VERT 3POS 2MM |
Manufacturer Part Number | 0533240360 |
Digi-Key Part Number | WM8313-ND |
Status | Obsolete |
Substitutes | Please click here |
Ohh, got it. Yeah, it’s the correct connector.
Molex part number 51090-0300 is the plug end — the receptacle end I bought is EOL, however. Here is the EOL notification I received from DigiKey:
Part Affected Manufacturer MOLEX, LLC Description CONN HEADER VERT 3POS 2MM Manufacturer Part Number 0533240360 Digi-Key Part Number WM8313-ND Status Obsolete Substitutes Please click here
Please please double check the substitutes they recommend for both footprint and pitch. I bought the actual Molex part — the substitutes are other manufacturers.
Which breakout board? The six-way one which I designed is intended to use JST-XH connectors. I can't speak for the three-way board.Sorry I wasn't clear, meant the white "molex" connector that gets soldered to the breakout board.
Which breakout board? The six-way one which I designed is intended to use JST-XH connectors. I can't speak for the three-way board.
Interesting. Yes, 404 is good news.Sorry Lee, since updating to Alpha .9 around a week ago I've not lost any data and getting a 404 on the flowdebuglog.txt. No news is good news I guess?
Not yet. RPints version of MQTT was working but I seem to have broken it in that version. I know that because I just fixed it.Is this expected to have MQTT working?
A step file is a common format that allows for 3d models to be exchanged between different CAD apps. So this allows for export and sharing of the model itself rather than the generated stl file uses as a base for 3d printing.I’m sure I have the original files, but I don’t know what a step file is. I model in AutoCAD only.
Send me DM and we can get you sorted out, I’m sure.
Enter your email address to join: