Wiki » History » Version 15

« Previous - Version 15/24 (diff) - Next » - Current version
Txinto Vaz, 12/19/2013 01:47 AM


uCANca is a toolkit for developing Mechatronic devices. It connects the Systems Engineering point of view with de Software Engineering one. uCANca helps to define a system and automatically generates source code and tools to help the full development cycle of the system.

uCANca can be used to develop:
  • Automotive mechatronic systems.
  • Astrophysics mechatronic systems (telescope instruments, satellites...).
  • Commercial electronic mechatronic systems.
  • Educative robotic systems.
  • ...

It can, obviously, develop simpler devices, like embedded systems, and also other automatisms, etc.

uCANca relies on system architecture concepts and is aimed to the development of Real Time software.

We strongly recommend to have a quick look to our toolkit, it is not enough to know what the tool can do for you, but it is worthy to see if it can captivate your attention before spending a lot of reading time ;) .

uCANca offer tools to help in these tasks:
  • Specification.
  • Test definition.
  • Design.
  • Implementation.
  • Unit testing.
  • Integration Testing.
  • Test execution.
uCANca encourages the team to apply modern development strategies/methodologies like:
  • Agile Modeling.
  • Model-in-the-Loop.
  • Software-in-the-Loop.
  • Hardware-in-the-Loop.
It also connects*1 with other tools like:
  • Matlab/Simulink.
  • Scilab/XCos (Simulink alternative).
  • CodeDesigner RAD (Finite State Machine editor with automatic source code generation).
  • LabView.
This uCANca toolkit also helps the user to include commonly demanded features like:
  • On board diagnostics.
  • ECU calibration.
And can help the team with the ability to:
  • Automatically generate documentation.
  • Synchronize with issue tracking systems.
  • ...

Some of these features are already shipped in the current release, while others are planned for future versions. You can check the roadmap here.

  • *1 connects:This connection is based on file exchange or project sync most of times