Skip to content

production explorer seems to timeout after one read #9

@kenstack

Description

@kenstack

I initialize my code with an mmtune which is successful - say db=-47

at the start of my loop I run a pump status request via decocare ie tweak ReadPumpStatus
on the first try this returns no problem and I continue to read history temp basal etc etc all no problem
I then sleep for about 4 min until the next loop

since switching to the production board on my first attempted ReadPumpStatus (for clarity I dont do an mmtune again unless needed so in this case no mmtune) im getting the following error
"ERROR:mmeowlink.handlers.stick:Timed out or other comms error - Received an error response Timeout - retrying: 1 of 3\nERROR:mmeowlink.handlers.stick:Timed out or other comms error - Received an error response Timeout - retrying: 2 of 3\nERROR:mmeowlink.handlers.stick:Timed out or other comms error - Received an error response Timeout - retrying: 3 of 3\nERROR:mmeowlink.handlers.stick:1482372001.91 - Response not received - retrying\n"

its quite repeatable and doesnt look like a freq issue rather I cant reach the board
I then tried just a board reset - doesnt seem to work
I do an mmtune and it works again, and subsequent commands are fine - until after my next sleep then the problem occurs again

so now Im basically mmtuning each loop which Id prefer not too jus to save battery and time - any advice? Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions