#1

Did it; got an Ansible and Grid.

Largely, with a little patience, it’s making sense. Wonderful interface, and having four tracks of CV out is just splendid.

However, I’m having some technical problems, which may or may not be user error.

Pressing and holding Config 2 has no effect at all. Nothing happens, and the grid is dark and does not respond to any input.

The module and Grid also froze three times yesterday evening, necessitating a complete power cycle to get it back up.

I’ve attempted to update the firmware, which is presenting its own challenges.

I’m on OSX 10.7.3.

Initial homebrew install was fine.

Running “brew install dfu-programmer” yielded “-bash: brew: command not found”

Tried to continue anyway.

Update instructions are vague about which front panel button to press and hold when powering up; I’ve tried all three.

Tried to run “update-firmware.command” anyway which yielded

“/ansible-1.0/update-firmware.command: line 3: dfu-programmer: command not found
/ansible-1.0/update-firmware.command: line 4: dfu-programmer: command not found
/ansible-1.0/update-firmware.command: line 5: dfu-programmer: command not found
logout”

So what should I be doing or what am I doing wrong?

#2

Not sure about the rest but to update it’s the button to the right of the USB port. Just power up holding the button then let go. I had issues way back when I first got my white whale but once I got it it’s set up forever.

1 Like
#3

Thanks Michael. That’s what I thought, but couldn’t be sure.

#4

Can you type echo $PATH in a terminal and paste the output.

#5

/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin

#6

Next up, type which -a brew and paste again please

#7

It just returns my command prompt. Nothing else.

#8

Right, reboot the computer (sorry!).

Try which -a brew again, and if it still returns nothing then can you paste the output of ls /usr/local and ls /usr/local/bin

#9

i can confirm this bug. it happens when running kria: neither side of the grid responds as the docs say it should when trying to change note or loop sync. this is on the default firmware, pre-1.0. will test the newest version later.

it looks like the homebrew installation didn’t properly set environment variables, such as updating ${PATH}. or it may have been installed in your home directory somewhere, not systemwide in /usr. according to the homebrew docs, your version of OSX is too old – 10.10 is the required minimum. you may need to grab an older homebrew download and follow the instructions for certain workarounds.

1 Like
#10

I had to make sure to not have the USB cable plugged in to the module when powering up in bootlouader mode.

#11

That’s expected behavior. Pre-1.0 didn’t have the config menu. You can see that Note + Loop Sync are new in 1.0: Ansible 1.0

1 Like
#12

Thanks everyone for the input.

Okay, so Config 2 doing nothing is expected. I’m still grappling with the upgrade. Sam, I tried the additional commands but they didn’t work, which after reading loflow’s comments, is expected.

I tried to follow and make sense of the links related to older Homebrew docs, but that’s simply out of my depth, and I don’t have the time to get familiar enough with what’s happening in there to make it work.

I’m upgrading my OS; it’s time I did anyway, and we’ll try again.

Anyone care to speculate if the freezing is related to pre-1.0 as well? I was running two tracks, nothing complicated, in Kria.

#13

Updated to OSX 10.12

Ran Homebrew install again. Seemed to work, but got asked for a password. Stumped. What password?

Hit enter, seemed okay.

Ran brew install dfu-programmer and nothing happened.

Ran the update script anyway, and got this:

/ansible-1.0/update-firmware.command: line 3: dfu-programmer: command not found
/ansible-1.0/update-firmware.command: line 4: dfu-programmer: command not found
/ansible-1.0/update-firmware.command: line 5: dfu-programmer: command not found
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.

[Process completed]

Stll did not work.

I’ve tried several times, booting up Ansible with USB cord connected, with it not connected, restarted computer, tried everything again, still no luck. Nothing happening on Config 2.

#14

Should be your user account password. If you don’t have one, it’s possible you need to create a root account?

(Sorry, not really a Mac guy but taking a stab.)

#15

Yep, what ppqq said. I was stuck at the password thing for a while, but you just enter your computer’s user account password that you would use to log in to your computer, download an app, or change a security parameter, etc.

It should work as expected after that!

#16

Thanks for that.

Yes, that’s what I thought.

My “what password” was partly in reference to the lack of any mention of it in the documentation; to that, and to any of the other potential issues I’m encountering. I don’t script, and until Friday, had never heard of Homebrew, never used my terminal, and things like git, ruby, perl, brew, etc., mean nothing to me.

I used my standard password my Macs have always asked me for when updating software, etc., and the password was accepted–i.e., there was no “incorrect password” response–but then nothing happened. I tried it twice. The second time, I walked away for half an hour to let the thing run, and nothing happened. Then, both times, when I tried to close the terminal window, I got a warning message asking if I was sure I wanted to terminate the session.

I also tried entering “brew install dfu-programmer” after entering my password, then running the script again after booting up Ansible, and again, no luck.

My frustration level is increasing. It would be really great if someone from Monome could address this here.

#17

The install requires an Internet connection I believe. Also, you might want to temporarily disable your security settings. This shouldn’t be an issue but you never know.

I understand your frustration with never going thru processes like this. But once you get things working, it should continue to work. So future upgrades should be a breeze.

#18

Paging @tehn. There are a lot of threads in this forum, and just one tehn.

Can you paste the output please?

1 Like
#19

Thanks, and I have that on that system. I was tabbing back and forth between the instructions on Monome’s site, the Homebrew site, etc.

Thank you too; there was no output at all. The insert point moved down one line and remained there, blank.

#20

i’ve been keeping track, but the information posted here by other gracious users is incredibly detailed and correct-- they’ve been getting to it before i do.

first, let’s figure out if you actually have installed homebrew. did you do it again and enter your password?

if it succeeded, you should be able to type “brew” into the terminal and something besides “command not found” will show.