- This topic has 5 replies, 3 voices, and was last updated 6 years, 12 months ago by
.
- Posts
So I lost communication with my Mooshimeter, for a while I would see the meter with my tablet, but would get an error 113 when trying to connect to it.
Attempted to remove batteries, press and hold reset button for 5 seconds, so far no luck.
Current LED flash pattern appears to be:
2 blinks, 2 second pause, 3-4?? fast blinks, 10 second pause the repeats.
Prior to this I did have the meter in Logging mode, cannot recall if I shut Logging down before I had the communication failure.
I did find and look over the LED blinking patterns listed, however, mine does not appear to match any of the listed patterns.
Any ideas/suggestions?
J
An update, this seems to be partially self induced.
Here is what went on before I lost connectivity to the meter.
I installed the Moosi App on an iPad in the house because I wanted to compare the iProduct to the Android. I shut down my Android App and then installed the App on the iProduct and connected up to the iProduct without problem or incident.
The problem was when I then wanted to move back to the Android, it can see the meter but cannot reconnect.
I have tried almost everything I can think of. Made sure the App was closed on the iProduct. Removed the batteries from the meter, used the button to reset the meter, forced the meter into Shipping Mode, turned off the Bluetooth on the iProduct, restarted the Android.
For some reason the meter seems to still be married to the iProduct. Almost like an Arpcache type of problem.
I am getting either a Initial Error -1 or a 133 error.
So what I finally did to regain connectivity on the Android is from the iProduct, I put the meter in Shipping Mode, I closed the App on the iProduct, I then turned off the Bluetooth on the iProduct. Then I woke up the meter and attempted to reconnect with the Android and it finally did reconnect.
Unclear if there is something going on with the iProduct and the Bluetooth that keeps the connection even though the App was closed??
I will try to reproduce the situation and try to get a better understanding of what is going on.
Curious if anyone else has seen this type of behavior?
j
Hi jfoj,
So regarding the LED blink patterns – the double blink every 10 seconds means the SD card is successfully mounted. The meter gives a triple blink every time it takes a successful log sample. You can see more information on the blink patterns here:
https://moosh.im/wiki/index.php/LED_Blink_Patterns
Regarding connection to Android device after connecting to iOS device: The app does not automatically terminate the connection when you put the app in the background. So unless you explicitly disconnected the meter (by tapping the connection icon from the “scan” page of the app), the meter was probably still connected to the iOS device, which could explain why you were having problems connecting from Android.
Hope this helps, did I miss anything? Best
~JamesJames,
Thanks for the reply, this kind of makes sense?
So I actually double tapped the Home button and then swiped upwards on the IOS device to close the Moosi App. BUT, does the BT connection still stay alive in the background even though the App is closed? I think this may be the case now that I think about how the BT connection may be working.
I did see the LED pattern page you posted, you might want to put some examples on the page when you have a combination of things going on and how to decipher them. I think my Log interval was in fact set to 10 seconds and this may be why there was the 10 second pause between triple LED blinks.
Example, so in my case, it was unclear if the meter was in Standby Mode with the 2 blinks because I was not officially connected to the App??
But at the same time the Logging was probably still enabled so this is why I probably saw the fast triple blink every 10 seconds along with a slower double blink pattern.
It seems that there is a slow blink and a fast blink of the LED’s which is not very clear in the LED Blink Pattern Wiki. You also use the term “chirp” which typically references sound, not flashes. I would also think that a “chirp” would be a faster flash if I had to make the connection.
Maybe a YouTube video with examples would be more obvious?
Please understand I look at the world more from just my point of view. This product likely will be used by people with different native languages and I have personally worked much of Europe and I fully understand how language translations, slang and other terms can easily get confused. I deal with a lot of translated German documentation and not only are there many translation challenges, there are many semantic problems as well and I have to read between the lines all the time and also correct people with properly understanding some of the statements.
I am not trying to be difficult, I just look at the much larger picture and always play outside of the lines.
Thanks for your continued support and efforts.
j
Hi j,
So I actually double tapped the Home button and then swiped upwards on the IOS device to close the Moosi App. BUT, does the BT connection still stay alive in the background even though the App is closed? I think this may be the case now that I think about how the BT connection may be working.
I thought that the BT connection closed when the app was force-quit. If you want to make super sure, you can turn off bluetooth on the phone from the iOS swipe-up menu.
Thanks for the comments. One of my greatest regrets in designing the Mooshimeter is only putting a single LED for visible output, if I do another hardware version putting clearer user feedback is at the top of my list. A video is a good idea. The reason I didn’t make one sooner is that I wasn’t sure I would keep the blink codes the way they are. But they’ve been this way for about 6 months and communicate the necessary information, so I think they’ll stick around.
Thanks again
~JamesI think you could still use the single LED and get more feedback to the user.
Stealing from something else.
You could have a LED flash flag that will allow you to get a point of reference. Think Morse Code sort of.
You have a starting “marker” of one flash, then 2 flashes repeated 2 to 3 times, this gives the user a starting reference, then the LED can flash “numerical” patterns or codes, maybe once, then the starting “marker” is flashed again to alert the user to the end or the start of the sequence again.
I realize there are power conservation issues and other things, but maybe there is a group of codes ever 1 minute in addition to a “heartbeat” to indicate what the meter is doing.
I have PLENTY of ideas if you want to get deeper into this.
j
