Forgot your password?
New user?
Document Actions
MAKEcontroller
Up one levelrequest on implementing the MAKEcontroller usb interface
- ll.mcusb.pat — by klaus filip — last modified 2007-02-07 17:37
- second test
- data_out — by klaus filip — last modified 2007-01-28 14:53
- first draft of sendig data to the MC
- All MC ins — by Frank Cebreros — last modified 2007-01-29 04:05
- All analog and digital MC card ins
- all_in — by klaus filip — last modified 2007-01-30 22:43
- try this: the metro is replaced by a qmetro and this triggers only 4 requests a time. the repeat-time is defined by the throttle. (something like 20 could make sense here)
- Act edit — by Frank Cebreros — last modified 2007-01-31 01:17
- I cannot edit the act.
- leztes data_out — by Frank Cebreros — last modified 2007-02-03 00:01
- data_out_#0.fixed — by klaus filip — last modified 2007-02-03 00:44
- All MC-card outs — by Frank Cebreros — last modified 2007-02-05 06:10
- Digital, Motor, PWM, Stepper and Servo data out for the MAKEController card
- new_scetch — by klaus filip — last modified 2007-02-07 03:56
MAKEcontroller first test
Posted by
klaus filip
at
2007-01-26 23:36
my first Q is if you do max-programming yourself?
and then please describe more how your setup is thought.
do you want to control devices via max or lloopp?
and i do not see how you define the names of the parameters.
are there default-names by the hardware?
here is a first test:

put the file ll.mcusb.pat into lloopp_externals/lloopp.absternulls/abstractions/filip (or actually somewhere in max' searchpath) .
and replace control@.pat in lloopp_externals/lloopp.acts.
then relaunch lloopp, open control@ and select mc.usb from the input-menu.
with some luck you should imediately get values from your device into the routing-window.
and then please describe more how your setup is thought.
do you want to control devices via max or lloopp?
and i do not see how you define the names of the parameters.
are there default-names by the hardware?
here is a first test:

put the file ll.mcusb.pat into lloopp_externals/lloopp.absternulls/abstractions/filip (or actually somewhere in max' searchpath) .
and replace control@.pat in lloopp_externals/lloopp.acts.
then relaunch lloopp, open control@ and select mc.usb from the input-menu.
with some luck you should imediately get values from your device into the routing-window.
...
Posted by
klaus filip
at
2007-01-26 23:36
No luck with the first try, I had no value at all.
Yes I do some max programming myself.
My setup right now with the MC is the following, in the first analogin
I use an expression pedal, in the following 2 analogins I have
pressure sensors and in the following 2, switches, I use with some
rigged shoes. The 2 following analogins are connected to the CVouts of
my theremin. As outputs I'm using only a led on a digitalout as a
visual check.
My prime intention is to generate and/or process sounds wit lloopp
using the data from the shoes. The theremin data I'm trying to use to
do some video fx.
The parameters are default names of the hardware.
Best regards
Frank
Yes I do some max programming myself.
My setup right now with the MC is the following, in the first analogin
I use an expression pedal, in the following 2 analogins I have
pressure sensors and in the following 2, switches, I use with some
rigged shoes. The 2 following analogins are connected to the CVouts of
my theremin. As outputs I'm using only a led on a digitalout as a
visual check.
My prime intention is to generate and/or process sounds wit lloopp
using the data from the shoes. The theremin data I'm trying to use to
do some video fx.
The parameters are default names of the hardware.
Best regards
Frank
...
Posted by
klaus filip
at
2007-01-26 23:47
can you please open ll.mcusb from the finder, connect a print to mc.ubs and turn on
the metro.
if you get values writen into the max-window please try again
with control@, make sure its turned ON and also open the "subpatch" from
the title-menu and locate the ll.mcusb to open it from within the act......
...for the lloopp-2-MC side we have to think about.
what should the LED be indicating?
it works!
Posted by
Frank Cebreros
at
2007-01-27 01:18
It works the ll.mcusb patch had a mistake (my fault). The metro was conected directly to the mc.usb and not to the message box requesting the data and from there to the mc.usb. I fixed it and saved it, opened it inside lloopp and had data incoming.
The led is a general indicator, nothing special (for the moment).
Thanks
Frank
The led is a general indicator, nothing special (for the moment).
Thanks
Frank
cool !
Posted by
klaus filip
at
2007-01-27 02:37
do you want to send values to the led "back" out (think of it as sending back to a motorfader) ?
or do you want to send lloopp-data out?
do you have a patch that is sending out?
best
klaus
or do you want to send lloopp-data out?
do you have a patch that is sending out?
best
klaus
requesting data
Posted by
klaus filip
at
2007-01-27 02:40
another thing is to request all data from the mc.usb.
if it needs that an cannot get a message that requests ALL data we need to know all the names...
if it needs that an cannot get a message that requests ALL data we need to know all the names...
data
Posted by
Frank Cebreros
at
2007-01-27 17:27
I want to send lloopp-data out. Like to use the frack1 to drive servos or dimm lights, with the digitalout it has no sense because it has only two states, but with the pwm or motor out it would work.
There is no message to request all the data.
There are 8 analogins:
/analogin/0/value, /analogin/1/value, /analogin/2/value, /analogin/3/value,
/analogin/4/value, /analogin/5/value, /analogin/6/value, /analogin/7/value
and 8 digitalins:
/digitalin/0/value, /digitalin/1/value, /digitalin/2/value, /digitalin/3/value,
/digitalin/4/value, /digitalin/5/value, /digitalin/6/value, /digitalin/7/value
There is also the problem that you can not request all the values at the same time, I have tried it and the card crashes. So there must be a slight delay between every request.
Best regards
Frank
There is no message to request all the data.
There are 8 analogins:
/analogin/0/value, /analogin/1/value, /analogin/2/value, /analogin/3/value,
/analogin/4/value, /analogin/5/value, /analogin/6/value, /analogin/7/value
and 8 digitalins:
/digitalin/0/value, /digitalin/1/value, /digitalin/2/value, /digitalin/3/value,
/digitalin/4/value, /digitalin/5/value, /digitalin/6/value, /digitalin/7/value
There is also the problem that you can not request all the values at the same time, I have tried it and the card crashes. So there must be a slight delay between every request.
Best regards
Frank
data_out
Posted by
klaus filip
at
2007-01-28 15:03
i made a quick draft for sending data out.
i took the servo-message written in the help-file as a starting point.
you can add whatever you want. important steps:
place a named(!) userinterface in the main-patch (the name can be anything else as well
like maybe shorter just "val1"). then create a [r #0.same_name] in the subpatch and connect this accordingly.
for the incoming data-request you would have to test how fast you can get all the data in. maybe with a counter connected to the metro to step through all your names.
i took the servo-message written in the help-file as a starting point.
you can add whatever you want. important steps:
place a named(!) userinterface in the main-patch (the name can be anything else as well
like maybe shorter just "val1"). then create a [r #0.same_name] in the subpatch and connect this accordingly.
for the incoming data-request you would have to test how fast you can get all the data in. maybe with a counter connected to the metro to step through all your names.
All ins
Posted by
Frank Cebreros
at
2007-01-29 04:12
I have uploaded a patch that requests all inputs. I have tested it and it works although I get an error message pattrmarker:No such object. It also slows the computer down a little, I suppose because of the high data flow.
Frank
Frank
usb message
Posted by
Frank Cebreros
at
2007-01-29 04:37
I get an error message with the data_out act when I move the faders. USB message: error Packet Error. Don't know what it means.
Best regards
Frank
Best regards
Frank
..
Posted by
klaus filip
at
2007-01-30 22:47
please try to strip this down....connect a print aside with mac.usb...see what exactly is sent, and if the error appears at each output...or only if something goes too fast...
motor out
Posted by
Frank Cebreros
at
2007-01-29 23:49
I have uploaded a working data_out act. I have used the motor instead of servo message because of my setup. I had no problem to edit the subpatch but I coudn't edit the interface ( add buttons/faders or change names).
Thanks
Frank
Thanks
Frank
edit the interface...
Posted by
klaus filip
at
2007-01-30 22:18
i started with writing a "documentation" about this at http://lloopp.klingt.org/plone/lloopp/documentation/developer-edit-acts/
so please go there and comment (or edit) there if something is unclear.
so please go there and comment (or edit) there if something is unclear.
Growbutton
Posted by
Frank Cebreros
at
2007-01-31 01:13
When I click the grow button in de titlebar the window grows, but blank, the act interface stays the same size in the upper left corner and I can't change the size.
grow-button
Posted by
klaus filip
at
2007-02-01 00:20
ah ja, i forgot about this issue on XP.
i also never knew how to get around this obvious max-bug in the windows version.
currently my windows-max is expired, so i have to wait one day or two for to get the response from cyclings. and then i will try to find a workaround. it must be related to the windows settings we do in lloopp with no title and no grow.
i also never knew how to get around this obvious max-bug in the windows version.
currently my windows-max is expired, so i have to wait one day or two for to get the response from cyclings. and then i will try to find a workaround. it must be related to the windows settings we do in lloopp with no title and no grow.
growing
Posted by
klaus filip
at
2007-02-01 02:03
ok this was quick,
got the response and the fix: uploaded in the documentation-section..
got the response and the fix: uploaded in the documentation-section..
#0.TP?
Posted by
Frank Cebreros
at
2007-02-02 03:45
Hi Klaus
All works fine, the new all in works wonderfull and the s and r mcusb solved the problem,THANKS.
But I still can't edit the act interface, I dont understand what you mean with -> ( assuming you opened the act from the File-Open menu -#0 issue) and I recieve an error message, #0.TP:no such object.
Best regards
Frank
All works fine, the new all in works wonderfull and the s and r mcusb solved the problem,THANKS.
But I still can't edit the act interface, I dont understand what you mean with -> ( assuming you opened the act from the File-Open menu -#0 issue) and I recieve an error message, #0.TP:no such object.
Best regards
Frank
#0
Posted by
klaus filip
at
2007-02-02 16:18
hi frank, good for the rest.
so the only thing remaining is this #0-issue.
i think your modified act was already corrupted because you once saved it after you opened it from the act-menu of the ho_st. you need to get this point straight: create a new patch
and create a new object [r #0blabla]. then save this as test.pat and put it into lloopp.acts. then go to ho_st and open this one with the act-menu. you will notice, that the #0blabla now is something like 3425blabla. if you open this a second time from the ho_st, the number will be different. thats the way we can open many acts of the same kind.
only if you open this new patch (test.pat) with the File-open-dialog from max-menubar the #0 will remain #0. so, in your data_out-act you need to open it and revert all objects with a numberBla to #0Bla. oh, i just realize: also in actmaker is this number as an argument now, so you can't do it because its still out of sight.(unless you change #0.TP in the new helper-patch to the stored number...xxxx.TP). ok, please send me your newest data_out again, i will fix it.
so the only thing remaining is this #0-issue.
i think your modified act was already corrupted because you once saved it after you opened it from the act-menu of the ho_st. you need to get this point straight: create a new patch
and create a new object [r #0blabla]. then save this as test.pat and put it into lloopp.acts. then go to ho_st and open this one with the act-menu. you will notice, that the #0blabla now is something like 3425blabla. if you open this a second time from the ho_st, the number will be different. thats the way we can open many acts of the same kind.
only if you open this new patch (test.pat) with the File-open-dialog from max-menubar the #0 will remain #0. so, in your data_out-act you need to open it and revert all objects with a numberBla to #0Bla. oh, i just realize: also in actmaker is this number as an argument now, so you can't do it because its still out of sight.(unless you change #0.TP in the new helper-patch to the stored number...xxxx.TP). ok, please send me your newest data_out again, i will fix it.
all ok
Posted by
Frank Cebreros
at
2007-02-05 03:09
All fine with the new data_out act, it unlocked and I could edit the interface.
THANKS
THANKS
in out trouble
Posted by
Frank Cebreros
at
2007-01-31 01:31
I have found a little problem. I can't open the data_out and an control@1 act at the same time because both try to open the mc.usb object and you can have only one open. It's not veeery important, but is there any way to share the usb output.
Thanks
Frank
Thanks
Frank
in_out trouble
Posted by
klaus filip
at
2007-02-01 00:30
ok i did not know, you cannot have two of them...
so replace the mc.usb in the data_out act with a [s mcusb].
then in our ll.mcusb connect a [r mcusb] to the inlet of mc.usb.
with that all data created in the data_out act will be sent directly to the one
in control@. (which must be always loaded then of course...)
i found another thing in some mc-patch:
/7/ = go to Analog in "7";
/5/ = go to Analog in "6";
/1/ = go to Analog in "1";
/0/ = go to Analog in "0";
/*/ = go to all Analog In "0 -7";
maybe you can check this out, if your device sends all data, when requesting with "*"...
so replace the mc.usb in the data_out act with a [s mcusb].
then in our ll.mcusb connect a [r mcusb] to the inlet of mc.usb.
with that all data created in the data_out act will be sent directly to the one
in control@. (which must be always loaded then of course...)
i found another thing in some mc-patch:
/7/ = go to Analog in "7";
/5/ = go to Analog in "6";
/1/ = go to Analog in "1";
/0/ = go to Analog in "0";
/*/ = go to all Analog In "0 -7";
maybe you can check this out, if your device sends all data, when requesting with "*"...
Frank Cebreros wrote: