"Comms Lost"
John Board
Posts: 371
G'day,
I've been programming the prop recently with an older laptop - Windows XP SP2 (possibly SP3), and when I try to download larger file/project, it comes up with a message saying "Propeller Lost on COMXX" just after/while verifying the RAM, I'm pretty sure (98%) that I'm using v1.3. Any ideas/suggestions? It doesn't happen all the time - Just at all the arquard moments :P
Thanks again!
-John
I've been programming the prop recently with an older laptop - Windows XP SP2 (possibly SP3), and when I try to download larger file/project, it comes up with a message saying "Propeller Lost on COMXX" just after/while verifying the RAM, I'm pretty sure (98%) that I'm using v1.3. Any ideas/suggestions? It doesn't happen all the time - Just at all the arquard moments :P
Thanks again!
-John
Comments
-Phil
-John
Not quite sure what you mean, Control Panel as in the Windows CP? Or in Prop Tool? Also, where to go from Windows CP? I've gone to:
The Device Manager -> Ports (COM & LPT) -> COMXX -> Port Settings -> Advanced
Do I drag the two silders down to '1'? Or am I completely wrong?
-John
-Phil
Thanks again!
-John
Is this a quickstart board?
Thanks for the response turbosupra. No, it isn't a quickstart board, its one of the old "Gadget Gangster Propeller USB Platform Boards". GG no longer stocks them (same with Parallax), so I have supplied a link to mouser's website where they still have a page
http://au.mouser.com/gadgetgangsterpropeller/
Thanks for your hemp,
John
I've my PP-USB boards a lot and haven't seen this but then all the Windows I have now are Win7.
There are some cheap USB to serial plugs that do not work with the propeller. They work fine as a serial port once the propeller is programmed but not when programming.
I just tested both the latency and the delay as suggested in two posts above and neither work with these modules.
There was an old version of the proptool from 5 years ago that worked with many devices that now do not work. Without the source code it is hard to be certain, but the evidence suggests this is a software rather than a hardware problem.
If you can find a different ft232 driver that might help.
Another option that I tested just now was to use BST (Brad's Spin Tool). This does seem to cope better with different hardware. The catch with BST is there are not those little arrows in the spin program that form a rather essential part of the spin syntax.
No solution is perfect but one that does seem to work is to write software using the proptool but download it with BST.
One thing I noticed in the manual that is *very* interesting is using the spin language in a more "object oriented" way:
Who wrote it, I can't wait to try it? Any hiccups in switching to that from the prop tool?
It's written by Andre Demenev (probably spelt wrong).
Worked very well for me when I tried it out.
Note:
1) The Compile->Detect Propeller menu option (or F7) does not scan all ports for a Prop. You have to configure the port manually.
2) To specify the port go to Edit->Preferences-Compiler->options and there you will see port edit box, your port should appear in the drop down list.
3) To see indentation markers switch on Edit->Preferences->Editor ->Visible Tabs
Down side is that there is no nice terminal window like BST
Now if we could only get Andrey to use Parallax's new open source Spin compiler instead of BST we could use PZST on ARM boards as well.
From there you can get to Andrey's profile and sens a private forum message. No idea if he has an email address with PZST in the google code site.
I always wonder about scanning for devices. It carries the possibility of disturbing other serial connected devices.
Thanks, I will message him although he did say that this was intentional.
In the old days we had serial ports. It was clear what was attached to what port. It was static and that was that.
Now we have this stupid USB and "plug-n-play" where you can never tell what port your device ends up as.
Your solution is a fix to that problem that should not be in the first place.
Bah, I don't know.
Fantastic! That all works now. In that editor screen you can also have it as a white background, or the colors like in the proptool.
Two problems solved there - now can use cheapie USB to serial plugs, and also can start using objects they way they were meant to be used!
I'm a happy camper!
In HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\FTDIBUS\VID_13E2+PID_0080+A6007aHNA\0000\FriendlyName it has "PropScope (COM3)" stored as the value.
Is there a need for a usb management helper tool? With device name reader/display? You can change them to whatever you want, check it out