search

monome / ansible

http://monome.org/docs/ansible
GNU General Public License v2.0
64 stars 26 forks source link

Grid freeze #26

Closed fluxxion82 closed 6 years ago

fluxxion82 commented 6 years ago

When using the 128 varibright grid with a Switch connected to Ansible(latest firmware v1.5.0), probably within 10 min of use, the grid freezes up. Sometimes I can still see the pulse going through all the steps, and other times there's no pulse movement. Every time though, I can not move to any of the menu items or change any params in the current menu on the grid; I can't switch tracks, and go to the notes or durations, etc. Ansible continues to play though. In order to get the grid back to normal, (if using an external clock, I have to stop the external clock), using the switch module I switch to the other output, which currently isn't being used, then switch back to the Ansible connection. Once I do those steps, the grid starts to function normally. Haven't tried other firmware versions as I just bought the Ansible.

tehn commented 6 years ago

though you haven't tried other versions, have you reflashed the firmware to confirm the newest is present?

On Sun, Aug 6, 2017 at 6:08 PM Sterling Albury notifications@github.com wrote:

When using the 128 varibright grid with a Switch connected to Ansible(latest firmware v1.5.0), probably within 10 min of use, the grid freezes up. Sometimes I can still see the pulse going through all the steps, and other times there's no pulse movement. Every time though, I can not move to any of the menu items or change any params in the current menu on the grid; I can't switch tracks, and go to the notes or durations, etc. Ansible continues to play though. In order to get the grid back to normal, (if using an external clock, I have to stop the external clock), using the switch module I switch to the other output, which currently isn't being used, then switch back to the Ansible connection. Once I do those steps, the grid starts to function normally. Haven't tried other firmware versions as I just bought the Ansible.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/monome/ansible/issues/26, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPEcCpWgmrE9M4ybY9-SE9QstCziAtSks5sVjlbgaJpZM4Ou2zp .

fluxxion82 commented 6 years ago

Yeah, I reflashed the firmware again and so far everything is looking good; the grid hasn't frozen up since. I'll close the issue. Thanks.

fluxxion82 commented 6 years ago

Actually, I take that back..it just froze on me again. I feel like maybe having an external clock might be playing a part. I'll install the previous version and see if I have any issues.

samdoshi commented 6 years ago

Sounds like it relates to this bug: https://llllllll.co/t/is-it-normal-for-ansible-to-freeze-after-a-lot-of-arc-activity/4735

fluxxion82 commented 6 years ago

Interesting. Definitely sounds like something is going on. I just posted a quick blurb there. I'm really feeling like, for me at least, having an external clock is triggering the issue. Last night I was going to start trying other firmware versions but decided to reflash the latest firmware and see how long it runs without freezing without an external clock, and so far it's still going. I switched the grid off while I was asleep and at work, but switched the grid back to Ansible and it's still going. I'll play around with it for a couple hours and if it's still going, I'll hook up the external clock and see how long it takes.

Edit: The grid worked fine for two nights with no external clock with Ansible. After a playing with Ansible for a couple hours this evening, I hooked up an external clock source and reset (Pamela's Workout at x32 clock in, and one output for reset - the 'nn' setting on the output that sends a signal when stopping and stopping), modified global and individual time divisions, and after about 35 min, the grid froze. The pulse indicator is still moving but I'm unable to move to different tracks or menus. On a slightly related note, if I remove the external clock, the internal clock doesn't seem to start back up. This is after the freeze. Before it locks up, if I remove the external clock the internal clock starts again.

-- Edit 2: Saw the link to the new firmware, ansible-1.5.1b01 that seems to fix the issue. I'll test that firmware out tomorrow after work. Thanks.

samdoshi commented 6 years ago

Can you try the firmware from this post:

https://llllllll.co/t/ansible-grid-arc-become-unresponsive-after-period-of-time/7900/20?u=sam

tehn commented 6 years ago

added 1.5.1 release which fixes.