Header Overview

The most frequently asked questions and answers regarding AscTec Communication Interface (ACI).

 

  • Q: I don't receive any data when using ACI (Tool), but the AutoPilot Control Software receives data. Why?

  • Q: You wrote, that you set all variables, commands and parameters with a fixed id. What happened, if i.e. a variable still doesn't exist in its form (because of changing the hardware)?
  • Q: I am sending a lot of variables over „aciSingleSend“ with an acknowledge, but sometimes they will not be sent. Why?
  • Q: The ACI Tool doesn't save the lists on the hard-drive on Windows. It creates a file called “data”, but the file is still empty. How can I fix it?
  • Q: How can I use the ACI Tool on the mastermind? I cannot connect to any device because there is no /dev/ttyUSB* device listed.
  • Q: Why has the ACI Tool not all functionality, which ACI completely supports?
  • Q: I have published a lot of new variables/commands/parameters in the AscTec SDK V3 code, but not all variables/commands/parameters are committed, if I request them over the ACI Tool or over the ACI Remote SDK. Why?

 


Q: I don't receive any data when using ACI (Tool), but the AutoPilot Control Software receives data. Why?

A: Most propably you don't have a connection to the High-Level Processor (HLP). The AutoPilot Control Software uses the Low-Level Protocol and the XBee is connected to the LLP in delivery condition. Please make sure you have connected the XBee to the HL Serial 0 port. Otherwise the ACI will not work.

Q: You wrote, that you set all variables, commands and parameters with a fixed id. What happened, if i.e. a variable still doesn't exist in its form (because of changing the hardware)?

A:  First of all, a new id will be created for the new variable. After that, there are two possibilities, what happened with the old one: First option is to calculate the new variable to its old form and publish it with the old id. That means, that you can get the variable in both forms and all your old code with the older hardware will be compatible with the new sensor. If it not possible to calculate the new variable in its old form, then the old id will be not published in any form again until there will be a option to calculate it again to its old form. 

Q: I am sending a lot of variables over „aciSingleSend“ with an acknowledge, but sometimes they will not be sent. Why?

A: Sending with an acknowledge means, that you are buffering your sending variables and with the next ACI engine period, the buffer will be sent.
If you are sending a lot of variables in a row, it is recommended to publish the variable and request it.

Q: The ACI Tool doesn't save the lists on the hard-drive on Windows. It creates a file called “data”, but the file is still empty. How can I fix it?

A: When the file doesn't exist, it creates it with read-only proprietary enabled. To fix that, disable this proprietary and it should work.

Q: How can I use the ACI Tool on the mastermind? I cannot connect to any device because there is no /dev/ttyUSB* device listed.

A: Your normal FTDI chip connected with you desktop pc via USB is recognized in many linux distributions as a USB device. The mastermind defines the device on ttyS2, because it is connected over a super I/O and not over USB. A fast and easy fix would be a symbol link on the device via

Otherwise, you can also change one single line in the ACI Tool. Only change ttyUSB to ttyS.

Q: Why has the ACI Tool not all functionality, which ACI completely supports?

A: The ACI Tool was designed for fast testing of your program written on your UAV. In most cases, it is enough to test, if your written code on your device is working and if all variables, commands and parameters are published or not. The most of the ACI Tool is UI design and not ACI itself. Take a look at the ACI Tool documentation to see, how much ACI is in the tool. Writing a testing tool (only text-based) is done with some lines of code (take a look on the tutorials). In the most times, it is still easier to write your own code instead of testing everything with the ACI Tool.

Q: I have published a lot of new variables/commands/parameters in the AscTec SDK V3 code, but not all variables/commands/parameters are committed, if I request them over the ACI Tool or over the ACI Remote SDK. Why?

A: The amount are limited of publishing data in the ACI code. For that, please take a look in the asctecDefinesOnBoard.h code and look for the defines:

Increase the number if you want to to publish more than the limit.