1

\documentclass[12pt,english,a4paper]{book}

     2

\usepackage[T1]{fontenc}

     3

\usepackage[latin9]{inputenc}

     4

\usepackage{graphicx}

     5

\usepackage{amsfonts}

     6

\usepackage{textcomp}

     7

\usepackage{color}

     8

\usepackage{calc}

     9

\usepackage{longtable}

    10

\usepackage{hyperref}

    11

\usepackage{graphics}

    12

\DeclareGraphicsExtensions{.jpg}

    13

\DeclareGraphicsExtensions{.png}

    14

\hypersetup{colorlinks=true, linkcolor=blue, filecolor=blue, pagecolor=blue, urlcolor=blue}

    15

    16

%%%%\%%%%%%%% titre, auteurs, date, etc...%%%%%%%%%%%%%%%%%%

    17

\title{\Huge The CanFestival CANOpen stack manual}

    18

\author{Edouard TISSERANT}

    19

\date{\today}

    20

    21

\setcounter{secnumdepth}{5}

    22

\renewcommand\thesection{\arabic{section} -}

    23

\renewcommand\thesubsection{\arabic{section}.\arabic{subsection})}

    24

\renewcommand\thesubsubsection{\arabic{section}.\arabic{subsection}.\arabic{subsubsection})}

    25

\renewcommand\theparagraph{\alph{paragraph})}

    26

\renewcommand\thesubparagraph{\roman{subparagraph})}

    27

    28

\newcommand{\canopen}{CANopen }

    29

    30

\begin{document}

    31

{\centering\textsf{\huge The CanFestival \canopen stack manual.}}

    32

    33

\renewcommand{\contentsname}{CanFestival v3.0 Manual}

    34

\setcounter{tocdepth}{2} \tableofcontents{}

    35

    36

\clearpage{}

    37

    38

\section{Introduction}

    39

    40

CanFestival is an OpenSource (LGPL and GPL) \canopen framework.

    41

    42

\subsection{The CanFestival project}

    43

    44

This project, initiated by Edouard TISSERANT in 2001, has grown thanks

    45

to Francis DUPIN and other contributors.

    46

    47

Today, CanFestival focuses on providing an ANSI-C platform independent

    48

\canopen stack that can be implemented as master or slave nodes on

    49

PCs, Real-time IPCs, and Microcontrollers.

    50

    51

CanFestival is a project supported by Lolitech.

    52

    53

    54

\subsection{What is \canopen}

    55

    56

CANopen is a CAN based high level protocol. It defines some protocols

    57

to :

    58

    59

\begin{enumerate}

    60

\item Configure a CAN network. 

    61

\item Transmit data to a specific node or in broadcast. 

    62

\item Administrate the network. For example detecting a not responding node. 

    63

\end{enumerate}

    64

The documentation can be found on the CAN in Automation website :

    65

    66

\href{http://www.can-cia.de/canopen}{http://www.can-cia.de/canopen}

    67

    68

The most important document about \canopen is the normative CiA Draft

    69

Standard 301, version 4.02. You can now download the specification

    70

from the CAN in Automation website at no cost.

    71

    72

To continue reading this document, let us assume that you have read

    73

some papers introducing \canopen .

    74

    75

    76

\section{CanFestival Features}

    77

    78

    79

\subsection{Tools }

    80

    81

The \canopen library is coming with some tools :

    82

    83

\begin{enumerate}

    84

\item Object Dictionary editor GUI. WxPython Model-View-Controler based

    85

GUI, that helps a lot in generating object dictionary source code for

    86

each node. 

    87

\item A configure script, that let you chose compile time options such as

    88

target CPU/HOST, CAN and TIMER drivers.\\

    89

 This script has not been generated with autoconf, it has been made

    90

keeping micro-controller target in mind. 

    91

\end{enumerate}

    92

    93

\subsection{Multi-Platform}

    94

    95

\begin{enumerate}

    96

\item Library source code is C-ANSI. 

    97

\item Driver and examples coding conventions merely depend on target specific

    98

contributor/compiler. 

    99

\item Unix compatible interfaces and examples should compile and run on

   100

any Unix system (tested on GNU/Linux and GNU/FreeBSD). 

   101

\end{enumerate}

   102

   103

\subsection{\canopen standard conformance}

   104

   105

\subsubsection{DS-301}

   106

   107

Supported features should conform to DS301. V.4.02 13 february 2002. 

   108

   109

\begin{enumerate}

   110

\item NMT master and slave

   111

\item Heartbeat consumer and producer

   112

\item NodeGuard slave reponder and basic master without tracking

   113

\item SYNC service

   114

\item SDO multiples client and server, segmented and expedited

   115

\item PDO : TPDO and RPDO, with respect to transmission type

   116

\item PDO mapping from/to OD variables bit per bit. 

   117

\item EMCY : Send and receive and keeps track of emergency objects

   118

\item Data types : 8 to 64 bits values, fixed length strings.

   119

\end{enumerate}

   120

   121

\subsubsection{DS-302}

   122

   123

Only concise DFC is supported.

   124

   125

\section{How to start}

   126

   127

\subsection{Host requirements}

   128

   129

What you need on your development workstation.

   130

   131

\subsubsection{Object Dictionary Editor GUI}

   132

   133

\begin{enumerate}

   134

\item Python, with 

   135

\item wxPython modules installed (at least version 2.6.3).

   136

\item Gnosis xml tools. (Optional can also be installed locally to the project

   137

automatically with the help of a Makefile. Please see {}``Using Dictionary

   138

Editor GUI'' ) 

   139

\end{enumerate}

   140

   141

\subsubsection{Linux and Unix-likes}

   142

   143

\begin{enumerate}

   144

\item Linux, FreeBSD, Cygwin or any Unix environment with GNU toolchain. 

   145

\item The GNU C compiler (gcc) or any other ANSI-C compiler for your target

   146

platform. 

   147

\item Xpdf, and the official 301\_v04000201.pdf file in order to get GUI

   148

context sensitive help. 

   149

\item GNU Make 

   150

\item Bash and sed 

   151

\end{enumerate}

   152

   153

\subsubsection{Windows (for native win32 target)}

   154

   155

\begin{enumerate}

   156

\item Visual Studio Express 2005 or worst. 

   157

\item Microsoft platform SDK (requires Genuine Advantage) 

   158

\item Cygwin (for configuration only) 

   159

\end{enumerate}

   160

   161

\subsection{How to get CanFestival}

   162

   163

Please always use CVS, this is the best way to get the most reactive

   164

support from the developer community :

   165

   166

   167

\begin{verbatim}

   168

	cvs -d:pserver:anonymous@lolitech.dyndns.org:/canfestival login

   169

\end{verbatim}

   170

   171

(type return, without entering a password)

   172

   173

Then, enter :

   174

   175

\begin{verbatim}

   176

	cvs -z3 -d:pserver:anonymous@lolitech.dyndns.org:/canfestival co -P CanFestival-3

   177

\end{verbatim}

   178

   179

   180

   181

\section{Understanding Canfestival}

   182

   183

\subsection{CanFestival Project tree layout}

   184

   185

Simplified directory structure.

   186

   187

\begin{verbatim}

   188

./src ANSI-C source of \canopen stack

   189

./include Exportables Header files

   190

./drivers Interfaces to specific platforms/HW

   191

./drivers/unix Linux and Cygwin OS interface

   192

./drivers/win32 Native Win32 OS interface

   193

./drivers/timers_xeno Xenomai timers/threads (Linux only)

   194

./drivers/timers_rtai Rtai timers/threads (Linux only)

   195

./drivers/timers_kernel Linux kernel timer/threads

   196

./drivers/timers_unix Posix timers/threads (Linux, Cygwin)

   197

./drivers/can_virtual_kernel Fake CAN network (kernel space)

   198

./drivers/can_serial Serial point to point and PTY hub (*nix only)

   199

./drivers/can_peak_linux PeakSystem CAN library interface

   200

./drivers/can_peak_win32 PeakSystem PCAN-Light interface

   201

./drivers/can_uvccm_win32 Acacetus's RS232 CAN-uVCCM interface

   202

./drivers/can_virtual Fake CAN network (Linux, Cygwin)

   203

./drivers/hcs12 HCS12 full target interface

   204

./examples Examples

   205

./examples/TestMasterSlave 2 nodes, NMT SYNC SDO PDO, win32+unix

   206

./examples/TestMasterMicroMod 1 node, control Peak I/O Module, unix

   207

./examples/gene_SYNC_HCS12 Just send periodic SYNC on HCS12

   208

./examples/win32test Ask some DS301 infos to a node (win32)

   209

./objdictgen Object Dictionary editor GUI

   210

./objdictgen/config Pre-defined OD profiles

   211

./objdictgen/examples Some examples/test OD

   212

./doc Documentation source

   213

\end{verbatim}

   214

   215

   216

   217

\subsection{Implement CanFestival in your application}

   218

   219

\begin{center}

   220

\includegraphics[width=12cm]{Pictures/10000201000003F9000002CF880931E7} 

   221

\par\end{center}

   222

   223

\bigskip{}

   224

   225

   226

   227

\subsection{CanFestival CAN interfaces}

   228

   229

Because most CAN controllers and drivers implement FIFOs, CanFestival

   230

consider sending message as a non blocking operation.

   231

   232

In order to prevent reentrent calls to the stack, messages reception

   233

is implemented differently on {\textmu}C and OS.:

   234

   235

\begin{enumerate}

   236

\item {\textmu}C must provide interruption masking, mutually excluding timer and CAN receive interrupts.\\

   237

   238

   239

   240

\begin{center}

   241

\includegraphics[width=12cm]{Pictures/10000201000003CA0000016604E6A5EF} 

   242

\par\end{center}

   243

   244

\item OS must provide a receive thread, a timer thread and a mutex. CAN

   245

reception should be a bloking operation.\\

   246

   247

   248

   249

\begin{center}

   250

\includegraphics[width=12cm]{Pictures/10000201000003F9000002CF8B0CDAEA} 

   251

\par\end{center}

   252

   253

\end{enumerate}

   254

   255

\subsection{CanFestival event scheduling}

   256

   257

A \canopen node must be able to take delayed actions.

   258

   259

For instance, periodic sync emission, heartbeat production or SDO timeout

   260

need to set some alarms that will be called later and do the job.

   261

   262

{\textmu}C generally do not have enough free timers to handle all

   263

the \canopen needs directly. Moreover, CanFestival internal data

   264

may be corrupt by reentrant calls.

   265

   266

CanFestival implement a micro -scheduler (timer.c). It uses only one

   267

timer to mimic many timers. It manage an alarm table, and call alarms

   268

at desired time.

   269

   270

\begin{center}

   271

\includegraphics[width=12cm]{Pictures/100000000000022C000000DEDAD2140C} 

   272

\par\end{center}

   273

   274

Scheduler can handle short clock value ranges limitation found on

   275

some {\textmu}C. As an example, value range for a 16bit clock counter

   276

with 4{\textmu}s tick is crossed within 0.26 seconds... Long alarms

   277

must be segmented.

   278

   279

Chronogram illustrate a long alarm (A) and a short periodic alarm

   280

(B), with a A value {\textgreater} clock range {\textgreater}

   281

B value. Values t0...t8 are successive setTimer call parameter values.

   282

t1 illustrates an intermediate call to TimeDispatch, caused by a delay

   283

longer than clock range. Because of long alarm segmentation, at the

   284

end of t1, TimeDispatch call will not trig any alarm callback.

   285

   286

\begin{center}

   287

\includegraphics[width=12cm]{Pictures/1000000000000396000000FFC42573DA} 

   288

\par\end{center}

   289

   290

   291

\section{Linux Target}

   292

   293

Linux target is default configure target.

   294

   295

   296

\subsection{Linux Compilation and installation}

   297

   298

Call ./configure -- help to see all available compile time options.

   299

   300

After invoking ./configure with your platform specific switches, just

   301

type make.

   302

   303

   304

   305

\begin{verbatim}

   306

	./configure [options]

   307

	make

   308

	make install

   309

\end{verbatim}

   310

   311

   312

   313

   314

\subsubsection{Standard Linux node}

   315

   316

   317

\begin{verbatim}

   318

	./configure --timers=unix

   319

\end{verbatim}

   320

   321

   322

To do a \canopen node running on PC -Linux, you need :

   323

   324

\begin{enumerate}

   325

\item A working linux distribution 

   326

\item One or more Peak system PC CAN interface and the last Peak Linux driver

   327

installed. 

   328

\end{enumerate}

   329

   330

\subsubsection{Real -Time Linux node}

   331

   332

With Xenomai :

   333

\begin{verbatim}

   334

	./configure --timers=xeno

   335

\end{verbatim}

   336

With Rtai :

   337

\begin{verbatim}

   338

	./configure --timers=rtai

   339

\end{verbatim}

   340

   341

To do a \canopen node running on PC -Linux, you need :

   342

   343

\begin{enumerate}

   344

\item A working Linux distribution patched with XENOMAI (2.1 or greater) or RTAI (3.6). 

   345

\item One or more Peak system PC CAN interface and the last Peak Real Time

   346

Linux driver installed. 

   347

\end{enumerate}

   348

   349

\subsubsection{Linux kernel node}

   350

   351

To do a CANopen node running on PC-Linux in kernel space, you need:

   352

   353

   354

\begin{enumerate}

   355

\item A working Linux distribution with pre-built 2.6.x.x kernel sources

   356

\item A CAN card driver compatible with CanFestival

   357

\end{enumerate}

   358

   359

   360

\subsubsection{CAN devices}

   361

   362

Currently supported CAN devices and corresponding configure switch:

   363

   364

   365

\paragraph{Peak systems}

   366

   367

   368

\begin{verbatim}

   369

	./configure --can=peak_linux

   370

\end{verbatim}

   371

   372

   373

PeakSystems CAN interface is automatically chosen as default CAN interface

   374

if libpcan is present in the system.

   375

   376

Please download driver at \href{http://www.peak-system.com/linux}{http://www.peak

   377

-system.com/linux} and follow instructions in order to install driver

   378

on your system.

   379

   380

   381

\paragraph{Socket -Can (http://socketcan.berlios.de)}

   382

   383

   384

\begin{verbatim}

   385

	./configure --can=socket

   386

\end{verbatim}

   387

   388

\paragraph{Serial}

   389

   390

   391

\begin{verbatim}

   392

	./configure --can=serial

   393

\end{verbatim}

   394

   395

The CAN serial driver implements a 1:1 serial connection between 2 CAN devices.

   396

For example, you can connect 2 CANFestival applications via a NULL modem cable.

   397

   398

Also with this driver comes a software hub, for up to 16 CANFestival apps to 

   399

be connected on a single PC, with an optional connection to another CAN driver.

   400

Note that only the serial driver is supported at this time.  The hub uses ptys 

   401

(pseudo ttys) available on a *nix like system.

   402

   403

   404

\paragraph{LinCan}

   405

   406

   407

\begin{verbatim}

   408

	./configure --can=lincan

   409

\end{verbatim}

   410

   411

   412

\paragraph{Virtual CAN interfaces (for test/debug)}

   413

   414

   415

\begin{verbatim}

   416

	./configure --can=virtual

   417

		or, for kernel space:

   418

	./configure --can=kernel_virtual

   419

\end{verbatim}

   420

   421

   422

Virtual CAN interface use Unix pipes to emulate a virtual CAN network.

   423

Each message issued from a node is repeat to all other nodes. Currently

   424

only works with nodes running in the same process, and does not support

   425

work with Xenomai or Rtai.

   426

   427

   428

\subsection{Testing your CanFestival installation}

   429

   430

\subsection{User space}

   431

   432

Sample provided in /example/TestMasterSlave is installed into your

   433

system during installation.

   434

   435

   436

\begin{verbatim}

   437

	TestMasterSlave

   438

\end{verbatim}

   439

   440

   441

Default CAN driver library is libcanfestival\_can\_virtual.so., which

   442

will simply pass CAN messages through Unix pipes between Master and

   443

Slave.

   444

   445

You may also want to specify different can interface and define some

   446

CAN ports. Another example using Peak{\textquotesingle}s dual PCMCIA

   447

(configure and install with --can=peak) :

   448

   449

   450

\begin{verbatim}

   451

	TestMasterSlave -l libcanfestival_can_peak.so -s 40 -m 41

   452

\end{verbatim}

   453

   454

   455

\subsection{Kernel space}

   456

   457

   458

\begin{verbatim}

   459

	example/kerneltest

   460

\end{verbatim}

   461

   462

   463

It's based on TestMasterSlave example

   464

and has the same functionality. Uses virtual can driver as default

   465

too. After successful installation you can insert the module by typing:

   466

modprobe canf\_ktest Module control is done by simple console 'canf\_ktest\_console'

   467

which is used to start/stop sending data.

   468

   469

   470

\section{Windows Targets}

   471

   472

CanFestival can be compiled and run on Windows platform. It is possible

   473

to use both Cygwin and win32 native runtime environment.

   474

   475

\subsection{Object Dictionary Editor GUI installation.}

   476

   477

Please refer to \hyperlink{a821UsingDictionaryEditorGUIoutline}{8.2.1)Using

   478

Dictionary Editor GUI}

   479

   480

\subsection{CYGWIN}

   481

   482

\subsubsection{Requirements}

   483

   484

Cygwin have to be installed with those packages :

   485

   486

\begin{enumerate}

   487

\item gcc 

   488

\item unzip 

   489

\item wget 

   490

\item make 

   491

\end{enumerate}

   492

Currently, the only supported CAN devices are PeakSystems ones, with