So as long as the IDE detects echo you can program a BASIC Stamp.I havent noticed this with other versions of Windows, however it may be a problem with newer drivers.So if you have had any issues with your Propeller not being detected when using the USB interface please read below.
When installing the FTDI Driver, either via the included driver in the Propeller Tool or BASIC Stamp IDE, or when running the CDM Installer from FTDI you should see the following command (DOS-like) box pop-up during the driver installation. If you do not, then the drivers were not installed. CLICK FOR LARGER VIEW) I have seen where the driver setup had to be run at least twice to get this to appear and most assume that if theyve run the driver and accepted the box asking for permission to make changes to the system that everything is good. Ftdichip Cdm Package Download The LatestIf you did not see this box then download the latest driver from the ftdi website at the following link: In the row for Windows in the comments column are the words setup executable, which is a link to download the setup installer. When running the driver, if you do not see the command window above re-run it. Ftdichip Cdm Package Software Or EvenIf after three tries you still have not seen it you may have another issue such as insufficient permissions, anti-virus software or even malware preventing the install. ![]() You should see the following dialogue box which already has the FT232R ProductVendor IDs in the box. Click the Add button to add this ProductVendor ID to the list of devices to remove. Optionally you can check the Generate log file checkbox for a record of what operations were performed and which COM Port entries were removed. Once completed you should restart your computer so that the OS can clean things up. You should then be ready to re-install your drivers as listed above. I hope this helps. Sometimes driver installations dont go as planned and the reasons may not be anything we can diagnose andor help with. Ftdichip Cdm Package Serial Solutions WouldBut over in the Pololu forum David Grayson implied that more usb to serial solutions would work if Parallax implemented a work around to the Windows built in virtual COM port driver bug. Heres what David said The main problem was that there was a bug in the Windows USB-to-serial driver usbser.sys and the Parallax software didnt implement a workaround for it. Specifically, if the software changes the value of the RTS control line for the virtual COM port, the driver doesnt actually send that new value to the Wixel right away. Instead it waits until the next time DTR is changed by the software. ![]() I know there is some workaround to this because the problem doesnt happen if you control the COM ports RTS line using the.NET SerialPort class, but to implement that workaround would require changing the Parallax software. There might have been some other issue with the Send Break command, but we dont remember. I asked him why the FTDI based cables didnt have this problem and he said the FTDI chips have their own driver, ftdibus.sys, so they dont use usbser.sys and are not subject to its bugs. Basically has Parallax ever tried the work around Being able to use the built in virtual COM port driver could be handy. The problem I am seeing involves installation of the driver, not what you described. As for the loopback issue, while I have not seen this, loopback is not required for the IDE to program the BASIC Stamp, however echo is.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |