|
From: | anonymous |
Subject: | [Octave-bug-tracker] [bug #59581] (instrument-control) serialport error after second call |
Date: | Mon, 30 Nov 2020 19:54:39 -0500 (EST) |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36 |
URL: <https://savannah.gnu.org/bugs/?59581> Summary: (instrument-control) serialport error after second call Project: GNU Octave Submitted by: None Submitted on: Tue 01 Dec 2020 12:54:37 AM UTC Category: Octave Forge Package Severity: 3 - Normal Priority: 5 - Normal Item Group: Unexpected Error or Warning Status: None Assigned to: None Originator Name: Jens Bongartz Originator Email: bongartz@hs-koblenz.de Open/Closed: Open Release: 6.1.0 Discussion Lock: Any Operating System: Microsoft Windows _______________________________________________________ Details: Hello! I tested Octave 6.1.0 (Windows 8.1 and 10) with the instrument-control package (0.6.0) to receive data from a connected Arduino via serialport(). First initalization of serialport works as expected. After closing (clear) serialport a second call to serialport leads to one of the following errors: serialport: Error opening the interface: Illegal byte sequence serialport: Error opening the interface: No such file or directory It seems that the serial port of the computer remains blocked after closing because other application can also not access the serial port. Closing of Octave releases the serial port and access is regained. With Octave 5.2.0 and instrument-control (0.6.0) the problem does not occur. Best regards Jens Bongartz _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59581> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |