Flow meter not recognized

[mik3y]

Continued from Kegbot/kegbot-server#266

cc @grendel513

[mik3y]

@grendel513 b67 is in Play

[grendel513]

We updated to the latest version on Play. The app now does recognize the flow meeter, however even though the LED light flickers on/off and the kegboard-monitor.py script does detect flow, the app does not.

Additionally, every time the board is plugged in to the table it wants to register it as a new controller.

I have submitted a few bugreports for you to take a look at.

Thanks,

Jay

[grendel513]

Here is the output from kegboard-monitor.py

jay.paz@jpaz-mac [ ~  ]$ kegboard-monitor.py
Waiting for a kegboard ...
Found: <Kegboard path=/dev/tty.usbmodem1411 speed=115200>
Listening to board ...
<HelloMessage: protocol_version=None firmware_version=17 serial_number=>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.625>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.25>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.625>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.1875>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.6875>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.125>
<MeterStatusMessage: meter_name=flow0 meter_reading=1>
<MeterStatusMessage: meter_name=flow0 meter_reading=6>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.6875>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.125>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.6875>
<MeterStatusMessage: meter_name=flow0 meter_reading=11>
<MeterStatusMessage: meter_name=flow0 meter_reading=21>
<MeterStatusMessage: meter_name=flow0 meter_reading=29>
<MeterStatusMessage: meter_name=flow0 meter_reading=39>
<MeterStatusMessage: meter_name=flow0 meter_reading=48>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.125>
<MeterStatusMessage: meter_name=flow0 meter_reading=49>
<MeterStatusMessage: meter_name=flow0 meter_reading=60>
<MeterStatusMessage: meter_name=flow0 meter_reading=77>
<MeterStatusMessage: meter_name=flow0 meter_reading=87>
<MeterStatusMessage: meter_name=flow0 meter_reading=89>
<MeterStatusMessage: meter_name=flow0 meter_reading=90>
<MeterStatusMessage: meter_name=flow0 meter_reading=94>
<MeterStatusMessage: meter_name=flow0 meter_reading=102>
<MeterStatusMessage: meter_name=flow0 meter_reading=115>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.75>
<MeterStatusMessage: meter_name=flow0 meter_reading=149>
<MeterStatusMessage: meter_name=flow0 meter_reading=166>
<MeterStatusMessage: meter_name=flow0 meter_reading=185>
<MeterStatusMessage: meter_name=flow0 meter_reading=195>
<MeterStatusMessage: meter_name=flow0 meter_reading=203>
<MeterStatusMessage: meter_name=flow0 meter_reading=207>
<MeterStatusMessage: meter_name=flow0 meter_reading=208>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.0625>
<MeterStatusMessage: meter_name=flow0 meter_reading=212>
<MeterStatusMessage: meter_name=flow0 meter_reading=223>
<MeterStatusMessage: meter_name=flow0 meter_reading=236>
<MeterStatusMessage: meter_name=flow0 meter_reading=250>
<MeterStatusMessage: meter_name=flow0 meter_reading=263>
<MeterStatusMessage: meter_name=flow0 meter_reading=282>
<MeterStatusMessage: meter_name=flow0 meter_reading=300>
<MeterStatusMessage: meter_name=flow0 meter_reading=322>
<MeterStatusMessage: meter_name=flow0 meter_reading=337>
<MeterStatusMessage: meter_name=flow0 meter_reading=352>
<MeterStatusMessage: meter_name=flow0 meter_reading=369>
<MeterStatusMessage: meter_name=flow0 meter_reading=381>
<MeterStatusMessage: meter_name=flow0 meter_reading=394>
<MeterStatusMessage: meter_name=flow0 meter_reading=403>
<MeterStatusMessage: meter_name=flow0 meter_reading=405>
<MeterStatusMessage: meter_name=flow0 meter_reading=407>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.6875>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.0625>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.6875>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.0>
<TemperatureReadingMessage: sensor_name=thermo-43000004d8f5d228 sensor_reading=26.6875>
<TemperatureReadingMessage: sensor_name=thermo-77000004d87bf728 sensor_reading=10.0>

[mik3y]

<HelloMessage: protocol_version=None firmware_version=17 serial_number=>

Please program a board serial number; use the program set-kegboard-serialnumber from the command line.

[grendel513]

That did the trick...thanks. Maybe that step should be added to the instructions?

On Sat, May 10, 2014 at 12:18 PM, mike w notifications@github.com wrote:

Please program a board serial number; use the program set-kegboard-serialnumber from the command line.

— Reply to this email directly or view it on GitHubhttps://github.com/Kegbot/kegbot-android/issues/90#issuecomment-42748139 .

[mik3y]

@grendel513 We rolled back the change requiring board serial numbers; sorry for the hassles.

[grendel513]

Thanks for letting me know. How will this affect my set up? Do I need to do anything?

~ jay

On May 27, 2014, at 8:54 PM, mike w notifications@github.com wrote:

@grendel513 We rolled back the change requiring board serial numbers; sorry for the hassles.

— Reply to this email directly or view it on GitHub.

[mik3y]

Thanks for letting me know. How will this affect my set up? Do I need to do anything?

You shouldn't need to do anything: Serial numbers are used to distinguish between like Kegboards on the same system. If you plug in another Kegboard at the same time, it must have a serial number, otherwise the app will refuse to use it.

[zylantha]

Can't the app recognise a kegboard that doesn't have a serial number, and ask if you want to automatically assign one to it (and then of course write it to the board) ?

On 28 May 2014 12:10, mike w notifications@github.com wrote:

Thanks for letting me know. How will this affect my set up? Do I need to do anything?

You shouldn't need to do anything: Serial numbers are used to distinguish between like Kegboards on the same system. If you plug in another Kegboard at the same time, it must have a serial number, otherwise the app will refuse to use it.

— Reply to this email directly or view it on GitHubhttps://github.com/Kegbot/kegbot-android/issues/90#issuecomment-44357944 .

[mik3y]

Can't the app recognise a kegboard that doesn't have a serial number, and ask if you want to automatically assign one to it (and then of course write it to the board) ?

Yes, we did that in 22ba5a90 and it was causing problems. Since that change was a ungainly in the first place, we reverted that part of it. I expect we'll revisit it soon.