Yes proper FTDI drivers installed.
The Analog Firmata works, however the Standard Firmata is totally broken.
D.
On 3/9/10 4:27 PM, Greg Pond wrote:
do you have the proper ftdi drivers installed? http://www.ftdichip.com/Drivers/VCP.htm
good luck.
On Tue, Mar 9, 2010 at 7:22 AM, Derek Holzer <derek@umatic.nl mailto:derek@umatic.nl> wrote:
Hi all, I'm in the middle of a workshop right now, and nothing I planned works. All the users on OSX cannot use the Pduino objects. They all have latest Pd-Extended 0.41.4 and latest Pduino-0.5beta6. They have all successfully loaded the Standard-FirmataV2 (the Standard-Firmata is too big for the Atmega8) to an Arduino NG w/ Atmega8. Then they open arduino-help.pd, use "devices" to determine the proper port and set the port. Then I have them test with "pinMode 13 1" followed by "digital 13 1". I see the RX LEDS flash, but the pin 13 LED does nothing. Then I open [pd DIGITAL-OUTPUT] and use that patch to flash all the digital outputs, after setting them to output mode in the main patch. Again, RX lights blink but nothing else. After that I get long strings of the following: UNKNOWN INPUT COMMAND: 8 32120 [arduino] warning currently unsupported 160 [arduino] warning currently unsupported 176 This is consistent across every installation, whether PPC or Intel. We can't really go further with Arduino without fixing this, so I hope someone can help. In contrast, I am using Pduino04.beta2 with Pd-extended-0.39 on my machine and everything works fine. I have also been unble to run any Pduino with Pd-extended-0.41.4. Installing Pduino04.beta2 with Pd-extended-0.39 on a couple of machines of the students hasn't been an effectivbe workaroundm however ([arduino-help.pd] crashes Pd in this case). Any suggestions welcome. Is there something I totally missed here???? D. -- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 48: "Discover your formulas and abandon them" _______________________________________________ Pd-list@iem.at <mailto:Pd-list@iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
You need to match the versions of the Firmata on the Arduino and the
Firmata on Pd. Also, you should not use Firmata from Arduino 0017,
its buggy. Use Arduino 0018.
For ATMEGA8 using OldStandardFirmata, but before uploading, change the
baud rate in setup() to 57600. That's the only change from Firmata
V2.0 to V2.1. V2.0 is 115200 and V2.1 is 57600. Arduino now uses
57600 for everything.
.hc
On Mar 9, 2010, at 10:10 AM, Derek Holzer wrote:
Yes proper FTDI drivers installed.
The Analog Firmata works, however the Standard Firmata is totally
broken.D.
On 3/9/10 4:27 PM, Greg Pond wrote:
do you have the proper ftdi drivers installed? http://www.ftdichip.com/Drivers/VCP.htm
good luck.
On Tue, Mar 9, 2010 at 7:22 AM, Derek Holzer <derek@umatic.nl mailto:derek@umatic.nl> wrote:
Hi all,
I'm in the middle of a workshop right now, and nothing I planned works. All the users on OSX cannot use the Pduino objects. They
all have latest Pd-Extended 0.41.4 and latest Pduino-0.5beta6. They
have all successfully loaded the Standard-FirmataV2 (the Standard- Firmata is too big for the Atmega8) to an Arduino NG w/ Atmega8.Then they open arduino-help.pd, use "devices" to determine the proper port and set the port.
Then I have them test with "pinMode 13 1" followed by "digital 13 1". I see the RX LEDS flash, but the pin 13 LED does nothing.
Then I open [pd DIGITAL-OUTPUT] and use that patch to flash all the
digital outputs, after setting them to output mode in the main patch.
Again, RX lights blink but nothing else.After that I get long strings of the following:
UNKNOWN INPUT COMMAND: 8 32120 [arduino] warning currently unsupported 160 [arduino] warning currently unsupported 176
This is consistent across every installation, whether PPC or
Intel. We can't really go further with Arduino without fixing this, so I hope someone can help.In contrast, I am using Pduino04.beta2 with Pd-extended-0.39 on my machine and everything works fine. I have also been unble to run
any Pduino with Pd-extended-0.41.4. Installing Pduino04.beta2 with Pd-extended-0.39 on a couple of machines of the students hasn't
been an effectivbe workaroundm however ([arduino-help.pd] crashes Pd in this case).Any suggestions welcome. Is there something I totally missed
here????D.
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 48: "Discover your formulas and abandon them"
Pd-list@iem.at mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 158: "Think of the radio"
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Mistrust authority - promote decentralization. - the hacker ethic
Hey HC,
yes I was religious about matching Firmatas between versions. I even had Koray here looking over my shoulder to see if I was doing anything stupid. He agreed that all versions of StandardFirmata we tried were buggy on OSX.
We are using Arduino 18. I don't see OldStandardFirmata anywhere in the Pduino-0.5beta6 zip I downloaded, nor do I see a StandardFirmataV2.1 anywhere. Are we looking at the same download? What are you referring to?
In short, we've gotten AnalogFirmata to work, but not StandardFirmata (too big for Atmega8) or StandardFirmataV2_0 (numerous errors). Some of the student projects require both Analog and Digital outputs, can you pls point me in the direction of something that works?
I will try changing the baudrate in Firmata V2.0 to 57600 and see what happens.
Best, Derek
On 3/9/10 10:38 PM, Hans-Christoph Steiner wrote:
You need to match the versions of the Firmata on the Arduino and the Firmata on Pd. Also, you should not use Firmata from Arduino 0017, its buggy. Use Arduino 0018.
For ATMEGA8 using OldStandardFirmata, but before uploading, change the baud rate in setup() to 57600. That's the only change from Firmata V2.0 to V2.1. V2.0 is 115200 and V2.1 is 57600. Arduino now uses 57600 for everything.
.hc
On Mar 9, 2010, at 10:10 AM, Derek Holzer wrote:
Yes proper FTDI drivers installed.
The Analog Firmata works, however the Standard Firmata is totally broken.
D.
On 3/9/10 4:27 PM, Greg Pond wrote:
do you have the proper ftdi drivers installed? http://www.ftdichip.com/Drivers/VCP.htm
good luck.
On Tue, Mar 9, 2010 at 7:22 AM, Derek Holzer <derek@umatic.nl mailto:derek@umatic.nl> wrote:
Hi all,
I'm in the middle of a workshop right now, and nothing I planned works. All the users on OSX cannot use the Pduino objects. They all have latest Pd-Extended 0.41.4 and latest Pduino-0.5beta6. They have all successfully loaded the Standard-FirmataV2 (the Standard-Firmata is too big for the Atmega8) to an Arduino NG w/ Atmega8.
Then they open arduino-help.pd, use "devices" to determine the proper port and set the port.
Then I have them test with "pinMode 13 1" followed by "digital 13 1". I see the RX LEDS flash, but the pin 13 LED does nothing. Then I open [pd DIGITAL-OUTPUT] and use that patch to flash all the digital outputs, after setting them to output mode in the main patch. Again, RX lights blink but nothing else.
After that I get long strings of the following:
UNKNOWN INPUT COMMAND: 8 32120 [arduino] warning currently unsupported 160 [arduino] warning currently unsupported 176
This is consistent across every installation, whether PPC or Intel. We can't really go further with Arduino without fixing this, so I hope someone can help.
In contrast, I am using Pduino04.beta2 with Pd-extended-0.39 on my machine and everything works fine. I have also been unble to run any Pduino with Pd-extended-0.41.4. Installing Pduino04.beta2 with Pd-extended-0.39 on a couple of machines of the students hasn't been an effectivbe workaroundm however ([arduino-help.pd] crashes Pd in this case).
Any suggestions welcome. Is there something I totally missed here????
D.
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 48: "Discover your formulas and abandon them"
Pd-list@iem.at mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 158: "Think of the radio"
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Mistrust authority - promote decentralization. - the hacker ethic
I just taught a class on Firmata/Pduino with 15 students on Mac OS X
and it worked for all of them. If you think there is a bug, please do
file a bug report. I am wrapping up everything for the Pduino 0.5
release, so it would be good to get more info to make sure it all works.
ATMEGA8's are not really well supported by Arduino any more. You can
get a ATMEGA168 for a few euros, and just swap chips. Its definitely
worth the upgrade.
The vesrion of Firmata included in Arduino 0018 is the best one, but
the one in Pduino-0.5beta6 zip should be fine too. OldStandardFirmata
== StandardFirmataV2_0
.hc
On Mar 9, 2010, at 3:50 PM, Derek Holzer wrote:
Hey HC,
yes I was religious about matching Firmatas between versions. I even
had Koray here looking over my shoulder to see if I was doing
anything stupid. He agreed that all versions of StandardFirmata we
tried were buggy on OSX.We are using Arduino 18. I don't see OldStandardFirmata anywhere in
the Pduino-0.5beta6 zip I downloaded, nor do I see a
StandardFirmataV2.1 anywhere. Are we looking at the same download?
What are you referring to?In short, we've gotten AnalogFirmata to work, but not
StandardFirmata (too big for Atmega8) or StandardFirmataV2_0
(numerous errors). Some of the student projects require both Analog
and Digital outputs, can you pls point me in the direction of
something that works?I will try changing the baudrate in Firmata V2.0 to 57600 and see
what happens.Best, Derek
On 3/9/10 10:38 PM, Hans-Christoph Steiner wrote:
You need to match the versions of the Firmata on the Arduino and the Firmata on Pd. Also, you should not use Firmata from Arduino 0017,
its buggy. Use Arduino 0018.For ATMEGA8 using OldStandardFirmata, but before uploading, change
the baud rate in setup() to 57600. That's the only change from Firmata
V2.0 to V2.1. V2.0 is 115200 and V2.1 is 57600. Arduino now uses 57600 for everything..hc
On Mar 9, 2010, at 10:10 AM, Derek Holzer wrote:
Yes proper FTDI drivers installed.
The Analog Firmata works, however the Standard Firmata is totally
broken.D.
On 3/9/10 4:27 PM, Greg Pond wrote:
do you have the proper ftdi drivers installed? http://www.ftdichip.com/Drivers/VCP.htm
good luck.
On Tue, Mar 9, 2010 at 7:22 AM, Derek Holzer <derek@umatic.nl mailto:derek@umatic.nl> wrote:
Hi all,
I'm in the middle of a workshop right now, and nothing I planned works. All the users on OSX cannot use the Pduino objects. They all have latest Pd-Extended 0.41.4 and latest Pduino-0.5beta6. They
have all successfully loaded the Standard-FirmataV2 (the Standard- Firmata is too big for the Atmega8) to an Arduino NG w/ Atmega8.Then they open arduino-help.pd, use "devices" to determine the proper port and set the port.
Then I have them test with "pinMode 13 1" followed by "digital 13 1". I see the RX LEDS flash, but the pin 13 LED does nothing.
Then I open [pd DIGITAL-OUTPUT] and use that patch to flash all the
digital outputs, after setting them to output mode in the main patch.
Again, RX lights blink but nothing else.After that I get long strings of the following:
UNKNOWN INPUT COMMAND: 8 32120 [arduino] warning currently unsupported 160 [arduino] warning currently unsupported 176
This is consistent across every installation, whether PPC or Intel. We can't really go further with Arduino without fixing this, so I hope someone can help.
In contrast, I am using Pduino04.beta2 with Pd-extended-0.39 on my machine and everything works fine. I have also been unble to run
any Pduino with Pd-extended-0.41.4. Installing Pduino04.beta2 with Pd-extended-0.39 on a couple of machines of the students hasn't
been an effectivbe workaroundm however ([arduino-help.pd] crashes Pd in this case).Any suggestions welcome. Is there something I totally missed
here????D.
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 48: "Discover your formulas and abandon them"
Pd-list@iem.at mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 158: "Think of the radio"
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Mistrust authority - promote decentralization. - the hacker ethic
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 67: "Emphasize the flaws"
kill your television
Where do I find the matching Pd Firmata objects for the Firmata in Arduino 18 then?
Maybe all of this could be a bit better documented? ;-)
D.
On 3/10/10 1:17 AM, Hans-Christoph Steiner wrote:
The vesrion of Firmata included in Arduino 0018 is the best one, but the one in Pduino-0.5beta6 zip should be fine too. OldStandardFirmata == StandardFirmataV2_0
Man, just change chip. Use the 168 or the 328. and stop complaining, or use google then. people told you what to do, now you should try it. this is open if you want to help document it, so please do.
2010/3/10 Derek Holzer derek@umatic.nl
Where do I find the matching Pd Firmata objects for the Firmata in Arduino 18 then?
Maybe all of this could be a bit better documented? ;-)
D.
On 3/10/10 1:17 AM, Hans-Christoph Steiner wrote:
The vesrion of Firmata included in Arduino 0018 is the best one, but the
one in Pduino-0.5beta6 zip should be fine too. OldStandardFirmata == StandardFirmataV2_0
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 96: "Is the intonation correct?"
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Yes and merry christmas to you to you too Ricardo. Google up Pure Data
FLOSS Manual if you would like to see how much I complain and how
little I document...
Kids these days..jeeeez......
D
Quoting Ricardo Lameiro ricardolameiro@gmail.com:
Man, just change chip. Use the 168 or the 328. and stop complaining, or use google then. people told you what to do, now you should try it. this is open if you want to help document it, so please do.
List goofballs aside, I think it would be good to clarify all this stuff.
The split between the things available on HCs site and what comes with
Arduino is quite confusing. I was only using the ones from HC to keep
the versions matching.
The Arduino-provided Firmata stuff does not contain the Pd objects
themselves, and if the Pd objects must match certain Firmata then it
would be good to make a note of that somewhere... maybe on the site
where the Pd stuff is downloaded?
And besides that, if some Firmata says it supports ATMEGA8 then I
believe what it says. I spent half of yesterday smashing my face
against the keyboards of 12 students, trying to teach them something
that was broken, and the reason it was broken was not documented. So
yes I get a bit cranky!
Peace out dudes, D.
2010/3/10 Derek Holzer derek@umatic.nl
Where do I find the matching Pd Firmata objects for the Firmata in Arduino 18 then?
Maybe all of this could be a bit better documented? ;-)
On Mar 10, 2010, at 9:59 AM, Derek Holzer wrote:
List goofballs aside, I think it would be good to clarify all this
stuff.The split between the things available on HCs site and what comes
with Arduino is quite confusing. I was only using the ones from HC
to keep the versions matching.
No argument here, its just a matter of finding the time to do it.
With Firmata 2.1 the baudrate should be totally stable (that's the big
change between 2.0 and 2.1), and further updates shouldn't cause
issues. I'm working on finalizing the Pduino 0.5 release.
The Arduino-provided Firmata stuff does not contain the Pd objects
themselves, and if the Pd objects must match certain Firmata then it
would be good to make a note of that somewhere... maybe on the site
where the Pd stuff is downloaded?
For the latest Pduino, either use the included one, or the one in
Arduino 0018.
And besides that, if some Firmata says it supports ATMEGA8 then I
believe what it says. I spent half of yesterday smashing my face
against the keyboards of 12 students, trying to teach them something
that was broken, and the reason it was broken was not documented. So
yes I get a bit cranky!
Firmata is an Arduino library which fully supports the ATMEGA8.
StandardFirmata is a firmware that uses the Firmata library that is
too big for the ATMEGA8. As a teacher, I would highly recommend
avoiding the ATMEGA8, they are not well supported by the Arduino
community.
.hc
Peace out dudes, D.
2010/3/10 Derek Holzer derek@umatic.nl
Where do I find the matching Pd Firmata objects for the Firmata in
Arduino 18 then?Maybe all of this could be a bit better documented? ;-)
If you are not part of the solution, you are part of the problem.
Hi HC,
thanks for clarification. I will try to find some time to stick it in
the FLOSS Manual Pduino chapters later on. I did get the ATMEGA8s
running with the new baudrate, now I have a problem with the ATMEG328
but I will deal with that tomorrow.
I tried to get all 12 students using same versions of everything but
you know how hard that can be. What was supposed to be a 10 minute
installation took the entire afternoon, along with questions about
motors, circuits, mechanics and everything else in the middle of
debugging. Not an optimal moment for concentration to fix a glitch...
maybe I will stick to hardware-only workshops from now on, computers
are only good for causing ulcers and hairloss!
I landed here Sunday and started the workshop the next morning so I
had no time to investigate what hardware the school had. I told them
they should upgrade the ATMEGAs they have but you know how long that
takes at any kind of institution ;-)
Best from Helsinki! D.
Quoting Hans-Christoph Steiner hans@at.or.at:
On Mar 10, 2010, at 9:59 AM, Derek Holzer wrote:
List goofballs aside, I think it would be good to clarify all this stuff.
The split between the things available on HCs site and what comes
with Arduino is quite confusing. I was only using the ones from HC
to keep the versions matching.No argument here, its just a matter of finding the time to do it. With Firmata 2.1 the baudrate should be totally stable (that's the big change between 2.0 and 2.1), and further updates shouldn't cause issues. I'm working on finalizing the Pduino 0.5 release.
The Arduino-provided Firmata stuff does not contain the Pd objects
themselves, and if the Pd objects must match certain Firmata then
it would be good to make a note of that somewhere... maybe on the
site where the Pd stuff is downloaded?For the latest Pduino, either use the included one, or the one in Arduino 0018.
And besides that, if some Firmata says it supports ATMEGA8 then I
believe what it says. I spent half of yesterday smashing my face
against the keyboards of 12 students, trying to teach them
something that was broken, and the reason it was broken was not
documented. So yes I get a bit cranky!Firmata is an Arduino library which fully supports the ATMEGA8. StandardFirmata is a firmware that uses the Firmata library that is too big for the ATMEGA8. As a teacher, I would highly recommend avoiding the ATMEGA8, they are not well supported by the Arduino community.
.hc
Peace out dudes, D.
2010/3/10 Derek Holzer derek@umatic.nl
Where do I find the matching Pd Firmata objects for the Firmata in Arduino 18 then?
Maybe all of this could be a bit better documented? ;-)
If you are not part of the solution, you are part of the problem.
Keep in mind this is beta software so you were just a beta tester. It
would be great to incorporate your experience into the next release.
Perhaps the best way to support the ATMEGA8 is to post a firmware for
it somewhere, like StandardFirmataATMEGA8. It would just be
OldStandardFirmata/StandardFirmataV2_0 renamed to
StandardFirmataATMEGA8 and with the baud rate of 57600.
What is only a question of the ATMEGA8? Or where there other problems?
.hc
On Mar 10, 2010, at 11:48 AM, Derek Holzer wrote:
Hi HC,
thanks for clarification. I will try to find some time to stick it
in the FLOSS Manual Pduino chapters later on. I did get the ATMEGA8s
running with the new baudrate, now I have a problem with the
ATMEG328 but I will deal with that tomorrow.I tried to get all 12 students using same versions of everything but
you know how hard that can be. What was supposed to be a 10 minute
installation took the entire afternoon, along with questions about
motors, circuits, mechanics and everything else in the middle of
debugging. Not an optimal moment for concentration to fix a
glitch... maybe I will stick to hardware-only workshops from now on,
computers are only good for causing ulcers and hairloss!I landed here Sunday and started the workshop the next morning so I
had no time to investigate what hardware the school had. I told them
they should upgrade the ATMEGAs they have but you know how long that
takes at any kind of institution ;-)Best from Helsinki! D.
Quoting Hans-Christoph Steiner hans@at.or.at:
On Mar 10, 2010, at 9:59 AM, Derek Holzer wrote:
List goofballs aside, I think it would be good to clarify all this
stuff.The split between the things available on HCs site and what comes
with Arduino is quite confusing. I was only using the ones from
HC to keep the versions matching.No argument here, its just a matter of finding the time to do it.
With Firmata 2.1 the baudrate should be totally stable (that's the big change between 2.0 and 2.1), and further updates shouldn't cause issues. I'm working on finalizing the Pduino 0.5 release.The Arduino-provided Firmata stuff does not contain the Pd
objects themselves, and if the Pd objects must match certain
Firmata then it would be good to make a note of that somewhere...
maybe on the site where the Pd stuff is downloaded?For the latest Pduino, either use the included one, or the one in Arduino 0018.
And besides that, if some Firmata says it supports ATMEGA8 then I
believe what it says. I spent half of yesterday smashing my face
against the keyboards of 12 students, trying to teach them
something that was broken, and the reason it was broken was not
documented. So yes I get a bit cranky!Firmata is an Arduino library which fully supports the ATMEGA8. StandardFirmata is a firmware that uses the Firmata library that is
too big for the ATMEGA8. As a teacher, I would highly recommend avoiding the ATMEGA8, they are not well supported by the Arduino community..hc
Peace out dudes, D.
2010/3/10 Derek Holzer derek@umatic.nl
Where do I find the matching Pd Firmata objects for the Firmata
in Arduino 18 then?Maybe all of this could be a bit better documented? ;-)
If you are not part of the solution, you are part of the problem.
¡El pueblo unido jamás será vencido!
Once I fixed the baudrate (thx!!!) it works fine. One student has trouble with an ATMEGA328 that I will have to troubleshoot tomorrow.
Good idea to make a specific release, or at least label it in some way that makes it clear. I know it's ugly to support very old hardware, but I think there are a lot of those things out there in the world still.
Best, D.
On 3/10/10 7:03 PM, Hans-Christoph Steiner wrote:
Keep in mind this is beta software so you were just a beta tester. It would be great to incorporate your experience into the next release.
Perhaps the best way to support the ATMEGA8 is to post a firmware for it somewhere, like StandardFirmataATMEGA8. It would just be OldStandardFirmata/StandardFirmataV2_0 renamed to StandardFirmataATMEGA8 and with the baud rate of 57600.
What is only a question of the ATMEGA8? Or where there other problems?
.hc
On Mar 10, 2010, at 11:48 AM, Derek Holzer wrote:
Hi HC,
thanks for clarification. I will try to find some time to stick it in the FLOSS Manual Pduino chapters later on. I did get the ATMEGA8s running with the new baudrate, now I have a problem with the ATMEG328 but I will deal with that tomorrow.
I tried to get all 12 students using same versions of everything but you know how hard that can be. What was supposed to be a 10 minute installation took the entire afternoon, along with questions about motors, circuits, mechanics and everything else in the middle of debugging. Not an optimal moment for concentration to fix a glitch... maybe I will stick to hardware-only workshops from now on, computers are only good for causing ulcers and hairloss!
I landed here Sunday and started the workshop the next morning so I had no time to investigate what hardware the school had. I told them they should upgrade the ATMEGAs they have but you know how long that takes at any kind of institution ;-)
Best from Helsinki! D.
Quoting Hans-Christoph Steiner hans@at.or.at:
On Mar 10, 2010, at 9:59 AM, Derek Holzer wrote:
List goofballs aside, I think it would be good to clarify all this stuff.
The split between the things available on HCs site and what comes with Arduino is quite confusing. I was only using the ones from HC to keep the versions matching.
No argument here, its just a matter of finding the time to do it. With Firmata 2.1 the baudrate should be totally stable (that's the big change between 2.0 and 2.1), and further updates shouldn't cause issues. I'm working on finalizing the Pduino 0.5 release.
The Arduino-provided Firmata stuff does not contain the Pd objects themselves, and if the Pd objects must match certain Firmata then it would be good to make a note of that somewhere... maybe on the site where the Pd stuff is downloaded?
For the latest Pduino, either use the included one, or the one in Arduino 0018.
And besides that, if some Firmata says it supports ATMEGA8 then I believe what it says. I spent half of yesterday smashing my face against the keyboards of 12 students, trying to teach them something that was broken, and the reason it was broken was not documented. So yes I get a bit cranky!
Firmata is an Arduino library which fully supports the ATMEGA8. StandardFirmata is a firmware that uses the Firmata library that is too big for the ATMEGA8. As a teacher, I would highly recommend avoiding the ATMEGA8, they are not well supported by the Arduino community.
.hc
Peace out dudes, D.
2010/3/10 Derek Holzer derek@umatic.nl
Where do I find the matching Pd Firmata objects for the Firmata in Arduino 18 then?
Maybe all of this could be a bit better documented? ;-)
If you are not part of the solution, you are part of the problem.
¡El pueblo unido jamás será vencido!
I don't have any ATMEGA8 boards anymore, so I am not in a position to
maintain that stuff. Perhaps you could just bundle up the version you
got working, call it StandardFirmataAtmega8 and post it somewhere?
.hc
On Mar 10, 2010, at 3:58 PM, Derek Holzer wrote:
Once I fixed the baudrate (thx!!!) it works fine. One student has
trouble with an ATMEGA328 that I will have to troubleshoot tomorrow.Good idea to make a specific release, or at least label it in some
way that makes it clear. I know it's ugly to support very old
hardware, but I think there are a lot of those things out there in
the world still.Best, D.
On 3/10/10 7:03 PM, Hans-Christoph Steiner wrote:
Keep in mind this is beta software so you were just a beta tester. It would be great to incorporate your experience into the next release.
Perhaps the best way to support the ATMEGA8 is to post a firmware
for it somewhere, like StandardFirmataATMEGA8. It would just be OldStandardFirmata/StandardFirmataV2_0 renamed to
StandardFirmataATMEGA8 and with the baud rate of 57600.What is only a question of the ATMEGA8? Or where there other
problems?.hc
On Mar 10, 2010, at 11:48 AM, Derek Holzer wrote:
Hi HC,
thanks for clarification. I will try to find some time to stick it
in the FLOSS Manual Pduino chapters later on. I did get the ATMEGA8s running with the new baudrate, now I have a problem with the
ATMEG328 but I will deal with that tomorrow.I tried to get all 12 students using same versions of everything but you know how hard that can be. What was supposed to be a 10 minute installation took the entire afternoon, along with questions about motors, circuits, mechanics and everything else in the middle of debugging. Not an optimal moment for concentration to fix a
glitch... maybe I will stick to hardware-only workshops from now on, computers are only good for causing ulcers and hairloss!I landed here Sunday and started the workshop the next morning so I had no time to investigate what hardware the school had. I told them they should upgrade the ATMEGAs they have but you know how long that takes at any kind of institution ;-)
Best from Helsinki! D.
Quoting Hans-Christoph Steiner hans@at.or.at:
On Mar 10, 2010, at 9:59 AM, Derek Holzer wrote:
List goofballs aside, I think it would be good to clarify all this stuff.
The split between the things available on HCs site and what comes with Arduino is quite confusing. I was only using the ones from HC to keep the versions matching.
No argument here, its just a matter of finding the time to do it.
With Firmata 2.1 the baudrate should be totally stable (that's the big change between 2.0 and 2.1), and further updates shouldn't cause issues. I'm working on finalizing the Pduino 0.5 release.The Arduino-provided Firmata stuff does not contain the Pd objects themselves, and if the Pd objects must match certain Firmata
then it would be good to make a note of that somewhere... maybe on the
site where the Pd stuff is downloaded?For the latest Pduino, either use the included one, or the one in Arduino 0018.
And besides that, if some Firmata says it supports ATMEGA8 then I believe what it says. I spent half of yesterday smashing my face against the keyboards of 12 students, trying to teach them
something that was broken, and the reason it was broken was not
documented. So yes I get a bit cranky!Firmata is an Arduino library which fully supports the ATMEGA8. StandardFirmata is a firmware that uses the Firmata library that
is too big for the ATMEGA8. As a teacher, I would highly recommend
avoiding the ATMEGA8, they are not well supported by the Arduino community..hc
Peace out dudes, D.
2010/3/10 Derek Holzer derek@umatic.nl
> Where do I find the matching Pd Firmata objects for the
> Firmata in > Arduino > 18 then? > > Maybe all of this could be a bit better documented? ;-)
If you are not part of the solution, you are part of the problem.
¡El pueblo unido jamás será vencido!
-- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 68: "Faced with a choice, do both"
"Making boring techno music is really easy with modern tools, but with
live coding, boring techno is much harder." - Chris McCormick
-
Derek Holzer -
Hans-Christoph Steiner -
Ricardo Lameiro