Propeller lost on Com port

Welly

hi,

I have been using my laptop and desktop with windows 10 and PropITool 1.32 for years successfully. Suddenly the laptop now loses the comport when 'long' spin programs are being downloaded. This happens with different prop plugs, different boards and cables connecting the laptop...same result. Every combination works fully on the desktop. I am using board 32810 but the result is same with other boards. All three usb laptop ports behave similarly ...mouse and other usb port functions seem normal. Could it be a power glitch on the 'longer' downloads ?

I have looked at past post on this subject

Any help ?
thanks

july 25,2019

Welly

RS_Jim

Does it happen if you try it without ac power to the laptop? If so do you have a powered USB hub Hub?
Jim

Welly

Same without ac power and same with powered USB Hub. Since it works with shorter programs, i believe that leaves the power to prop plug which is usb powered. If I cut the usb line and power prop plug separately ...worth a try ?

Welly

Wuerfel_21

have you tried messing with the advanced COM port settings in windows? (you can find them somewhere in the device properties dialog in device manager). Changing the buffer sizes in particular can sometimes fix wired COM port issues.

Welly

Yes I have changed the latency...but not the buffer size. I will try it
thanks

Welly

Buffer set to max 4096 ...no difference.

RS_Jim

Welly,
The reason I inquired about powered USB hub, is I have destroyed several Prop chips with ground loops caused by mixing a powered hub and a grounded laptop. I discarded one USB hub when I found 41Volts AC to ground no matter how the switching power supply was connected to the mains. That was very hard on PLL circuits in the Prop.
Jim

Welly

I don't use a hub with Prop ..I just tried it as you suggested

Welly

Jammer7071

I have the same problem..
never could figure it out either.
I did find that version 1.05.5 of the Propeller Tool works without that problem.

Cluso99

This problem has been reported numerous times in the past. I don’t think there was a solution for PropTool.
I suggest you try one of the other loaders such as bst.

Rayman

Try changing some "Advanced Settings" for the com port.
I remember this issue coming up before and some setting there fixes it...

Rayman

If that doesn't work, you could try SpinEdit…
Download the files in the first two posts here: http://forums.parallax.com/discussion/169259/spinedit-editor-for-spin-spin2-and-fastbasic/p1

put them in some folder and run SpinEdit. It uses a different loader.
But, you might try searching this forum for "FTDI Advanced Settings Windows" for what fixes it...

Rayman

This post: https://forums.parallax.com/discussion/110371/propplug-reset-on-usb-activity
Suggests turning off "Serial Enumerator" and turning on "Disable Modem Ctrl at Startup"

But, I don't think that is what you need.
I think it's the "Latency Timer"...

Rayman

Here's somebody that says a lower latency timer fixes this kind of issue:
https://forums.parallax.com/discussion/97251/hardware-communication-error-fixed

FYI: Window sometimes updates the FTDI driver without asking and things like this happen...