Re: [PD] Pduino 0.7 compatibility with Pd vanilla
I'm not sure if I'm totally up to date here but with a nano on Windos10 I also get no pin 7 reported. ARDUINO_INFO: version 2 5 ARDUINO_INFO: firmware StandardFirmata.ino 2 5 A pin like D2 willl report: comport receives from the arduino: 144 120 1 (b0000) (b0001) convert_to_symbolic_commands outputs: digital 2 0 ARDUINO_OUT: digital 2 0 comport receives from the arduino: 144 124 10 (b0100) (b0001) convert_to_symbolic_commands outputs: digital 2 1 ARDUINO_OUT: digital 2 1 But piin 7 is like this: comport receives from the arduino: 144 124 0 (b0100) (b) comport receives from the arduino: 144 124 1 (b0100) (b0001) This appears to be because the state of pin 7 is in the second data byte, which is ignored by the [pd convert_to_symbolic_commands ]. Bits 8 and up work because they are in the next port, so they appear as bits 0-7, so probably Pin 15 also doesn't work. The code in firmatamarshaller.cpp refers to two versions: FirmataStream->write(DIGITAL_MESSAGE | (portNumber & 0xF)); // Tx bits 0-6 (protocol v1 and higher) // Tx bits 7-13 (bit 7 only for protocol v2 and higher) encodeByteStream(sizeof(portData), reinterpret_cast(), sizeof(portData)); . ...so possibly pduino is not yet compatible with version2. Martin On Sat, Mar 20, 2021 at 6:15 PM Roman Haefeli wrote: > > On Sat, 2021-03-20 at 21:53 +0100, Roman Haefeli wrote: > > On Sat, 2021-03-20 at 19:24 +0100, Gilles Marivier wrote: > > > : > > > > https://github.com/pd-externals/pduino/issues > > > > > > Done ! > > > > > > I forgot a point : all others pins work fine on Nano > > > > Thanks, yeah, I saw it. However, I can't make any promises, though, > > since I don't own a Nano (in case that problem is specific to the > > Nano, > > which is not yet clear). > > Ok, this particular problem is fixed in current master. It turns out > the buggy code had 8 copies! So always the last pin in a group of 8 (7, > 15, 23, etc.) did not return anything. > > I believe this digital input mess could be done in a better, more > robust way with less code duplication. > > Also, with the Arduino Leonardo and Firmata 2.5, the higher numbered > pins (the "analog pins") do not report with pduino when set as digital > inputs. > > It looks like some refactoring of that old code is warranted. > > Roman > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] Pduino 0.7 compatibility with Pd vanilla
On Sat, 2021-03-20 at 21:53 +0100, Roman Haefeli wrote: > On Sat, 2021-03-20 at 19:24 +0100, Gilles Marivier wrote: > > : > > > https://github.com/pd-externals/pduino/issues > > > > Done ! > > > > I forgot a point : all others pins work fine on Nano > > Thanks, yeah, I saw it. However, I can't make any promises, though, > since I don't own a Nano (in case that problem is specific to the > Nano, > which is not yet clear). Ok, this particular problem is fixed in current master. It turns out the buggy code had 8 copies! So always the last pin in a group of 8 (7, 15, 23, etc.) did not return anything. I believe this digital input mess could be done in a better, more robust way with less code duplication. Also, with the Arduino Leonardo and Firmata 2.5, the higher numbered pins (the "analog pins") do not report with pduino when set as digital inputs. It looks like some refactoring of that old code is warranted. Roman signature.asc Description: This is a digitally signed message part ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] Pduino 0.7 compatibility with Pd vanilla
On Sat, 2021-03-20 at 19:24 +0100, Gilles Marivier wrote: > : > > > > https://github.com/pd-externals/pduino/issues > > Done ! > > I forgot a point : all others pins work fine on Nano Thanks, yeah, I saw it. However, I can't make any promises, though, since I don't own a Nano (in case that problem is specific to the Nano, which is not yet clear). Roman signature.asc Description: This is a digitally signed message part ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] Pduino 0.7 compatibility with Pd vanilla
Hi Le 18/03/2021 à 13:57, Roman Haefeli a écrit : Hi Gilles On Thu, 2021-03-18 at 12:57 +0100, Gilles Marivier wrote: Hi, I'm back on the project using Pduino. I tested the new release (thanks Roman). There's still the digital input #7 problem with the Nano (168 or 368). Problem description : although sending message "pinMode 7 input" to the [arduino] object, reading the #7 input state is impossible. There is no error message, just nothing happens. Thanks for the report. I'll have a look. Config : - OSX HighSierra 10.13.6 - Pduino 0.7 - Pd 0.51.1 - Arduino Nano Atmel 168 - firmware AllInputsFirmata.ino 2 5 Tested too with : - Arduino Nano Atmel 368 - firmware StandardFirmata.ino 2 5 Can you open an issue on so we don't forget and can track any ongoing development there: https://github.com/pd-externals/pduino/issues Done ! I forgot a point : all others pins work fine on Nano Works fine with Max/MSP's [arduino] object. That's good to know. Roman ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list -- www.marivier.rocks +33.(0)6.58.39.46.15 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] From telnet to netreceive whole sentence
Am 20. März 2021 13:25:38 MEZ schrieb "Csaba Láng" : > Dear list, > > I want to get a string of words with spaces to puredata and render > these > words to gemwin with text3d. > How can I send it from telnet and be sure all the words with spaces > will > arrive to netreceive? send unicodepoints rather than strings, and use the [string ... ( msg of [text3d]. if your string is ASCII only, you can just use the output of [netreceive -u -b]. to use UDP, you need something like netcat. with telnet you can only use TCP/IP, so you must accumulate the raw binary message depending on your made-up protocol (eg split lines on \n). there's also a utf-8 to unicodepoint abstraction in the Unicode library at https://git.iem.at/pd/unicode > Normally if I send via OSC I loose everything after the space. then you are probably doing something wrong (when crreaatinthe OSC message). mfg.hft.fsl IOhannes ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
[PD] From telnet to netreceive whole sentence
Dear list, I want to get a string of words with spaces to puredata and render these words to gemwin with text3d. How can I send it from telnet and be sure all the words with spaces will arrive to netreceive? Normally if I send via OSC I loose everything after the space. Any hints are welcome. Best, Popesz ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
