Closed DrExpress1 closed 6 years ago
Got similar feedback from other users, for instance here from a training in Italy: On a few desktop there were recurrent problem of VPL hanging with a white screen after the compilation and test of a program. As soon as Thymio was detached from USB VPL was not able to reconnect. We had a procedure: a) stop Thymio b) reconnect the USB cable c)close and restart VPL and reconnect Thymio. Equipment used: Desktop with Windows XP, Aseba 1.4 nightly build of this weekend, Thymio some with firmware 8 and some 9.
Could it be defect cables, and weird reactions from the operating system?
No... we got new tymions and i tried it with a few thymions and it was always the same....
I just test now. It is a problem of windows 10. Disconnection is not detected.
@FrancescoMondada
This case seems to be different. It is reletad to issue #399
In Windows the disconnections is not detected until there is a data transfer. In VPL it is only the case when you click on play. At this moment you have the reconnection message. So in actual VPL and Windows system, when you disconnect, before reconnecting press the play button to make appear the reconnection message. Also if you have the reconnection window appear and you robot is already connect, disconnect and reconnect it should work.
The usbser driver was updated in win 10. This should explain why disconnection does not react as in previous versions. More info here: https://msdn.microsoft.com/en-us/library/windows/hardware/dn707976(v=vs.85).aspx
Great to hear others have experienced the same thing. We love these robots and our students love them. If we could fix this, rather than have to close program and reconnect We are using Aseba Studio, not VPL(for text-based coding). Any progress on this issue?
Sorry for bad news but no progress at this time. We need a Win 10 specialist to handle this. The only fix we have is to use Wireless Thymio so that you do not need reconnection or that you close save and clse the program before ( I know not user friendly at all) But we see the needs and will try to find a solution. Open to suggestions.
hey....thanks for response. So we have 30 units, but do not think they are wifi version is there a way to make these units work with dongle?
On Thu, Oct 20, 2016 at 4:24 PM, Michael Bonani notifications@github.com wrote:
Sorry for bad news but no progress at this time. We need a Win 10 specialist to handle this. The only fix we have is to use Wireless Thymio so that you do not need reconnection or that you close save and clse the program before ( I know not user friendly at all) But we see the needs and will try to find a solution. Open to suggestions.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/aseba-community/aseba/issues/435#issuecomment-255217827, or mute the thread https://github.com/notifications/unsubscribe-auth/AGM9WtNYAdyiKl18jP5ak1WpqtlhxU0dks5q184RgaJpZM4GTAHv .
thanks!
-Doug
Hi, Normally all Thymio could be update to Wireless version. You can bought an upgrade kit like this one: http://www.mobsya.org/en/kit-wireless-diy.html Regards
Hi there,
So it has been three months and there has been no developments with a solution. This is making it really difficult to use the robots as it is a nightmare for kids to disconnect, connect, ect. Is there any movement on a solution or 'hack' solution.
Cheers
I have opened an issue on Dashel regarding this problem. As a summary, the problem is that the built-in Windows 10 rfcomm
driver does not generate write (or read) errors on the associated stream when the physical USB-serial device is disconnected. This is a serious flaw in the driver.
Doesn't seem to be limited to the serial port. Try with asebaswitch between Aseba Studio and the Thymio as follows:
cmd.exe
C:\Program Files (x86)\AsebaStudio
)asebaswitch.exe "ser:device=COM6"
(you can check which COM port to use with Aseba Studio first)On Linux, restarting asebaswitch causes Aseba Studio to reconnect.
I tested that with Windows 10. Does it work on Win7?
If this test case is confirmed, that would mean that the whole disconnection notification (including for TCP) for the native API is broken in Windows 10.
@swithers19 we are working on a work around for the serial port. The problem is that the operating system does not report disconnection when they happen as it should. It is a bug in the operating system.
I stress test reconnection with the "reconnect" example of dashel. It works fine, there is I think now a problem in studio.
Ok, then it might be a threading issue. Let's talk live about this then.
this fix now
I have done a Programm with the thymion. I compiled it with an USB-cable. But if I put off the cable from thymion and put it again in, the program doesnt find thymion anymore. But i hear the usb-connecting/disconnecting-sound from Windows everytime. i am using win 10 and asiba 1.4.