Hey all
I was about to create a Deken package of comport, but realized, there are some behaviors I don't understand.
I do have some patches that indicate the right outlet of comport did once output some sensible messages, like 'open 1' when the connection is established and 'open 0' when the connection is closed. The help- file lists a whole bunch of messages that would reflect inner state changes of the external. I am currently not able to trigger any of those documented messages.
May some of you can shed some light on this, I would really appreciate it:
* I only get '-1' from right outlet whenever I close a connection or open a different port. It's not documented. What does it mean?
* Even when I compile a version from 2006, I can't get the old behavior back and I still don't get any other message than '-1' on the right outlet. Why is that?
* What is 'verbose $1' about? What are valid verbose levels? I was able to make [comport] print some info with increased verbosity levels.
* Wouldn't it be good if there'd be some 'report' message that would trigger a dump of the current inner state, like 'xonxoff 0, stopbit 2, parity 0' etc.
BTW: I'm using those sources: https://git.iem.at/pd/comport.git (make sure to add --recursive when cloning)
Thanks, Roman
On Fri, Mar 3, 2017 at 4:55 AM, Roman Haefeli reduzent@gmail.com wrote:
- Wouldn't it be good if there'd be some 'report' message that would trigger a dump of the current inner state, like 'xonxoff 0, stopbit 2, parity 0' etc.
Have you tried the [info( message?
Martin
On Fre, 2017-03-03 at 08:35 -0500, Martin Peach wrote:
On Fri, Mar 3, 2017 at 4:55 AM, Roman Haefeli reduzent@gmail.com wrote:
* Wouldn't it be good if there'd be some 'report' message that would trigger a dump of the current inner state, like 'xonxoff 0, stopbit 2, parity 0' etc.
Have you tried the [info( message?
Thanks, I missed that one. That's exactly what I meant.
Now I realize that it is not necessary for 'open' to be reported automatically. One can send 'info' in zero logical time after 'open' and it instantaneously reports whether opening the device worked or not.
Everything alright then.. Time for a release.
Roman
hi roman and list,
i downloaded your comport v1.1 for osx and i have a strange problem…
whenever i try to create a comport object with some initial values the object box does not create and pd freezes (i have to force quit)
creating a [comport] works…also opening the help patch works.
i had comport v0.0. extended installed before if it matters, but it seems deken overwrites the files automagically if the folder name is the same…
cheers
simon
On 3 Mar 2017, at 16:08, Roman Haefeli reduzent@gmail.com wrote:
On Fre, 2017-03-03 at 08:35 -0500, Martin Peach wrote:
On Fri, Mar 3, 2017 at 4:55 AM, Roman Haefeli reduzent@gmail.com wrote:
- Wouldn't it be good if there'd be some 'report' message that
would trigger a dump of the current inner state, like 'xonxoff 0, stopbit 2, parity 0' etc.
Have you tried the [info( message?
Thanks, I missed that one. That's exactly what I meant.
Now I realize that it is not necessary for 'open' to be reported automatically. One can send 'info' in zero logical time after 'open' and it instantaneously reports whether opening the device worked or not.
Everything alright then.. Time for a release.
Roman_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Hey Simon
Thanks for your report. Frankly, I didn't test on OS X yet.
On Mon, 2017-03-06 at 15:54 +0100, Simon Iten wrote:
i downloaded your comport v1.1 for osx and i have a strange problem…
whenever i try to create a comport object with some initial values the object box does not create and pd freezes (i have to force quit)
What arguments did you give to [comport]?
creating a [comport] works…also opening the help patch works.
The help patch uses a [comport 1 9600]. Can you successfully create this? I'm wondering whether your problem is related to that fact that you specify arguments at all or rather if it has a problem with specifically those values you want to use. What device is it on the port you specify?
i had comport v0.0. extended installed before if it matters, but it seems deken overwrites the files automagically if the folder name is the same…
I _think_ downloading a package always overwrites any previously installed packages with the same name [1].
Does the same happen with the v0.0-extended version?
Roman
[1] Actually, Deken just extracts the archive over the existing folder, which means that any files in the destination folder not part of the archive will remain there. Don't get fooled by the file VERSION.txt which shows 1.1 after you installed comport v0.0-extended.
hey roman,
0.0extended works. i am creating this: [comport 1 19200] with an arduino connected.
but now i reinstalled 1.1 and it also works… very strange…
so, i guess sorry for the noise.
On 6 Mar 2017, at 16:23, Roman Haefeli reduzent@gmail.com wrote:
Hey Simon
Thanks for your report. Frankly, I didn't test on OS X yet.
On Mon, 2017-03-06 at 15:54 +0100, Simon Iten wrote:
i downloaded your comport v1.1 for osx and i have a strange problem…
whenever i try to create a comport object with some initial values the object box does not create and pd freezes (i have to force quit)
What arguments did you give to [comport]?
creating a [comport] works…also opening the help patch works.
The help patch uses a [comport 1 9600]. Can you successfully create this? I'm wondering whether your problem is related to that fact that you specify arguments at all or rather if it has a problem with specifically those values you want to use. What device is it on the port you specify?
i had comport v0.0. extended installed before if it matters, but it seems deken overwrites the files automagically if the folder name is the same…
I _think_ downloading a package always overwrites any previously installed packages with the same name [1].
Does the same happen with the v0.0-extended version?
Roman
[1] Actually, Deken just extracts the archive over the existing folder, which means that any files in the destination folder not part of the archive will remain there. Don't get fooled by the file VERSION.txt which shows 1.1 after you installed comport v0.0-extended.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On Mon, 2017-03-06 at 16:33 +0100, Simon Iten wrote:
hey roman,
0.0extended works. i am creating this: [comport 1 19200] with an arduino connected.
but now i reinstalled 1.1 and it also works… very strange…
In the meanwhile, I tested it, too, though only on macOS 10.10 virtual machine without access to any real serial devices. I wasn't able to reproduce the Pd crash. [comport] instantiates fine with whatever arguments I give it.
I'm glad it works for you too, now.
Roman
-
Martin Peach -
Roman Haefeli -
Simon Iten