This is my first post, so please take it easy on me. I received my ArduCopter this week and assembling went smoothly. I have been flying a MikroKopter Quad and a MikroKopter Octo for two year, so I'm not entirely new to the field. I'm an embedded software engineer (mostly Linux) by profession, with a heavy background in electronics. So most problems I can fix myself, but not this one:
Yesterday I was trying to configure my ArduCopter, using the ConfiguratorTool. Unfortunately this tool depends on the Instruments LABView runtime library. This library, 160MB of it, comes in a wide variety of flavours and versions: minimum/standard, 32/64-bit and 2009/2010. Each one takes ages to download and even longer to install, reboot try if it works and finally to uninstall.
I have found one version to 'work'. That is: With that version he ConfiguratorTool doesn't immediatly complain about the missing runtime library at launch. Not surprisingly that's the version mentioned in the Wiki (good job btw). But when trying to connect to the ArduCopter, it still produces an error about a missing library.
So I've been trying most combinations, until late last night: The Wiki link leads to a 32-bit version, but I've got a 64-bit machine and Windows 7 to match. So trying the 64-bit version seemed logical, but that version isn't detected at launch.
Any idea?
(I'm sorry for my verbosity ;-)
You need to be a member of diydrones to add comments!
Replies
And in it's defense: It works really well! I've got no problem connecting, not even with the default timeout. It shows all the info I need and there's even some help included.