Propscope slowly dying ?
0xff
Posts: 3
Hi,
Propscope has been running fine for a few months from now.
A few days ago, I began to receive some timeout during software connection to the device, then when switch volt/div got response from it.
Now the scope is not recognized at all by the software - BTW the device stills mount as a COM port at OS level.
The 'Load and Connect' producse the following output :
--
58:57 starting thread
58:57 Opened port to COM2
58:60 Load an image
58:60 toggling dtr
58:71 discarded, writing reset
--
Are there anymore investigations that can be done before being SOL ?
I've tried other options, as pluging-in the scope in a VM, to another physical machine, updated to the soft to v.2.0.7 with no luck as you might have guessed
Thanks for any advice !
Propscope has been running fine for a few months from now.
A few days ago, I began to receive some timeout during software connection to the device, then when switch volt/div got response from it.
Now the scope is not recognized at all by the software - BTW the device stills mount as a COM port at OS level.
The 'Load and Connect' producse the following output :
--
58:57 starting thread
58:57 Opened port to COM2
58:60 Load an image
58:60 toggling dtr
58:71 discarded, writing reset
--
Are there anymore investigations that can be done before being SOL ?
I've tried other options, as pluging-in the scope in a VM, to another physical machine, updated to the soft to v.2.0.7 with no luck as you might have guessed
Thanks for any advice !
Comments
I'm looking into a bootloader issue, IMHO that would explain what's going on.
@staff members : any advice to diagnose further ?
Hi,
Make sure you're using a standard USB cable, not a Parallax retractable usb cable.
There was a hardware change a while back that resolved an issue with the PropScope not getting enough power which resulted in the scope not working after several minutes. Test the PropScope on a different pc to make sure your pc hardware/software is not the cause.
Hanno
I've tried :
- 3 different cables (the original one I was using + 3 others).
- Disabling other COM Ports (as read in another thread)
- Another PC (a laptop this time)
but no go.
Just for the sake of it, I've tried to identify the chip by installing/using Propeller Tool - the chip is not identified - as stated earlier the device mount at OS level - the FTDI chip is recognized, the Propscope COM is present when the device is attached.
Hanno