Hi,
In the Pduino test patch ("arduino-test.pd") there is a subpatch called "old analog/digital controls".
This includes a series of toggles which send the message "analogIns X Y" (where X is the analog pin to enable/disable and Y is either 0 or 1).
With the version I'm testing (which is Firmata 2.1 on an Arduino Duemilanove) those messages are actually needed in order to get the analog inputs to work.
Maybe those messages aren't needed with Firmata 2.2? That would explain the "old" in the subpatch name.
Thanks m.
ej m i also noticed this during workshopping some time ago but it just got lost in the backyard of my brain... nice that you mentioned it again! i also had to enable analogIns through the "old analog/digital controls" subpatch or "analogIns X 1" message. in the arduino-help.pd there's a toggle for this but strangely enough also here you've to send enable "analogIns X Y" the first time you connect the arduino! hans maybe add the enable "analogIns X Y" message to arduino-help.pd.
best ø
On 05/18/2011 01:39 PM, Matteo Sisti Sette wrote:
Hi,
In the Pduino test patch ("arduino-test.pd") there is a subpatch called "old analog/digital controls".
This includes a series of toggles which send the message "analogIns X Y" (where X is the analog pin to enable/disable and Y is either 0 or 1).
With the version I'm testing (which is Firmata 2.1 on an Arduino Duemilanove) those messages are actually needed in order to get the analog inputs to work.
Maybe those messages aren't needed with Firmata 2.2? That would explain the "old" in the subpatch name.
Thanks m.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
That's the original way of controlling the analog inputs. It just
controls whether the Arduino sends the analog messages. Its there
only for backwards compatibility. Use the non-old messages now.
.hc
On May 19, 2011, at 10:07 AM, olsen wrote:
ej m i also noticed this during workshopping some time ago but it just
got lost in the backyard of my brain... nice that you mentioned it again! i also had to enable analogIns through the "old analog/digital
controls" subpatch or "analogIns X 1" message. in the arduino-help.pd there's a toggle for this but strangely
enough also here you've to send enable "analogIns X Y" the first
time you connect the arduino! hans maybe add the enable "analogIns X Y" message to arduino-help.pd.best ø
On 05/18/2011 01:39 PM, Matteo Sisti Sette wrote:
Hi,
In the Pduino test patch ("arduino-test.pd") there is a subpatch
called "old analog/digital controls".This includes a series of toggles which send the message "analogIns
X Y" (where X is the analog pin to enable/disable and Y is either 0 or 1).With the version I'm testing (which is Firmata 2.1 on an Arduino
Duemilanove) those messages are actually needed in order to get the analog inputs to work.Maybe those messages aren't needed with Firmata 2.2? That would
explain the "old" in the subpatch name.Thanks m.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- ETs DNA will not be televised http://hasa-labs.org
If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an
idea, which an individual may exclusively possess as long as he keeps
it to himself; but the moment it is divulged, it forces itself into
the possession of everyone, and the receiver cannot dispossess himself
of it. - Thomas Jefferson
On 05/19/2011 04:45 PM, Hans-Christoph Steiner wrote:
That's the original way of controlling the analog inputs. It just controls whether the Arduino sends the analog messages. Its there only for backwards compatibility. Use the non-old messages now.
okedoke - for the matter of integrity this should be included in the arduino-help.pd otherwise people only looking at arduino-help.pd get confused?
salutis ø
.hc
On May 19, 2011, at 10:07 AM, olsen wrote:
ej m i also noticed this during workshopping some time ago but it just got lost in the backyard of my brain... nice that you mentioned it again! i also had to enable analogIns through the "old analog/digital controls" subpatch or "analogIns X 1" message. in the arduino-help.pd there's a toggle for this but strangely enough also here you've to send enable "analogIns X Y" the first time you connect the arduino! hans maybe add the enable "analogIns X Y" message to arduino-help.pd.
best ø
On 05/18/2011 01:39 PM, Matteo Sisti Sette wrote:
Hi,
In the Pduino test patch ("arduino-test.pd") there is a subpatch called "old analog/digital controls".
This includes a series of toggles which send the message "analogIns X Y" (where X is the analog pin to enable/disable and Y is either 0 or 1).
With the version I'm testing (which is Firmata 2.1 on an Arduino Duemilanove) those messages are actually needed in order to get the analog inputs to work.
Maybe those messages aren't needed with Firmata 2.2? That would explain the "old" in the subpatch name.
Thanks m.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- ETs DNA will not be televised http://hasa-labs.org
If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it. - Thomas Jefferson
That's the original way of controlling the analog inputs. It just controls whether the Arduino sends the analog messages. Its there only for backwards compatibility. Use the non-old messages now.
What are the non-old messages? Maybe I should study the firmata documentation instead of just playing around with these patches, but looking at the arduino-test and arduino-help patches I can't see any way of enabling analog inputs (i.e. have the arduino send them) other than these "old" messages.
I guess it's in front of my eyes and I don't see it...
thanks m.
Hi,
I bring this up again after some further testing:
I:
In the Pduino test patch ("arduino-test.pd") there is a subpatch called "old analog/digital controls". ... "analogIns X Y" (where X is the analog pin to enable/disable and Y is either 0 or 1).
Hans-Christoph Steiner:
That's the original way of controlling the analog inputs. It just controls whether the Arduino sends the analog messages. Its there only for backwards compatibility. Use the non-old messages now.
I:
What are the non-old messages? looking at the arduino-test and arduino-help patches I can't see any way of enabling analog inputs
I didn't get any answer but i found out that the message "pinMode 14 analog" worked like "analogIns 0 1" (being pin 14 the same as A0)
However, actually this works _only_ on older versions of Firmata and doesn't work with the latest version.
By latest version I mean the StandardFirmata and StandardFirmata_2_2_for_UNO_0_3 example sketches packed with the latest version of the Arduino IDE (latest available package for Debian unstable).
With the latest version, the only way I've found that actually works to enable analog input pins are the so-called "old" messages analogIns <npin> <1/0>
Can anybody please clarify?
Thanks m.
With the latest version, the only way I've found that actually works to enable analog input pins are the so-called "old" messages analogIns <npin> <1/0>
/listinfo/pd-list
I was mentioning that before. I had the same problem.
There is another problem with the digital ins 1 and 2. I got myself a workaround. Unfortunately I don't remember anymore what it was exactly. It happened when you went from pin 1 or 2 to another one and back. The first value came out as a "0" instead of the correct version. I think it had to do with the fact that pins 1-8 should form a 8-bit number but 1+2 are part of another 8-bit number or something like that.
It happens somewhere in the part of the "mapping".
Ingo
On Jun 13, 2011, at 1:48 PM, Ingo wrote:
With the latest version, the only way I've found that actually works to enable analog input pins are the so-called "old" messages analogIns <npin> <1/0>
/listinfo/pd-list
I was mentioning that before. I had the same problem.
There is another problem with the digital ins 1 and 2. I got myself a workaround. Unfortunately I don't remember anymore what it was
exactly. It happened when you went from pin 1 or 2 to another one and back. The
first value came out as a "0" instead of the correct version. I think it
had to do with the fact that pins 1-8 should form a 8-bit number but 1+2 are
part of another 8-bit number or something like that.It happens somewhere in the part of the "mapping".
Ingo
I'm totally swamped these days, getting ready for a baby that's coming
soon. Please submit bug reports, patches, help file updates, and I'll
get to it when I can.
.hc
"We have nothing to fear from love and commitment." - New York Senator
Diane Savino, trying to convince the NY Senate to pass a gay marriage
bill
On Mon, 2011-06-13 at 13:57 -0400, Hans-Christoph Steiner wrote:
On Jun 13, 2011, at 1:48 PM, Ingo wrote:
With the latest version, the only way I've found that actually works to enable analog input pins are the so-called "old" messages analogIns <npin> <1/0>
/listinfo/pd-list
I was mentioning that before. I had the same problem.
There is another problem with the digital ins 1 and 2. I got myself a workaround. Unfortunately I don't remember anymore what it was
exactly. It happened when you went from pin 1 or 2 to another one and back. The
first value came out as a "0" instead of the correct version. I think it
had to do with the fact that pins 1-8 should form a 8-bit number but 1+2 are
part of another 8-bit number or something like that.It happens somewhere in the part of the "mapping".
Ingo
I'm totally swamped these days, getting ready for a baby that's coming
soon. Please submit bug reports, patches, help file updates, and I'll
get to it when I can.
@Ingo and Matteo
I'm also quite interested in having the [arduino] working properly. I didn't find any bugs recently, though. However, if you provide a step-by-step guide about how to reproduce a problem, I (and probably Olsen also) might be able to help, as I know the code inside a bit, although I'm not the author (as long as the problem exists on the Pd side and not on the Firmata side). Regarding the help and test files, we just improve what needs improvement. I hear that this is OK with Hans.
@Hans
I wish you guys good luck and a happy baby!
Roman
On Jun 13, 2011, at 3:09 PM, Roman Haefeli wrote:
On Mon, 2011-06-13 at 13:57 -0400, Hans-Christoph Steiner wrote:
On Jun 13, 2011, at 1:48 PM, Ingo wrote:
With the latest version, the only way I've found that actually
works to enable analog input pins are the so-called "old" messages analogIns <npin> <1/0>/listinfo/pd-list
I was mentioning that before. I had the same problem.
There is another problem with the digital ins 1 and 2. I got
myself a workaround. Unfortunately I don't remember anymore what it was exactly. It happened when you went from pin 1 or 2 to another one and back. The first value came out as a "0" instead of the correct version. I think it had to do with the fact that pins 1-8 should form a 8-bit number but 1+2 are part of another 8-bit number or something like that.It happens somewhere in the part of the "mapping".
Ingo
I'm totally swamped these days, getting ready for a baby that's
coming soon. Please submit bug reports, patches, help file updates, and
I'll get to it when I can.@Ingo and Matteo
I'm also quite interested in having the [arduino] working properly. I didn't find any bugs recently, though. However, if you provide a step-by-step guide about how to reproduce a problem, I (and probably Olsen also) might be able to help, as I know the code inside a bit, although I'm not the author (as long as the problem exists on the Pd side and not on the Firmata side). Regarding the help and test files, we just improve what needs improvement. I hear that this is OK with Hans.
Definitely, please improve!
@Hans
I wish you guys good luck and a happy baby!
Thanks!
hc
You can't steal a gift. Bird gave the world his music, and if you can
hear it, you can have it. - Dizzy Gillespie
On 06/13/2011 09:09 PM, Roman Haefeli wrote:
@Ingo and Matteo
I'm also quite interested in having the [arduino] working properly. I didn't find any bugs recently, though. However, if you provide a step-by-step guide about how to reproduce a problem, I (and probably Olsen also) might be able to help,
Ok, the problem is that in my case I'm not sure whether I'm experiencing an issue, an incorrectness in the test patch, or just my lack of knowledge of how it is _expected_ to behave.
With both old and new versions of the StandardFirmata firmware the following message enables analog input from pin A0 (i.e. pin 14):
"analogIns 0 1" (0 means A0 and 1 means on)
But in the test patch this is enclosed in a subpatch calles "old analog/digital controls" so is it supposed to be obsolete?
The only other way I've seemed to find to enable input from analog pin A0 is:
"pinMode 14 analog"
which seems to be the "suggested" way in the test patch (offered with the pink grid on the upper-right part of the patch),
but this only works with OLD versions of StandardFirmata.
So it looks like either: a. there is a third, current, non-obsolete, recommended way of doing that which I don't know b. the "suggested" way is the old one and the one documented as "old" is actually the new one (but I don't think so, that's not what Chris said) c. something isn't working right
The same happens with both Arduino 2009 (with the "StandardFirmata" sketch) and with an Arduino UNO (with the StandardFirmata_2_2_for_UNO_0_3). Both sketches are those that ship with the latest package of the Arduino IDE for Debian sid.
The older StandardFirmata sketch where the "pinMode N analog" message worked were taken from an older version of the arduino package for Ubuntu from the official repository, but I don't remember the version number.
The exact same thing that Matteo mentioned about the old analogue method is happening here, too. Tested with Diecimila and Duemilanove. I was also using the test patch as a starting patch. My workaraound was simply to use the old method (after for searching for quite some time).
I need to find the other problem with the digital Ins 1+2 giving wrong values will first. I will post a patch to reproduce it asap but it might take a couple of days to look for it. I had a workaround for it already but I do not know if this workaround could still be applied with other boards like the mega. As far as I remember it was a problem of the firmata sending wrong data rather than the pd patch doing something wrong.
Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag von Matteo Sisti Sette Gesendet: Dienstag, 14. Juni 2011 16:26 An: Roman Haefeli Cc: 'PD List' Betreff: Re: [PD] pduino test patch: "old analog/digital controls"
On 06/13/2011 09:09 PM, Roman Haefeli wrote:
@Ingo and Matteo
I'm also quite interested in having the [arduino] working properly. I didn't find any bugs recently, though. However, if you provide a step-by-step guide about how to reproduce a problem, I (and probably Olsen also) might be able to help,
Ok, the problem is that in my case I'm not sure whether I'm experiencing an issue, an incorrectness in the test patch, or just my lack of knowledge of how it is _expected_ to behave.
With both old and new versions of the StandardFirmata firmware the following message enables analog input from pin A0 (i.e. pin 14):
"analogIns 0 1" (0 means A0 and 1 means on)
But in the test patch this is enclosed in a subpatch calles "old analog/digital controls" so is it supposed to be obsolete?
The only other way I've seemed to find to enable input from analog pin A0 is:
"pinMode 14 analog"
which seems to be the "suggested" way in the test patch (offered with the pink grid on the upper-right part of the patch),
but this only works with OLD versions of StandardFirmata.
So it looks like either: a. there is a third, current, non-obsolete, recommended way of doing that which I don't know b. the "suggested" way is the old one and the one documented as "old" is actually the new one (but I don't think so, that's not what Chris said) c. something isn't working right
The same happens with both Arduino 2009 (with the "StandardFirmata" sketch) and with an Arduino UNO (with the StandardFirmata_2_2_for_UNO_0_3). Both sketches are those that ship with the latest package of the Arduino IDE for Debian sid.
The older StandardFirmata sketch where the "pinMode N analog" message worked were taken from an older version of the arduino package for Ubuntu from the official repository, but I don't remember the version number.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
eo
as i mentioned in my previous post the enabling of the analogIns was also somehow confusing for me, though now i found out it's all in the arduino-help.pd by Gerda Strobl and Georg Holzmann!
in the last subpatch [pd SWITCHING-INPUTS] you'll find the apropriate messages. i don't know why this is commented with (optional) but maybe this - also due to this thread - should be placed more prominent within the help-patch. as mentioned by roman we're currently doing some improvements on the whole pduino dingdongs & i'll try to find a solution - suggestions are welcome.
i guess it's a firmata peculiarity that you've explicit have to enable the analog pins as in arduino they are enabled by default - but correct me if i'm wrong.
hth ø
ej hans all the best for your genealogical tree extension!!
On 06/14/2011 04:51 PM, Ingo wrote:
The exact same thing that Matteo mentioned about the old analogue method is happening here, too. Tested with Diecimila and Duemilanove. I was also using the test patch as a starting patch. My workaraound was simply to use the old method (after for searching for quite some time).
I need to find the other problem with the digital Ins 1+2 giving wrong values will first. I will post a patch to reproduce it asap but it might take a couple of days to look for it. I had a workaround for it already but I do not know if this workaround could still be applied with other boards like the mega. As far as I remember it was a problem of the firmata sending wrong data rather than the pd patch doing something wrong.
Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag von Matteo Sisti Sette Gesendet: Dienstag, 14. Juni 2011 16:26 An: Roman Haefeli Cc: 'PD List' Betreff: Re: [PD] pduino test patch: "old analog/digital controls"
On 06/13/2011 09:09 PM, Roman Haefeli wrote:
@Ingo and Matteo
I'm also quite interested in having the [arduino] working properly. I didn't find any bugs recently, though. However, if you provide a step-by-step guide about how to reproduce a problem, I (and probably Olsen also) might be able to help,
Ok, the problem is that in my case I'm not sure whether I'm experiencing an issue, an incorrectness in the test patch, or just my lack of knowledge of how it is _expected_ to behave.
With both old and new versions of the StandardFirmata firmware the following message enables analog input from pin A0 (i.e. pin 14):
"analogIns 0 1" (0 means A0 and 1 means on)
But in the test patch this is enclosed in a subpatch calles "old analog/digital controls" so is it supposed to be obsolete?
The only other way I've seemed to find to enable input from analog pin A0 is:
"pinMode 14 analog"
which seems to be the "suggested" way in the test patch (offered with the pink grid on the upper-right part of the patch),
but this only works with OLD versions of StandardFirmata.
So it looks like either: a. there is a third, current, non-obsolete, recommended way of doing that which I don't know b. the "suggested" way is the old one and the one documented as "old" is actually the new one (but I don't think so, that's not what Chris said) c. something isn't working right
The same happens with both Arduino 2009 (with the "StandardFirmata" sketch) and with an Arduino UNO (with the StandardFirmata_2_2_for_UNO_0_3). Both sketches are those that ship with the latest package of the Arduino IDE for Debian sid.
The older StandardFirmata sketch where the "pinMode N analog" message worked were taken from an older version of the arduino package for Ubuntu from the official repository, but I don't remember the version number.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 06/16/2011 05:44 PM, olsen wrote:
it's all in the arduino-help.pd by Gerda Strobl and Georg Holzmann!
Which one???
Not the one that is distributed together with [arduino] and [arduino-test] at http://at.or.at/hans/pd/objects.html, right?
in the last subpatch [pd SWITCHING-INPUTS] you'll find the apropriate messages.
There I find the same analogIns messages that are supposed to be the old ones (but are the only ones I've found that work for analog pins with the latest version of Firmata)
i don't know why this is commented with (optional)
I must have another version of the help patch, as I don't see such a comment
How are the messages you're talking about?
i guess it's a firmata peculiarity that you've explicit have to enable the analog pins as in arduino they are enabled by default - but correct me if i'm wrong.
Yes, I guess what you have to explicitly enable is to have the firmware _send_ the values to the computer. It would be undesirable to have a constant flood of values of all pins whether you use them or not.
On 06/17/2011 12:24 AM, Matteo Sisti Sette wrote:
On 06/16/2011 05:44 PM, olsen wrote:
it's all in the arduino-help.pd by Gerda Strobl and Georg Holzmann!
Which one???
Not the one that is distributed together with [arduino] and [arduino-test] at http://at.or.at/hans/pd/objects.html, right?
yo it's in Pduino-0.5beta8 linked on this page
in the last subpatch [pd SWITCHING-INPUTS] you'll find the apropriate messages.
There I find the same analogIns messages that are supposed to be the old ones (but are the only ones I've found that work for analog pins with the latest version of Firmata)
jep i agree they're the same - i think it's a matter of wrong denotation so due to my knowledge there's nothing like old and newer messages -> the current 'contemporary' message for enabling the analog inputs is: [analogIns pinumber 1=on; 0=off( f.e. to enable analog pin 1: [analogIns 1 1( correct me if i'm wrong!
i don't know why this is commented with (optional)
I must have another version of the help patch, as I don't see such a comment
right behind the [pd SWITCHING-INPUTS] is a comment "<- example of switching inputs on and off (optional)"
How are the messages you're talking about?
i guess it's a firmata peculiarity that you've explicit have to enable the analog pins as in arduino they are enabled by default - but correct me if i'm wrong.
Yes, I guess what you have to explicitly enable is to have the firmware _send_ the values to the computer. It would be undesirable to have a constant flood of values of all pins whether you use them or not.
jep right so with firmata the analogIns have to be enabled explicitly to use them. i think the (optional) comment somehow makes it ambiguous. as told i'll try to consider this in the improvements we're working on!
salutis ø
yo bonitos
due to the pduino rewrite I've to reanimate this threat ;) I would like to remove the ambiguity and confusion about this old and new way of enabling the analog pins.
old way of enabling the analog 0 pin is sending the following to the arduino object: [analogIns 0 1(
enabling the same pin(analog 0) the new school way: [pinMode 14 analog(
is this correct? if so what's a bit byte confusing for people is that in the new way pin 14 equals the analog 0 pin - guess this is a peculiarity of firmata? isn't there a possability to use f.e. A0-A5 for adressing the analog pins?
thanks for info & salutis ø
On 06/17/2011 10:52 AM, olsen wrote:
On 06/17/2011 12:24 AM, Matteo Sisti Sette wrote:
On 06/16/2011 05:44 PM, olsen wrote:
it's all in the arduino-help.pd by Gerda Strobl and Georg Holzmann!
Which one???
Not the one that is distributed together with [arduino] and [arduino-test] at http://at.or.at/hans/pd/objects.html, right?
yo it's in Pduino-0.5beta8 linked on this page
in the last subpatch [pd SWITCHING-INPUTS] you'll find the apropriate messages.
There I find the same analogIns messages that are supposed to be the old ones (but are the only ones I've found that work for analog pins with the latest version of Firmata)
jep i agree they're the same - i think it's a matter of wrong denotation so due to my knowledge there's nothing like old and newer messages -> the current 'contemporary' message for enabling the analog inputs is: [analogIns pinumber 1=on; 0=off( f.e. to enable analog pin 1: [analogIns 1 1( correct me if i'm wrong!
i don't know why this is commented with (optional)
I must have another version of the help patch, as I don't see such a comment
right behind the [pd SWITCHING-INPUTS] is a comment "<- example of switching inputs on and off (optional)"
How are the messages you're talking about?
i guess it's a firmata peculiarity that you've explicit have to enable the analog pins as in arduino they are enabled by default - but correct me if i'm wrong.
Yes, I guess what you have to explicitly enable is to have the firmware _send_ the values to the computer. It would be undesirable to have a constant flood of values of all pins whether you use them or not.
jep right so with firmata the analogIns have to be enabled explicitly to use them. i think the (optional) comment somehow makes it ambiguous. as told i'll try to consider this in the improvements we're working on!
salutis ø
That confusion originates from the Arduino numbering scheme itself, since it uses A0 for analog pins in analog mode, but then it uses a number when using the same pin for digital things.
I think one way to represent this might be to allow the use of A0-A7 pin names in addition to the numbers, but then the confusing thing would be that the analog messages would then be [analog 14 0.2352(. So that's why I thought to try to use only the numbers, no A0-A7, and try to make that as understandable as possible.
.hc
On Nov 3, 2011, at 6:57 AM, olsen wrote:
yo bonitos
due to the pduino rewrite I've to reanimate this threat ;) I would like to remove the ambiguity and confusion about this old and new way of enabling the analog pins.
old way of enabling the analog 0 pin is sending the following to the arduino object: [analogIns 0 1(
enabling the same pin(analog 0) the new school way: [pinMode 14 analog(
is this correct? if so what's a bit byte confusing for people is that in the new way pin 14 equals the analog 0 pin - guess this is a peculiarity of firmata? isn't there a possability to use f.e. A0-A5 for adressing the analog pins?
thanks for info & salutis ø
On 06/17/2011 10:52 AM, olsen wrote:
On 06/17/2011 12:24 AM, Matteo Sisti Sette wrote:
On 06/16/2011 05:44 PM, olsen wrote:
it's all in the arduino-help.pd by Gerda Strobl and Georg Holzmann!
Which one???
Not the one that is distributed together with [arduino] and [arduino-test] at http://at.or.at/hans/pd/objects.html, right?
yo it's in Pduino-0.5beta8 linked on this page
in the last subpatch [pd SWITCHING-INPUTS] you'll find the apropriate messages.
There I find the same analogIns messages that are supposed to be the old ones (but are the only ones I've found that work for analog pins with the latest version of Firmata)
jep i agree they're the same - i think it's a matter of wrong denotation so due to my knowledge there's nothing like old and newer messages -> the current 'contemporary' message for enabling the analog inputs is: [analogIns pinumber 1=on; 0=off( f.e. to enable analog pin 1: [analogIns 1 1( correct me if i'm wrong!
i don't know why this is commented with (optional)
I must have another version of the help patch, as I don't see such a comment
right behind the [pd SWITCHING-INPUTS] is a comment "<- example of switching inputs on and off (optional)"
How are the messages you're talking about?
i guess it's a firmata peculiarity that you've explicit have to enable the analog pins as in arduino they are enabled by default - but correct me if i'm wrong.
Yes, I guess what you have to explicitly enable is to have the firmware _send_ the values to the computer. It would be undesirable to have a constant flood of values of all pins whether you use them or not.
jep right so with firmata the analogIns have to be enabled explicitly to use them. i think the (optional) comment somehow makes it ambiguous. as told i'll try to consider this in the improvements we're working on!
salutis ø
-- ETs DNA will not be televised http://hasa-labs.org
There is no way to peace, peace is the way. -A.J. Muste
Thanks Hans for making this thing clear - I'll try to find an adequate solution for the rewritten pduino-help asap!
best ø
On 11/03/2011 03:39 PM, Hans-Christoph Steiner wrote:
That confusion originates from the Arduino numbering scheme itself, since it uses A0 for analog pins in analog mode, but then it uses a number when using the same pin for digital things.
I think one way to represent this might be to allow the use of A0-A7 pin names in addition to the numbers, but then the confusing thing would be that the analog messages would then be [analog 14 0.2352(. So that's why I thought to try to use only the numbers, no A0-A7, and try to make that as understandable as possible.
.hc
On Nov 3, 2011, at 6:57 AM, olsen wrote:
yo bonitos
due to the pduino rewrite I've to reanimate this threat ;) I would like to remove the ambiguity and confusion about this old and new way of enabling the analog pins.
old way of enabling the analog 0 pin is sending the following to the arduino object: [analogIns 0 1(
enabling the same pin(analog 0) the new school way: [pinMode 14 analog(
is this correct? if so what's a bit byte confusing for people is that in the new way pin 14 equals the analog 0 pin - guess this is a peculiarity of firmata? isn't there a possability to use f.e. A0-A5 for adressing the analog pins?
thanks for info& salutis ø
On 06/17/2011 10:52 AM, olsen wrote:
On 06/17/2011 12:24 AM, Matteo Sisti Sette wrote:
On 06/16/2011 05:44 PM, olsen wrote:
it's all in the arduino-help.pd by Gerda Strobl and Georg Holzmann!
Which one???
Not the one that is distributed together with [arduino] and [arduino-test] at http://at.or.at/hans/pd/objects.html, right?
yo it's in Pduino-0.5beta8 linked on this page
in the last subpatch [pd SWITCHING-INPUTS] you'll find the apropriate messages.
There I find the same analogIns messages that are supposed to be the old ones (but are the only ones I've found that work for analog pins with the latest version of Firmata)
jep i agree they're the same - i think it's a matter of wrong denotation so due to my knowledge there's nothing like old and newer messages -> the current 'contemporary' message for enabling the analog inputs is: [analogIns pinumber 1=on; 0=off( f.e. to enable analog pin 1: [analogIns 1 1( correct me if i'm wrong!
i don't know why this is commented with (optional)
I must have another version of the help patch, as I don't see such a comment
right behind the [pd SWITCHING-INPUTS] is a comment "<- example of switching inputs on and off (optional)"
How are the messages you're talking about?
i guess it's a firmata peculiarity that you've explicit have to enable the analog pins as in arduino they are enabled by default - but correct me if i'm wrong.
Yes, I guess what you have to explicitly enable is to have the firmware _send_ the values to the computer. It would be undesirable to have a constant flood of values of all pins whether you use them or not.
jep right so with firmata the analogIns have to be enabled explicitly to use them. i think the (optional) comment somehow makes it ambiguous. as told i'll try to consider this in the improvements we're working on!
salutis ø
-- ETs DNA will not be televised http://hasa-labs.org
There is no way to peace, peace is the way. -A.J. Muste
heho
i just put my attempt for a solution considering this pin numbering confusion into github: https://github.com/reduzent/pduino take a look if time and leisure permitting - I'm herewith opening the suggestion box!
thanks in advance & salutis ø
On 11/09/2011 09:54 AM, olsen wrote:
Thanks Hans for making this thing clear - I'll try to find an adequate solution for the rewritten pduino-help asap!
best ø
On 11/03/2011 03:39 PM, Hans-Christoph Steiner wrote:
That confusion originates from the Arduino numbering scheme itself, since it uses A0 for analog pins in analog mode, but then it uses a number when using the same pin for digital things.
I think one way to represent this might be to allow the use of A0-A7 pin names in addition to the numbers, but then the confusing thing would be that the analog messages would then be [analog 14 0.2352(. So that's why I thought to try to use only the numbers, no A0-A7, and try to make that as understandable as possible.
.hc
On Nov 3, 2011, at 6:57 AM, olsen wrote:
yo bonitos
due to the pduino rewrite I've to reanimate this threat ;) I would like to remove the ambiguity and confusion about this old and new way of enabling the analog pins.
old way of enabling the analog 0 pin is sending the following to the arduino object: [analogIns 0 1(
enabling the same pin(analog 0) the new school way: [pinMode 14 analog(
is this correct? if so what's a bit byte confusing for people is that in the new way pin 14 equals the analog 0 pin - guess this is a peculiarity of firmata? isn't there a possability to use f.e. A0-A5 for adressing the analog pins?
thanks for info& salutis ø
On 06/17/2011 10:52 AM, olsen wrote:
On 06/17/2011 12:24 AM, Matteo Sisti Sette wrote:
On 06/16/2011 05:44 PM, olsen wrote:
it's all in the arduino-help.pd by Gerda Strobl and Georg Holzmann!
Which one???
Not the one that is distributed together with [arduino] and [arduino-test] at http://at.or.at/hans/pd/objects.html, right?
yo it's in Pduino-0.5beta8 linked on this page
in the last subpatch [pd SWITCHING-INPUTS] you'll find the apropriate messages.
There I find the same analogIns messages that are supposed to be the old ones (but are the only ones I've found that work for analog pins with the latest version of Firmata)
jep i agree they're the same - i think it's a matter of wrong denotation so due to my knowledge there's nothing like old and newer messages -> the current 'contemporary' message for enabling the analog inputs is: [analogIns pinumber 1=on; 0=off( f.e. to enable analog pin 1: [analogIns 1 1( correct me if i'm wrong!
i don't know why this is commented with (optional)
I must have another version of the help patch, as I don't see such a comment
right behind the [pd SWITCHING-INPUTS] is a comment "<- example of switching inputs on and off (optional)"
How are the messages you're talking about?
i guess it's a firmata peculiarity that you've explicit have to enable the analog pins as in arduino they are enabled by default - but correct me if i'm wrong.
Yes, I guess what you have to explicitly enable is to have the firmware _send_ the values to the computer. It would be undesirable to have a constant flood of values of all pins whether you use them or not.
jep right so with firmata the analogIns have to be enabled explicitly to use them. i think the (optional) comment somehow makes it ambiguous. as told i'll try to consider this in the improvements we're working on!
salutis ø
-- ETs DNA will not be televised http://hasa-labs.org
There is no way to peace, peace is the way. -A.J. Muste
-
Hans-Christoph Steiner -
Ingo -
Matteo Sisti Sette -
matteo sisti sette
-
olsen -
Roman Haefeli