Pduino problem

Reply to Pduino problem on Sun, 06 Oct 2019 17:58:10 GMT

Al33000 — Sun, 06 Oct 2019 17:58:10 GMT

Hello everyone, ive got this problem while trying to connect my arduino to Pd. Already installed firmata, used firmata test app to check its ok, and it is. But when i open the arduino-test pd patch, i get this:

netreceive: failed to sett SO_BROADCAST
comport - PD external for unix/windows
LGPL 1998-2015, Winfried Ritsch and others (see LICENSE.txt)
Institute for Electronic Music - Graz
[comport] Opening COM1
[comport]: could not open device COM1:
failure(2) ERROR_FILE_NOT_FOUND

[comport] opening serial port 1 failed!
moocow/string2any 32 -1
... couldn't create
route 13 0 20 1 (message->prepend) connection failed
route 14 0 20 1 (message->prepend) connection failed
route 16 0 20 1 (bang->prepend) connection failed
route 17 0 20 1 (bang->prepend) connection failed
moocow/string2any 32 -1
... couldn't create
moocow/any2string
... couldn't create
moocow/any2string
... couldn't create
moocow/string2any 32 -1
... couldn't create
[arduino]: version_0.5
[comport]: could not open device COM1:
failure(2) ERROR_FILE_NOT_FOUND

Firmware: 2-5.
UNKNOWN_INPUT_COMMAND: 0 480
UNKNOWN_INPUT_COMMAND: 0 479
UNKNOWN_INPUT_COMMAND: 0 479
UNKNOWN_INPUT_COMMAND: 0 480
UNKNOWN_INPUT_COMMAND: 0 479
UNKNOWN_INPUT_COMMAND: 0 480
UNKNOWN_INPUT_COMMAND: 0 479
UNKNOWN_INPUT_COMMAND: 0 479
UNKNOWN_INPUT_COMMAND: 0 479
UNKNOWN_INPUT_COMMAND: 0 480
UNKNOWN_INPUT_COMMAND: 0 479
UNKNOWN_INPUT_COMMAND: 0 480

So, i select the port im using and the A0 pin which is the one with the potentiometer im gonna use, and i get thousands of UNKNOWN_INPUT_COMMAND messages, i turn the pot and the values go from 0 to 1000, and the pd device info block has Firmata 2.5 so its recognizing the device, but cant go beyond that. Any ideas? I see that moocow is missing (and that could be relevant), but couldnt get anything using the "find externals" function.

Reply to Pduino problem on Sun, 06 Oct 2019 19:00:42 GMT

whale-av — Sun, 06 Oct 2019 19:00:42 GMT

@Al33000 For comport..... the port might not be COM1, and maybe if COM1 is reserved you need COM2 etc.
If the Moocow objects are not available they can probably be replaced if you are using Pd Vanilla.
For example [string2any] was a wrapper for [bytes2any] and can be replaced by [list tosymbol]
And similarly [any2string] can be replaced by [list fromsymbol]

Upload the patch if you need more help.
Those Vanilla objects will not split the message though, so if that was the intention with the arguments 32 -1 (which I don't think is the case) then a little more work will be necessary.
David.

Reply to Pduino problem on Sun, 06 Oct 2019 19:13:45 GMT

Al33000 — Sun, 06 Oct 2019 19:13:45 GMT

arduino-test.pd
Thanks for answering! This is driving me mad lol.. Heres the patch attached, its the arduino test utility for Pduino.

comport is fine, the messages you see there are when you havent set the correct port yet, you select the correct one (in this case port 7) and it doesnt bugger anymore.

Im using pd vanilla 0.49 on Windows, so i have to check any moocow references and change them for "list tosymbol" and "list fromsymbol"? ...ive read on forums moocow shows these warning messages but only when running on windows.

So, to recapitulate, firmata is properly installed on the arduino, and its actually giving out correct output data, but cant get them to be recognized by Pd, hence the unknown input command messages, pretty sure the moocow issue is the culprit but still cant get my head around it.

Reply to Pduino problem on Sun, 06 Oct 2019 20:39:35 GMT

whale-av — Sun, 06 Oct 2019 20:39:35 GMT

@Al33000 "netreceive: failed to sett SO_BROADCAST" is very strange...... unless the port is already in use..... not released when the patch was last closed.... or in use by another program.
I have just put a direct replacement into the zip file for the two missing objects (I have not changed the patch).
I have other stuff missing from vanilla, but I assume you have them...... [cyclone/gate] and stuff from the mapping/ library.
I cannot test.... no [arduino] object and worse still no Arduino.
Try running this one....... test.zip
You might be lucky....
David.
PS What is your OS that you are running Pd on?

Reply to Pduino problem on Sun, 06 Oct 2019 20:48:59 GMT

Al33000 — Sun, 06 Oct 2019 20:48:59 GMT

just tested what you uploaded, got this:

netreceive: failed to sett SO_BROADCAST
arduino 1
... couldn't create

and nothing else. i dont get unknown input command msgs anymore, even after setting the proper port and arduino analog pin. im on Win 7 Professional.

now, i moved the moocow folder you attached to my original pd patch folder and got this:

[comport] opening serial port 1 failed!
route 13 0 20 1 (message->prepend) connection failed
route 14 0 20 1 (message->prepend) connection failed
route 16 0 20 1 (bang->prepend) connection failed
route 17 0 20 1 (bang->prepend) connection failed
[arduino]: version_0.5
[comport]: could not open device COM1:
failure(2) ERROR_FILE_NOT_FOUND

Firmware: StandardFirmata.ino-2.5
UNKNOWN_INPUT_COMMAND: 0 240
UNKNOWN_INPUT_COMMAND: 0 239
UNKNOWN_INPUT_COMMAND: 0 239
UNKNOWN_INPUT_COMMAND: 0 239
UNKNOWN_INPUT_COMMAND: 0 239
UNKNOWN_INPUT_COMMAND: 0 239
UNKNOWN_INPUT_COMMAND: 0 239
UNKNOWN_INPUT_COMMAND: 0 239
UNKNOWN_INPUT_COMMAND: 0 239

no more moocow errors anymore, then i set the port, got the firmata 2.5 message, then set pin a0 and got the endless stream of unknown input command msgs that change value when i move the pot. i think we're pretty close, but still not there :/

Reply to Pduino problem on Sun, 06 Oct 2019 21:10:19 GMT

whale-av — Sun, 06 Oct 2019 21:10:19 GMT

@Al33000 You are lucky. Pd Extended, that will have exactly the correct objects for the patch, is available as a portable program (only for windows)...... http://puredata.info/downloads/pd-extended
You want this one.......
........Get Pd-extended for Windows (52.7MB)
........Windows ZIP (unzip and run anywhere)

You don't install it.... just unzip it (to your desktop?) keeping it all together in one folder, and then go to its Pd/bin folder and run pd.exe
Be sure to allow it through your firewall when the message pops up (Private network, not Public)

As it is portable it will not mess up your current Pd setup and you can just delete the folder later if you want.
I would keep it though. It can be useful in this sort of situation.
Then open your patch with that version.
If it still doesn't work then the problem is elsewhere.
In fact the "broadcast" message suggests that your current Pd is not allowed through the firewall... maybe....?
Clutching at straws otherwise as I cannot test the patch.
David.

Reply to Pduino problem on Sun, 06 Oct 2019 21:21:34 GMT

Al33000 — Sun, 06 Oct 2019 21:21:34 GMT

holy... that was it, that solved it

thanks a lot for your good will to help this blind man out of this trouble lol cheers!

Reply to Pduino problem on Sun, 06 Oct 2019 21:27:14 GMT

whale-av — Sun, 06 Oct 2019 21:27:14 GMT

@Al33000 You are very welcome.
Was it Pd extended that solved it or the firewall?
Asking so that others will know in the future.
David.

Reply to Pduino problem on Sun, 06 Oct 2019 21:53:34 GMT

Al33000 — Sun, 06 Oct 2019 21:53:34 GMT

It was Pd extended, it worked like a charm, now im on the project i was halted from yesterday when i got caught onto this, thank you again!