Hi, I just got my ARC-32. It’s my first step into this kind of hobbyist robotics. I’ve been trying to set up with little success. I’ve got a lynxmotion 6v power supply and I’ve hooked it up. When I switch it on, the PWR led turns green, and the STATUS led flashes constantly. I figured this probably wasn’t an error message, merely an initial program when there is nothing else to run. (is this correct?)
I’m running win7 64 bit, and I installed BM IDE fine, but the drivers basicmicro.com/Downloads_ep_43.html give me an error when I try to install them. When I extracted them there were 2 executables, and I ran the one with"64" on the end (as opposed to “32”). The error I’m getting is:
Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)
And when I try to connect in BM IDE, its finds nothing. I’m assuming the issue is with my installation of the driver, but could it have something to do with the blinking STATUS led?
thanks
I am pretty sure the blinking is normal. They preprogrammed each board with a test program…
Sorry, but I have never tried running my processors in 64 bit mode. I installed Windows 7 32 bit as to avoid issues like this. You may want to try the more up to date releases of studio. The post them under the news section of their forums. Most current is up on this thread: forums.basicmicro.net/news-f481/ … t9344.html
Also it may not be unusual for their drivers to not have the proper signatures. If you plug in a usb cable and power up the board, is a new comm port created? If so if you set the studios comm port to the new one and configure it for an Atom Pro and BMAtomPro Arc32, does it find the board? Not sure what else to ask now. Hopefully Nathan (Acidtech) will have more information.
Looks like its complaining that the driver files are not signed. I’ve had some Win7 64bit installs complain while others do not. I’ve yet to find a consistent method to force Win7 to install the unsigned drivers when it doesn’t want to. These are not kernel mode drivers so it should not be complaining but it does.
So to work around this you can force Win 7 to use the original FTDI drivers.
Once you’ve downloaded the drivers and unzipped the file here are the steps:
Open the Device Manager.
a. To do that click the Start button and then right click on Computer and click Properties. In the Properties window Click Device Manager.
Click the View menu in Device Manager and change to Devices by Connection.
Expand ACPI/Microsoft ACPI/PCI Bus/
Expand each USB Controller until you find the BasicMicro Communications Port.
Right click it and click uninstall. Check the “Delete driver files for this device” and click ok.
Click Action menu and Scan for hardware changes.
You should now see Communications Port were BasicMicro comport was before.
Right click Communications Port and click “Update Driver Software”.
Click “Browse my computer for driver software”
Click “Let me pick from a list of device drivers on my computer”.
Click Next on the new window
Click Have Disc
Browse to the folder you unzipped the FTDI drivers to.
Select the ftdibus.inf file and click OK.
Click OK again.
Select USB Serial Converter and click Next
Click Yes on the warning that comes up.
Click Close when driver finishes installing.
Second part.
In device manager you should now see USB Seriual Converter. Expand it if it isn’t already. Right click on USB Serial Port and click update driver software.
Follow steps 8 to 17 again but choose ftdiport.inf and select USB Serial Port in the selection window.
Right click on the USB Serial Port and click Properites. Click Port Settings. Click Advanced buttons. Click the Latency Drop down and set to 1. Click OK.
Your comport should now be installed without warnings/errors and you should be able to find the ARC-32 in Studio now(after you restart studio).
