i sent this yesterday but i dont think it went, apologies if it did. anyway
Hi, Im a bit stuck here On windows PD extended latest test release. If i create [comport 2 9600] it gives the error
[comport] ** ERROR ** could not reset params to DCB of port 3
[comport] invalid handle for COM
strangely hans's pduino patch opens fine and pulls in data.
Has comport changed in the way its created or am i over looking something? Thanks Nick
Nicholas Ward wrote:
i sent this yesterday but i dont think it went, apologies if it did. anyway
Hi, Im a bit stuck here On windows PD extended latest test release. If i create [comport 2 9600] it gives the error
[comport] ** ERROR ** could not reset params to DCB of port 3
This message is emitted when comport tries to close a port and restore its previous values. Is this the actual text? Why is it printing "port 3" and not "COM3"?
[comport] invalid handle for COM
Probably the previous port doesn't exist. I wonder why it tries to close it.
strangely hans's pduino patch opens fine and pulls in data.
It has no effect on the new port, it was only trying to restore the old one to its original state.
Has comport changed in the way its created or am i over looking something?
I recently updated comport in cvs. I don't know if that's the version you're using. The new version has four outlets (for data, port number, DSR state and CTS state).
Martin
Thanks Nick
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Jul 6, 2006, at 12:46 PM, Martin Peach wrote:
Nicholas Ward wrote:
i sent this yesterday but i dont think it went, apologies if it
did. anywayHi, Im a bit stuck here On windows PD extended latest test release. If i create [comport 2
9600] it gives the error[comport] ** ERROR ** could not reset params to DCB of port 3
This message is emitted when comport tries to close a port and
restore its previous values. Is this the actual text? Why is it
printing "port 3" and not "COM3"?[comport] invalid handle for COM
Probably the previous port doesn't exist. I wonder why it tries to
close it.strangely hans's pduino patch opens fine and pulls in data.
It has no effect on the new port, it was only trying to restore the
old one to its original state.Has comport changed in the way its created or am i over looking
something?I recently updated comport in cvs. I don't know if that's the
version you're using. The new version has four outlets (for data,
port number, DSR state and CTS state).
Its great that you added status outlets. How about having just one
status outlet? Then it would output like: [port 3(, [dsr 1(, [cts 0
(. You can then get the individual outlets easily by using a [route
port dsr cts].
Then it would also be very easy to add more status information
without breaking backwards compatibility. It would be nice to have
things like connection status [open 1(, [baud 9600(, [devicename /dev/
ttyS(, [parity 2(, [stopbit 1(, [bits 8(, etc.
I've done it this way with [hid] and [usbhid] and it works quite
well. It would be nice to have [comport] have a similar interface.
.hc
Martin
Thanks Nick
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
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity." -John Gilmore
Hans-Christoph Steiner wrote:
On Jul 6, 2006, at 12:46 PM, Martin Peach wrote:
Nicholas Ward wrote:
i sent this yesterday but i dont think it went, apologies if it did. anyway
Hi, Im a bit stuck here On windows PD extended latest test release. If i create [comport 2 9600] it gives the error
[comport] ** ERROR ** could not reset params to DCB of port 3
This message is emitted when comport tries to close a port and restore its previous values. Is this the actual text? Why is it printing "port 3" and not "COM3"?
[comport] invalid handle for COM
Probably the previous port doesn't exist. I wonder why it tries to close it.
strangely hans's pduino patch opens fine and pulls in data.
It has no effect on the new port, it was only trying to restore the old one to its original state.
Has comport changed in the way its created or am i over looking something?
I recently updated comport in cvs. I don't know if that's the version you're using. The new version has four outlets (for data, port number, DSR state and CTS state).
Its great that you added status outlets. How about having just one status outlet? Then it would output like: [port 3(, [dsr 1(, [cts 0(. You can then get the individual outlets easily by using a [route port dsr cts].
Then it would also be very easy to add more status information without breaking backwards compatibility. It would be nice to have things like connection status [open 1(, [baud 9600(, [devicename /dev/ttyS(, [parity 2(, [stopbit 1(, [bits 8(, etc.
I've done it this way with [hid] and [usbhid] and it works quite well. It would be nice to have [comport] have a similar interface.
OK, Hans-Christoph , I've modified comport the way you suggested (except for devicename, which will be added soon, but not before a couple of weeks). It's in CVS. Please let me know if it works or not... Also I'm nearly done on a band-limited pwm object. Any suggestions as to which directory it should go in?
Martin
Hi Nicholas,
Nicholas Ward wrote:
i sent this yesterday but i dont think it went, apologies if it did. anyway
Hi, Im a bit stuck here On windows PD extended latest test release. If i create [comport 2 9600] it gives the error
[comport] ** ERROR ** could not reset params to DCB of port 3
[comport] invalid handle for COM
[comport 0 9600] and [comport 1 9600] work fine for me. Are you sure you want to connect to COM3? [comport 2] is COM3!!!
And yes, comport changed recently. BTW, there's a bug mentioned by HCS about crashing pd on extensive transmitions via comport. If you find any other problems, send it to this list, please.
br, Piotr
Thats a copy and paste of the error. yep COM3 is what i want hence the comport 2. Im not near a windows machine now but Ill put a bit more time into this next week. Thanks for the info. N
On 7 Jul 2006, at 08:50, Piotr Majdak wrote:
Hi Nicholas,
Nicholas Ward wrote:
i sent this yesterday but i dont think it went, apologies if it did. anyway Hi, Im a bit stuck here On windows PD extended latest test release. If i create [comport 2 9600] it gives the error [comport] ** ERROR ** could not reset params to DCB of port 3 [comport] invalid handle for COM
[comport 0 9600] and [comport 1 9600] work fine for me. Are you sure you want to connect to COM3? [comport 2] is COM3!!!
And yes, comport changed recently. BTW, there's a bug mentioned by HCS about crashing pd on extensive transmitions via comport. If you find any other problems, send it to this list, please.
br, Piotr
-- Piotr Majdak Institut für Schallforschung Österreichische Akademie der Wissenschaften Reichsratsstr. 17 A-1010 Wien Tel.: +43-1-4277-29511 Fax: +43-1-4277-9296 E-Mail: piotr@majdak.com WWW: http://www.kfs.oeaw.ac.at
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
This actually changed. I redid the port numbering on all three
platforms for a couple reasons. On Windows, port 3 now equals COM3.
port 0 should be mapped to COM1 for compatibility, but I think forgot
to do that.
.hc
On Jul 7, 2006, at 7:38 AM, Nicholas Ward wrote:
Thats a copy and paste of the error. yep COM3 is what i want hence
the comport 2. Im not near a windows machine now but Ill put a bit
more time into this next week. Thanks for the info. NOn 7 Jul 2006, at 08:50, Piotr Majdak wrote:
Hi Nicholas,
Nicholas Ward wrote:
i sent this yesterday but i dont think it went, apologies if it
did. anyway Hi, Im a bit stuck here On windows PD extended latest test release. If i create [comport
2 9600] it gives the error [comport] ** ERROR ** could not reset params to DCB of port 3 [comport] invalid handle for COM[comport 0 9600] and [comport 1 9600] work fine for me. Are you
sure you want to connect to COM3? [comport 2] is COM3!!!And yes, comport changed recently. BTW, there's a bug mentioned by
HCS about crashing pd on extensive transmitions via comport. If
you find any other problems, send it to this list, please.br, Piotr
-- Piotr Majdak Institut für Schallforschung Österreichische Akademie der Wissenschaften Reichsratsstr. 17 A-1010 Wien Tel.: +43-1-4277-29511 Fax: +43-1-4277-9296 E-Mail: piotr@majdak.com WWW: http://www.kfs.oeaw.ac.at
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
As we enjoy great advantages from inventions of others, we should be
glad of an opportunity to serve others by any invention of ours; and
this we should do freely and generously. - Benjamin Franklin
-
Hans-Christoph Steiner -
Martin Peach -
Nicholas Ward -
Piotr Majdak