#204

oh duh, thanks. is there any way to use a grid in the druid env on a laptop, or is max my best shot?

#206

I’m on version 0.2.1 of druid.

Following your link, I tried to install the new firmware but got this log from dfu-utils:
“No DFU capable USB device available”. It seems the crow is not recognised by my laptop (osx Mojave)… Is there something else I could try? I’ll look for another cable in the meantime :v:

Link to old documentation: https://aidanreilly.github.io/docs/crow/update/#forcing-the-bootloader

#207

Woah. Need to take this down. This is an old build to test the new html docs site.

1 Like
#208

deleted this old fork of the docs repo.

#210

Attempting to get a TXi and crow talking. Am I correct that…

print(ii.txi[1].get('param',1))

Should return the knob value from druid if things are behaving?

edit: Ah. I see. So it’s an event model based thing. So no.

I’m now trying the following on an input clock tick in a known working script:

    ii.txi.get('param', 1)
    ii.txi.event = function(e, data, id)
      if e == 'param' then
        print('recieved')
        print(data)
      end
    end

And no dice. Can someone provide a simple working example of reading data from a TXi? Is there a druid command to verify the two devices can communicate?

#211

ii.***.get sends a single I2C message to poll the value, so you probably would need to register the event callback before calling get. I have not used a TXi but this works for Ansible running Kria, in druid:

> ii.kria.event = function(e, data) print(e .. ' = ' .. data) end

> ii.kria.get('cv', 0)
cv = 0.9985352

I think there are perhaps also some kinks to work out as far as whether crow I2C commands are 0-indexed or 1-indexed, this maybe depends some on the follower implementation. For Ansible I need to request channel 0 to get the first channel.

2 Likes
#212

I’ve added the following to my script:

print('bang')
ii.txi.event = function(e, data) print(e .. ' = ' .. data) end
ii.txi.get('param', 1)

The 'bang’s show up in druid, but not event responses. Hmmmm… getting warmer anyway. Thanks for that!

Sonofagun. I reconnected it to the TT, and it’s not working again. So the a code mistake is probably a ghost. Well, a kind of progress.

#213

I thought I had the same issues you were having with ii.txi.get('param', 1) which was returning nil. But it turns out I had the i2c cables connected to the wrong thing at the back of the TXI. after reconnecting, I get the following:

> ii.txi.get('param', 1)
^^ii.txi([[param]],2.39563,1)
1 Like
#214

Just got my Crow. Carefully following the steps from the docs page for installing to Windows. Python is installed and path is set. Stuck at installing druid.

powershell screenshot
powershell screenshot987×605 157 KB

#215

Get out of powershell. Just run at normal cmd prompt.

#216

It’s telling you you don’t have a program called “pip3”, which is commonly the name on Mac or Ubuntu systems but I think is probably just “pip” on Windows.

#217

performing exact same operation in cmd yields:

‘pip3’ is not recognized as an internal or external command, operable program or batch file

edit: @csboling pip is also not recognized

#218

But python -m pip was working? You should generally be able to do that instead. I’m recalling now that I think Python adds the directory with python.exe to your path but not the scripts/ folder beneath that, which is where pip gets installed. Will take a look at the Windows druid setup docs.

1 Like
#219

Screenshot to confirm:
cmd screenshot

#220

Can you try python -m pip install --upgrade setuptools? And if that works, python -m pip install monome-druid?

2 Likes
#221

It worked! ignore the red error message, I forgot the dash on the first druid install attempt:

install screenshot
install screenshot668×736 235 KB

I am confused about the path warnings as I have set the path according to the guide/what the command prompt reads.

#222

Took a break and came back to launch druid. It cannot detect my crow. I get the disconnected message at druid startup and power cycle with usb connected does not fix it. Windows detects the crow as “crow: telephone line”, and operating by itself the First script runs as advertised.

#223

@chriz when this has happened to me, crow is hung up on a script. force the bootloader using the patch cable to short the i2c lines like the docs show https://monome.org/docs/crow/update/#force and run the erase_userscript.bat from the release zip https://github.com/monome/crow/releases

#224

also i notice the command prompt screenshot above…you might want to have a look at the windows terminal…it’s a much nicer command line experience for windows (no experience running with crow so I don’t know if there are any gotchas, but I did help my boyfriend set up some other command line things and it was much closer to *nix shells) https://devblogs.microsoft.com/commandline/windows-terminal-1-0/

#225

Thank you, but it looks like my crow is not being recognized by dfu-util:

The crow usb bootloader shows up on my computer and I have used Zadig to install the correct driver WinUSB v6.1.7600.16385)

I have dfu-util downloaded/unzipped, added to path, and working. A version check in cmd is successful.

I have the crow firmware folder contents in the same folder as dfu-util

Running either erase_userscript or update_firmware .bat yields “No DFU capable USB device available” though it is powered/connected/recognized

Apologies if these troubleshootings should be in the general thread.