![]() ![]() If needs be, as a non-programmer I would spend time learning the communication relationship between the Arduino board and an edit text parser style interface, because I have the need to undertake projects that would value the efficiency dividend provided by the Firmata integration. However it comes to pass, access to the board elements in a simplified but clearly articulated integration that works is going to be the bottom line. I guess this represents some kind of 'wizard' interface that would allow the display and modification of properties and parameters associated with the board identified with a serial port. ![]() With addition of specifying in and out link ports on the actor itself. I don't think there is any example within the native Isadora actors. Examples of that kind of control interface can be found in the AU audio actors. Personally I would like to have the extended properties and parameters associated with the integration presented as a dialog interface when double clicking on the actor. Is this correct? or does the integration suggest that active pins on the board would be auto detected and PIN lines auto generated? The Arduino Firmata actor would expand dependent on how many PIN lines are articulated within an edit text parser pop out. I have plans for more ambitious projects for festivals in the August/September season this year, so the potential of what I understand from reading up about the Firmata protocol over the last couple of days has some appeal.įrom what I interpret from the Firmata Actor Help document that has been provided, the Arduino Firmata actor will be somewhat similar to the existing Serial In Watcher and Send Serial Data group of actors but within a single actor integration. For more elaborate projects I have worked with experienced programmers to create Isadora based communications using OSC and wireless boards. For the Arduino sketches I have relied on modification of sketch code provided through Arduino forums etc. I have Uno and Micro boards that have been integrated into the Isadora workflow with simple sketches, things like triggering relays on/off, hacking remote controller to turn appliances on/off and simple sensor input like pulse sensor and accelerometers etc. But I can also see that by auto populating the actor, it would be easier for the non-programmer.īest have not used the Firmata protocol before but have managed a few simple projects using Arduino boards. If you changed the function from output to input, you'd need to move the actual value from the input side of the actor to the output side. ![]() That means 34 inputs on the actor given the list shown above. If you were to auto-populate the actor, a way similar to the app shown above, there would be two inputs for each pin: the function and the value. If you were to show every pin on the board in the actor, you'd get a long list that would look a little bit like the Firmata test app shown below. So, it can be either a digital input or an output, which means the Isadora actor would have a corresponding output property or an input property. Pin 2: digital input digital output servo input_pullup For example, PIN 2 on my board offers all these capabilities: I see what you're saying, but the issue is that the "capabilities" information offers all the capabilities of the board - that doesn't indicate what you want to do. Otherwise as a programmer, this solution also seems quite straightforward. Especially since this is an "Arduino for Non-Programmers"-actor. that way everything is selectable through options. with the response you could populate the inputs and outputs of the actor. If you would add an active flag, you can have the actor send a BoardCapabilities Request when enabling. First off: is this necessary? I know Firmata can do a board capabilities request (sysex 0圆B, i believe). He did not post them in this said: I have been looking at the instructions. [EDIT: to all and and - I copied these comments from Tony from the Isadora User Group Global on Facebook.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |