Help request and questions about compatibility issues with the provided Simulik toolkit

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Help request and questions about compatibility issues with the provided Simulik toolkit

Mauro
The dcoumentation on the SDK provided with the lateset Humming bird version is not clear.

We bought the Asctec Humming bird on November 2014.

The drone is equiped with Low Level Firmware V3.13

We would like to use the provided Simulink toolkit, which seems to have been tested for Matlab 2011b with  SDK 2.0 (documentation says that ACI_device is not included but the files are contained in the archive which can be downloaded now from the website, but they are more updated).

We attempted to use both the SDK2.0 and SDK3.0 with the Matlab generated code (Matlab 2012b, windows 7), without success. In particular, the code is generated, the SDK2.0 compiles but the on the drone it does not work correctly (no data received when using UART_communication, despite the Xbee modules being correctly connected to the HL0 port, configured and recognised with the suggested XCTU tool)

Is there a compatibility issue between the LL firmware V3.13 and the SDK2.0?

The SDK 3.0 set with Simulink configuration does not compile. Is there a compatibility issue between the SDK 3.0 and the onboard.mdl file provided on the asctec dowload page? (We already attempted all the possible troubleshooting suggested in the documentation)

Has the simulink toolkit been tested so far on Matlab 2012b or above?

Could you please state  which set of compatible SDK, operating system, Matlab version, firmware version, etc has the provided simulink tool kit (custm mdl files) been tested and known to work? If I am not mistaken, there is no tested simulink support for the SDK3.0 and the latest firmware.


Thank you for your answers,

Mauro
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help request and questions about compatibility issues with the provided Simulik toolkit

Mauro
Furthermore, we correctly generated the code with matlab before compiling the project on Eclipse.

What is the correct folder structure to include the matlab generate code with the SDK2.0 and SDK3.0?

Thanks

Mauro
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help request and questions about compatibility issues with the provided Simulik toolkit

andre@asctec
Hi Mauro,

we definitely recommend to use the SDK3.0. I am running Windows 8.1 with Matlab R2014b and the Simulink Toolkit works fine.

You should have the following folder structure. Let's denote your Eclipse workspace folder <workspace>, then you should have:
<workspace>/AscTec_SDK_v3.0
<workspace>/custom_mdl

If you now select the Simulink build configuration in eclipse, it should compile without problems. Eventually, the compilation process aborts with an error message concerning a missing header. If that is the case, please copy the error message here. I think I remember a workaround, but I need to see the message to give you the right instructions.

Cheers,
Andre
Andre Ryll
AscTec Application Engineer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help request and questions about compatibility issues with the provided Simulik toolkit

Mauro
It gives me the following error:

Description                                                       Resource   Path Location  Type
Invalid project path: Duplicate path entries.
Error launching external scanner info generator (gcc -E -P -v -dD C:/Users/utente/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c)  


   Resource              Path   Location                Type
AscTec SDK V3.0       pathentry          Path Entry Problem
AscTec SDK V3.0        Unknown            C/C++ Problem


Furthermore, if I try to go to project properties->  C/C++ Build    it gives an error of java.lang.NUllPointerException


Thanks

Mauro
Loading...