#1

Hi – recently got an Ansible to go with my Grid (Walnut 128 Varibrite model).

All seems to work as it’s supposed to except when I try to tap twice on bottom buttons 6 - 9 to access extended parameters nothing seems to happen – the main parameter just stays lit.

Combed the forum for similar issues but can’t seem to find anything.

Am I just doing something wrong?

Thanks!

#2

Have you installed the proper firmware?

#3

I just ran the firmware update. It says process complete on my Mac. I turned off my system and powered it back on.

Now the Ansible seems unable to detect my grid.

Any thoughts?

#4

actually it appears to be totally dead. my teletype can’t seem to find it anymore either.

should I just try reinstalling the firmware?

#5

Yes

Also, maybe @tehn can help?

#6

@tehn I re-ran the firmware update and got the following message:

Checking memory from 0x2000 to 0x3FFFF… Empty.
Chip already blank, to force erase use --force.
Error opening ansible.hex
See --debug=51 or greater for more information.
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.

Any thoughts?

1 Like
#7

Also just realizing the first time I ran the firmware update this is what it printed:

Checking memory from 0x2000 to 0x3FFFF… Not blank at 0x2001.
Erasing flash… Success
Checking memory from 0x2000 to 0x3FFFF… Empty.
Error opening ansible.hex
See --debug=51 or greater for more information.
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.
Deleting expired sessions…8 completed.

1 Like
#8

Two questions:

  • can you paste exactly what you typed to flash the firmware
  • can you paste the output of ls -lh from the directory you flashed the firmware from?

Error opening ansible.hex is strange, and I want to check that the permissions on the file are correct, and that you’re flashing it from the right directory. Basically, it appears half the process has happened - the part that erases the old firmware - but the new hasn’t been applied yet. Don’t worry: it should be totally possible to resolve this, because we know your computer is connecting correctly to the ansible. It’s just that something was up writing the firmware data.

1 Like
#9

I did it on a MAC and flashed the firmware by double-clicking on the update-firmware.command file that was included in the firmware update package (left in the src directory as downloaded).

This ran the following command:

Danny-Gabai:~ danny.gabai$ /Users/danny.gabai/Downloads/ansible-1.6.0/src/update-firmware.command ; exit;

When I run the 1s -1h command in the directory I get:

Danny-Gabai:src danny.gabai$ ls -lh
total 480
-rwxr-xr-x@ 1 danny.gabai staff 2.8K Apr 17 15:06 Makefile
-rwxr-xr-x@ 1 danny.gabai staff 41K Apr 17 15:06 ansible_arc.c
-rwxr-xr-x@ 1 danny.gabai staff 1.8K Apr 17 15:06 ansible_arc.h
-rwxr-xr-x@ 1 danny.gabai staff 77K Apr 17 15:06 ansible_grid.c
-rwxr-xr-x@ 1 danny.gabai staff 2.8K Apr 17 15:06 ansible_grid.h
-rwxr-xr-x@ 1 danny.gabai staff 45K Apr 17 15:06 ansible_midi.c
-rwxr-xr-x@ 1 danny.gabai staff 1.8K Apr 17 15:06 ansible_midi.h
-rwxr-xr-x@ 1 danny.gabai staff 4.4K Apr 17 15:06 ansible_tt.c
-rwxr-xr-x@ 1 danny.gabai staff 444B Apr 17 15:06 ansible_tt.h
-rwxr-xr-x@ 1 danny.gabai staff 8.0K Apr 17 15:06 config.mk
-rwxr-xr-x@ 1 danny.gabai staff 140B Apr 17 15:06 flash.sh
-rwxr-xr-x@ 1 danny.gabai staff 12K Apr 17 15:06 main.c
-rwxr-xr-x@ 1 danny.gabai staff 1.4K Apr 17 15:06 main.h
-rwxr-xr-x@ 1 danny.gabai staff 172B Apr 17 15:06 update-firmware.command

#10

Bingo.

So, you’ve downloaded the source code itself, rather than a built release. Not your fault: it was the link @Justmat gave you.

Go here:

and download the 1.6.1 release (specifically, the file ansible-1.6.1.zip). In that folder is the update command, and the hex file you need to flash the ansible. I think that should work.

(If you’re interested, the thing you’d downloaded was all the source files that could be compiled into said hex file.).

1 Like
#11

Oh shit! So sorry for the troubles!

Edit: I just did a quick search to find the thread, and shared the first, most relevant post. I should have thought/read a bit more :slight_smile:

#12

Success! And all the extended parameters work now.

Thanks everyone!

2 Likes