Peter, I get the following error message when i try to send terminaltest2.java with the beta IDE on my computer:
error ide -0052 Incompatible firmware revision $f
and when i try to send terminaltest2.java with the current release of Javelin Stamp IDE on my computer I get the same timeout error, and it never ends up sending the program to the Javelin.
Try to download that program from one of the other
pc's you mentioned (those that work). Then connect
the javelin again to your pc and see what the IDE beta
messagewindow does.
I got this by downloading terminaltest2 onto the Javelin on the old PC, then running the Javelin on my PC using the IDE beta.
I went project-identify, then project-test connection and the terminal window appears.
It only accepts one command ( i did help and flash), if i try to send another command nothing happens.
But if i close the terminal window and try again, it doesn't let me unless i go back to project-identify, then it will let me do project-test connection and the terminal window appears again and again lets me enter in one command.
Now we are getting somewhere. Apparently the javelin does receive,
but it receives the characters twice. It looks as if the javelin does not
recognize that the first character received is valid, then sends another request,
after which the IDE beta retransmits the last sent character.
I got a hunch that the troubles are much alike the troubles when connecting to
a Javelin on a Board of Education USB version.
A simple test could confim that. You said you have a Board of Education Serial. Connect a 1k resistor between SIN (pin2)·and GND (pin4) of the 24pin socket. You can make this connection easiest at the solder side of the BoE.
This 1k does no harm. I have soldered such a resistor on my Professional Development Board
because that board has both an usb and serial connector.
After placing the 1k, try IDE beta messagewindow again.
If I am right, the javelin should now receive the characters only once,
and the commands will be recognized.
I forgot to say that I have the old Basic Stamp BOE, not the Javelin BOE, so i didn't see a good way to hook up the resistor on it.· So to try the resistor, I switched the Javelin back over to the Stamp PLC.· Is there a way to add the resistor to my BOE?· Attached is a pic.
Also, I went into the 2.0.3 IDE and did debug-messages, and the terminaltest2 window came up, but it wouldn't accept any commands.
The easiest way to connect the resistor, is to solder it on the bottom side
between pin2 and pin4 of the 24pin socket. That's how I connected the
resistor on both a PDB and a BoE USB.
After connecting the resistor, try both version 2.0.3 and IDE beta again.
If still no success you should get yourself a usb2ser cable with FTDI chipset
like the ones Parallax sells. Those are guaranteed to work with the javelin
(I assume your pc does have an usb connector),·rather than spending much
more time on this. Apparently there is something with the serial port, perhaps
voltage levels that are not up to standard, that prevents reliable communication.
Or use one of the older pc's you have around·that did work.
Note that if you get a usb2ser cable, the resistor is not required because
both your boards have serial interfaces.
I had ordered the USB2SER from Parallax 2 days ago, and it just came in this morning.
Once I set the javeline IDE to recognize the new COM port that it created (COM3), I am now able to download programs onto the Javelin Stamp with my PC.
So it must be some problem with the onboard serial ports on these newer Dells:· Precision 390, Optiplex 320.
Thanks for all your help.· Now I can finally get to work.·
Hopefully the next person who has the same problem as I did can benefit from all our troubleshooting.
Comments
error ide -0052 Incompatible firmware revision $f
and when i try to send terminaltest2.java with the current release of Javelin Stamp IDE on my computer I get the same timeout error, and it never ends up sending the program to the Javelin.
pc's you mentioned (those that work). Then connect
the javelin again to your pc and see what the IDE beta
messagewindow does.
regards peter
·
Attached are the results.
I got this by downloading terminaltest2 onto the Javelin on the old PC, then running the Javelin on my PC using the IDE beta.
I went project-identify, then project-test connection and the terminal window appears.
It only accepts one command ( i did help and flash), if i try to send another command nothing happens.
But if i close the terminal window and try again, it doesn't let me unless i go back to project-identify, then it will let me do project-test connection and the terminal window appears again and again lets me enter in one command.
Thanks, Dan
but it receives the characters twice. It looks as if the javelin does not
recognize that the first character received is valid, then sends another request,
after which the IDE beta retransmits the last sent character.
I got a hunch that the troubles are much alike the troubles when connecting to
a Javelin on a Board of Education USB version.
A simple test could confim that. You said you have a Board of Education Serial.
Connect a 1k resistor between SIN (pin2)·and GND (pin4) of the 24pin socket.
You can make this connection easiest at the solder side of the BoE.
This 1k does no harm. I have soldered such a resistor on my Professional Development Board
because that board has both an usb and serial connector.
After placing the 1k, try IDE beta messagewindow again.
If I am right, the javelin should now receive the characters only once,
and the commands will be recognized.
Let me know the results.
regards peter
where it shows a duplicate of each letter
and i still cannot send a program to the javelin
try the version 2.0.3 IDE. Do Debug->Messages
and then reset the BoE using its reset button.
Let me know what happens.
regards peter
I forgot to say that I have the old Basic Stamp BOE, not the Javelin BOE, so i didn't see a good way to hook up the resistor on it.· So to try the resistor, I switched the Javelin back over to the Stamp PLC.· Is there a way to add the resistor to my BOE?· Attached is a pic.
Also, I went into the 2.0.3 IDE and did debug-messages, and the terminaltest2 window came up, but it wouldn't accept any commands.
between pin2 and pin4 of the 24pin socket. That's how I connected the
resistor on both a PDB and a BoE USB.
After connecting the resistor, try both version 2.0.3 and IDE beta again.
If still no success you should get yourself a usb2ser cable with FTDI chipset
like the ones Parallax sells. Those are guaranteed to work with the javelin
(I assume your pc does have an usb connector),·rather than spending much
more time on this. Apparently there is something with the serial port, perhaps
voltage levels that are not up to standard, that prevents reliable communication.
Or use one of the older pc's you have around·that did work.
Note that if you get a usb2ser cable, the resistor is not required because
both your boards have serial interfaces.
regards peter
·
I had ordered the USB2SER from Parallax 2 days ago, and it just came in this morning.
Once I set the javeline IDE to recognize the new COM port that it created (COM3), I am now able to download programs onto the Javelin Stamp with my PC.
So it must be some problem with the onboard serial ports on these newer Dells:· Precision 390, Optiplex 320.
Thanks for all your help.· Now I can finally get to work.·
Hopefully the next person who has the same problem as I did can benefit from all our troubleshooting.
Regards,
Dan