The device shows up in the list, but the connection attempt fails immediately. This is usually due to invalid permissions on the device. For udev-based systems, you can resolve this by adding rules for the device. Open a terminal: cd /etc/udev/rules.d Create a file to hold the FTDI rules: sudo nano 40-ftdi.rules And add the … Read more
Many devices, including our own, use a VCP (virtual COM port) chip from FTDI to communicate with a computer.The driver situation for this type of device is a little bit messy. For Windows, you should not need to install drivers, but you can install the VCP drivers from FTDI if you want. For Ubuntu, you … Read more
Most hardware vendors integrate to Dragonframe using our DFMoco protocol (the same that we offer for free as Arduino code). The is a non real-time protocol. It provides shoot-move-shoot motion control, and is sufficient for almost all stop-motion animation. The eMotimo spectrum ST4 is the first third-party system to directly implement our real-time protocol. This … Read more
Robotic arms work very differently from typical motion control cranes. We do not have the expertise to create any type of integration, or to offer any help if you attempt to do it. The only integration you could reasonably do is to use separate software to program moves on the arm, and just work with … Read more
We try to maintain a list of compatible hardware in our FAQ(see previous questions). There is no standard protocol for operating with motion control hardware, so unless it’s on our list, or Dragonframe support is listed on the manufacturer’s page, it’s not going to work. The third party manufacturer must integrate their system with Dragonframe … Read more