Skip Menu |

This queue is for tickets about the Win32-SerialPort CPAN distribution.

Report information
The Basics
Id: 67869
Status: open
Priority: 0/
Queue: Win32-SerialPort
People
Owner: Nobody in particular
Requestors: M.Walischewski [...] dataxcom.de
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sat Apr 30 19:55:26 2011 M.Walischewski [...] dataxcom.de - Ticket created
Subject: Maybe Fix the Bug / Problem
Date: Sun, 1 May 2011 01:55:13 +0200
To: <bug-Win32-SerialPort [...] rt.cpan.org>
From: "Michael Walischewski" <M.Walischewski [...] dataxcom.de>
Hello, there is still a problem with WIN32::SerialPort and the CP2102 USB Device with a Virtual Com Port. I logged 2 different Communications between CP2102 VUSB and a "normal" Com4. After this , I change the CommPort.pm With these lines at line 639 the Problem for me is solved and the Comport work fine. if(($CP_Length > 64) and ($CP_Length<67) and ($self->{"_TYPE"} == PST_RS232)){ $CP_Length = 64; $CP_Version = 2; $CP_ProvCapabilities = 0xff; $CP_SettableBaud = 0x1007ffff; } if (($CP_Length > 64) and ($self->{"_TYPE"} == PST_RS232)) { carp "invalid COMMPROP block length= $CP_Length"; undef $self; return; } please public these workaround or bugfix . King regards Michael Walischewski
  Sun May 01 18:32:10 2011 Bbirthisel [...] aol.com - Correspondence added
Subject: Re: [rt.cpan.org #67869] Maybe Fix the Bug / Problem
Date: Sun, 01 May 2011 18:31:49 -0400
To: bug-Win32-SerialPort [...] rt.cpan.org
From: Bill Birthisel <bbirthisel [...] aol.com>
Hi Michael, As I indicated before, I don't have one of those devices and have not been able to duplicate the problem. I will study your proposed solution. I'm very busy at the moment, so I won't promise an immediate response. I don't see an obvious problem - so if someone else has the problem I don't mind them trying your solution. It will probably become an "authorized patch" rather than a new release since most devices do not require it and it takes a while to test everything else for possible side effects when I can't replicate the issue. -bill On Sat, 2011-04-30 at 19:55 -0400, Michael Walischewski via RT wrote: Show quoted text
> Sat Apr 30 19:55:26 2011: Request 67869 was acted upon. > Transaction: Ticket created by M.Walischewski@dataxcom.de > Queue: Win32-SerialPort > Subject: Maybe Fix the Bug / Problem > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: M.Walischewski@dataxcom.de > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=67869 > > > > Hello, > there is still a problem with WIN32::SerialPort and the CP2102 USB Device > with a Virtual Com Port. > I logged 2 different Communications between CP2102 VUSB and a "normal" Com4. > After this , I change the CommPort.pm > With these lines at line 639 the Problem for me is solved and the Comport > work fine. > if(($CP_Length > 64) and ($CP_Length<67) and ($self->{"_TYPE"} == > PST_RS232)){ > $CP_Length = 64; > $CP_Version = 2; > $CP_ProvCapabilities = 0xff; > $CP_SettableBaud = 0x1007ffff; > } > if (($CP_Length > 64) and ($self->{"_TYPE"} == PST_RS232)) { > carp "invalid COMMPROP block length= $CP_Length"; > undef $self; > return; > } > please public these workaround or bugfix . > King regards > Michael Walischewski > >
  Sun May 01 18:32:11 2011 The RT System itself - Status changed from 'new' to 'open'