dear list,
i'm repeating my question because i'm totally stuck.
[comport] reports RXerrors when trying to connect to an Arduino over
an USB com port.
the Arduino IDE works without fail.
it's on a new Lenovo with Windows 10.
i cannot fall back on my old W7 computer because it crashed.
needless to say that everything worked on W7, XP, MAC.
anybody who has experience with this?
any hint is very much appreciated.
rolf
What errors do you get? Do you get data OK/wrong/some/none? What baud rate are you using?
Martin
On Tue, Sep 15, 2015 at 10:56 AM, rolfm@dds.nl wrote:
dear list,
i'm repeating my question because i'm totally stuck.
[comport] reports RXerrors when trying to connect to an Arduino over an USB com port.
the Arduino IDE works without fail.
it's on a new Lenovo with Windows 10.
i cannot fall back on my old W7 computer because it crashed.
needless to say that everything worked on W7, XP, MAC.
anybody who has experience with this?
any hint is very much appreciated.
rolf
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Martin Peach chakekatzil@gmail.com schreef:
What errors do you get? Do you get data OK/wrong/some/none? What baud rate are you using?
RXERRORS on serial line (997)
after opening the port 10 of these messages appear. then after around 40 secs the message is given continouisly.
i tried 9600 and 115200 as baud rates: same result.
no data comes through.
this with a simple setup: Arduino sketch does every 3 secs a Serial.println, PD patch only with [comport] and [print].
rolf
On 2015-09-16 10:08, rolfm@dds.nl wrote:
RXERRORS on serial line (997)
997 is "ERROR_IO_PENDING", which - according to [1] - is not an error.
checking the sources of [comport] that ERROR_IO_PENDING is handled correctly for output (TX), but not for input (RX), cf comport.c:1085
gdfmart IOhannes
[1] https://msdn.microsoft.com/en-us/library/aa365747%28v=vs.85%29.aspx
On 2015-09-16 10:24, IOhannes m zmoelnig wrote:
On 2015-09-16 10:08, rolfm@dds.nl wrote:
RXERRORS on serial line (997)
997 is "ERROR_IO_PENDING", which - according to [1] - is not an error.
checking the sources of [comport] that ERROR_IO_PENDING is handled correctly for output (TX), but not for input (RX), cf comport.c:1085
though it seems that the "incorrect" handling in RX is mainly the printout of the error message. afaics, the data should arrive nonetheless.
hmm, dunno.
fgamsdr IOhannes
On Wed, Sep 16, 2015 at 4:08 AM, rolfm@dds.nl wrote:
Martin Peach chakekatzil@gmail.com schreef:
What errors do you get? Do you get data OK/wrong/some/none? What baud rate
are you using?
RXERRORS on serial line (997)
after opening the port 10 of these messages appear. then after around 40 secs the message is given continouisly.
i tried 9600 and 115200 as baud rates: same result.
no data comes through.
this with a simple setup: Arduino sketch does every 3 secs a Serial.println, PD patch only with [comport] and [print].
In your arduino code you will have a line Serial.begin(); with the baud rate inside the parentheses. It should be the same as what [comport] is using. Also Serial,println() sends ASCII and [comport] will output those ASCII codes, not the actual text. So if the baud rates are really the same at both ends and you still get no data, then [comport] is buggy on Win10, beyond printing the non-error message.
Martin
Martin Peach chakekatzil@gmail.com schreef:
On Wed, Sep 16, 2015 at 4:08 AM, rolfm@dds.nl wrote:
Martin Peach chakekatzil@gmail.com schreef:
What errors do you get? Do you get data OK/wrong/some/none? What baud rate
are you using?
RXERRORS on serial line (997)
after opening the port 10 of these messages appear. then after around 40 secs the message is given continouisly.
i tried 9600 and 115200 as baud rates: same result.
no data comes through.
this with a simple setup: Arduino sketch does every 3 secs a Serial.println, PD patch only with [comport] and [print].
In your arduino code you will have a line Serial.begin(); with the baud rate inside the parentheses. It should be the same as what [comport] is using. Also Serial,println() sends ASCII and [comport] will output those ASCII codes, not the actual text. So if the baud rates are really the same at both ends and you still get no data, then [comport] is buggy on Win10, beyond printing the non-error message.
Martin
i was afraid of that: [comport] buggy on W10. probably the only thing i can do now is filing a bug report.
and then trying to find a 'work-around' with a virtual machine.
thanks for the answer
rolf
On 2015-09-16 16:20, rolfm@dds.nl wrote:
i was afraid of that: [comport] buggy on W10. probably the only thing i can do now is filing a bug report.
and then trying to find a 'work-around' with a virtual machine.
for what it is worth: i just tested [comport] on a virtual W10 host (running on a Debian host), and i cannot find any problems so far.
note, that virtual serial-ports on the client are forwarded to network on the host, so no actual serial hardware is involved. it shouldn't make a difference for the client though.
so i'm not entirely sure that the problem is with [comport].
fgmasdr IOhannes
-
IOhannes m zmoelnig -
Martin Peach -
rolfm＠dds.nl