#12

Just getting acquainted with Meadowphysics 2.0… before jumping in to 2.1.
When you say the rules are applied to both position and speed… if you don’t set a speed range, then it functions just as it would without a range in 2.0?

#13

correct. you can’t set speed range in 2.0

#14

It seems like it isn’t responding to the teletype i²c commands mp.freeze and mp.mute anymore. Any new ones for the new features (like the clock speed) added instead?

#15

Yeah, my MP2 is also sketchy in terms of responding to TT II commands… some work some don’t.

#16

Just got a TT and trying getting some MP commands as well. I have a USB cable on order, As I don’t know what firmaware is on the MP as I bought it used. But it seems this is still a problem. Responds to reset. Definitely doesn’t respond to mute or freeze.

Earthsea seems to be working flawless.

Any chance the MP not responding to certain commands will be addressed?

#17

I think the freeze and mute commands are ditched since the meadowphysics 2.x fw works in a very different way. There are no more straight forward mapping of rows -> triggers. A row can trigger any trigger now so it’s ambiguous what a mute would mute, the trigger with that number or all the triggers trigged by the row with the number.

1 Like
Teletype 2.0 documentation
#18

Is there any chance this can be updated to the same features as Ansible Meadowphysics? Namely the output of note CV instead of 8 triggers

1 Like
#19

The meadowphysics hardware only has trigger outputs so it isn’t possible to generate CV without additional hardware (if I’m understanding your question correctly).

#20

Ok noted thanks for the info

#21

I can not get rules working on meadowphysics anymore.

Works now - don’t know what I did…:upside_down_face:

#22

Do you want a hand with this? I realized last night that the current firmware for MP doesn’t match the docs on the site, but pretty much matches (I think?) the Ansible docs with the exception of no CV out. If updating the MP docs on the site is about adapting the Ansible MP doc to the MP hardware firmware, I can help with that this coming week. If the intent is to keep the MP docs consistent with the 1.x firmware, that’s a-ok too. Willing to put in some time to get things set up the way you want if it’ll help.

8 Likes
#23

holy smokes, yes i clearly need help. thank you.

2 Likes
#24

Please do update the docs @cmcavoy, I keep needing to look things up and having to find the old thread where it’s discussed.

1 Like
#25

Quick update - I’ve got everything I need to update the docs (found the repositories, have an ansible and meadowphysics module to ‘test’ the docs). I’m not sure what the exact ETA is, but I’m shooting for a PR submitted by the end of this weekend.

8 Likes
#26

I have a draft of the updated docs on github. If users of the MP module with the 2.1 firmware could take a look and make sure everything makes sense, I’d appreciate it. Also - the images need to be updated. I’ve deleted them for now. Is anyone capable of making updates to the grid / MP images? I’m not sure if there’s a template? Also, I used the video from the top of this post as the tutorial video. After a few watch throughs, I don’t think there’s anything in there that conflicts with the MP module version.

5 Likes
#27

thanks you! i’ll make time to check these out soon. (in sweden right now teaching workshops)

@laborcamp is the wizard behind the ansible diagrams, though i should get the AI sources up on github so anyone can hack them up as templates.

2 Likes
#28

@laborcamp - my wife is a graphic designer, if you have templates available in illustrator, she can help me make the diagrams for the updated docs.

1 Like
#29

I created a pull request to make it easier to see the edits.

1 Like
#30

I don’t have the files with me right now (away from home). Will be back next week, and would be happy to send whatever you need. OR make the images you need. Let me know.
p.

1 Like
#31

Next week (or later) is a-ok, no rush. If you send the files, I can just work side by side with my wife and get them done. Are you ok with putting the files in the docs repo for re-use? Meaning they’d be licensed like the docs (which I realize now don’t have a license, but I’ve asked for that to be added.)