Tree [89b1b2] master /
 History



File Date Author Commit
 app 2010-07-28 Pavel Pisa Pavel Pisa [65f914] Included CANping (CAN bus stress test utility) ...
 libs4c 2010-07-28 Pavel Pisa Pavel Pisa [8114a2] The submodules provided components included in ...
 scripts 2013-06-25 Pavel Pisa Pavel Pisa [d527e7] Update URLs to the project GIT repositories aft...
 submodule 2010-07-28 Pavel Pisa Pavel Pisa [3f492e] Submodules combined into top-level OrtCAN project.
 .gitmodules 2010-07-28 Pavel Pisa Pavel Pisa [65f914] Included CANping (CAN bus stress test utility) ...
 INSTALL 2005-02-28 ppisa ppisa [e400e4] Committed latest Fanda's modification and pickl...
 Kconfig 2006-07-13 ppisa ppisa [25d53b] The configuration control file for in OCERA tre...
 Kconfig.dep 2004-03-02 ppisa ppisa [f1f791] Added individual Kconfig for CAN and ORTE compo...
 Makefile 2008-07-07 ppisa ppisa [d68c7e] Corrected seeking for MAKERULES_DIR in leaf-nod...
 Makefile.omk 2010-07-28 Pavel Pisa Pavel Pisa [8114a2] The submodules provided components included in ...
 Makefile.rules 2011-08-18 Pavel Pisa Pavel Pisa [8cf878] Linux 3.x kernel KBUILD can be examined by same...
 README 2009-08-15 ppisa ppisa [b85255] OCERA CAN/CANopen components README updated to ...
 README.makerules 2004-12-12 ppisa ppisa [c027e9] Updated location of Paul D. Smith's make 3.81be...
 TODO 2004-11-09 fanda fanda [f13201] :))
 kernelcfg2mk 2011-08-18 Pavel Pisa Pavel Pisa [8cf878] Linux 3.x kernel KBUILD can be examined by same...
 lincan 2010-07-28 Pavel Pisa Pavel Pisa [8114a2] The submodules provided components included in ...
 switch2standalone 2005-02-15 ppisa ppisa [db7a6e] Adjusted for new OCERA_DIR search mechanism
 test-can-in-konsole 2013-11-04 Pavel Pisa Pavel Pisa [63f235] test-script: use fallback to xterm if dcop enab...
 test-vca-socketcan-in-konsole 2013-11-04 Pavel Pisa Pavel Pisa [63f235] test-script: use fallback to xterm if dcop enab...

Read Me

 OCERA CAN/CANopen Componets
 ===========================

The code includes Linux character device style CAN driver,
CAN/CANopen libraries and support utilities.

 LinCAN Driver
 =============

LinCAN driver can be compiled for Linux kernel 2.4.x and 2.6.x.
Each communication object (chip message buffer) can be used
from multiple applications concurrently and separate
queues for each open instance are kept.

To check for latest release of LinCAN driver, look at it
FreshMeat page

  http://freshmeat.net/projects/lincan/

More comprehensive README for the LinCAN driver is located
in "lincan" subdirectory with driver sources.

  Driver and CAN/CANopen Components Sources Locations
  ===================================================

The development sources are located in OCERA CVS source forge
repository for now, but switch to GIT and may it be even different
location is expected when SF.net GIT repository support matures.

  http://sourceforge.net/projects/ocera/
  http://ocera.cvs.sourceforge.net/ocera/ocera/components/comm/can/

The temporary location for experimental code is in CTU local GIT
repository

  http://rtime.felk.cvut.cz/gitweb/lincan.git
  git://rtime.felk.cvut.cz/lincan.git

The latest version of whole OCERA CAN components tree can be
obtained from SF.net CVS.

  cvs -d:pserver:anonymous@ocera.cvs.sourceforge.net:/cvsroot/ocera login
  cvs -z3 -d:pserver:anonymous@ocera.cvs.sourceforge.net:/cvsroot/ocera co ocera/components/comm/can

Next commands builds OCERA CVS CAN components outside OCERA tree

  cd ocera/components/comm/can
  ./switch2standalone
  make

The selection of required features and options can be specified before make
command invocation. Lines containing required changes to config.omk-default
file should be stored in config.omk file. The config.omk is not altered
by OMK system and options defined there override values defined
in config.omk-default file. GNU make program version 3.81beta1 or newer
is required by OMK make-system. If this is problem, LinCAN driver alone
can be compiled with use of old style Makefiles as well.

The full description of OMK build system is provided on OMK homepage

  http://rtime.felk.cvut.cz/omk/

The official OCERA CAN components and LinCAN releases are located
in the SourceForge OCERA project files group

  http://sourceforge.net/projects/ocera/
    LinCAN files group

LinCAN development status page is kept up to date at FreshMeat

  http://freshmeat.net/projects/lincan/

Bookmark that page if you want to be informed about next releases.
The version from the OCERA CVS is recommended for active developers.


 OCERA CAN/CANopen Library and Programs
 ======================================

The projects provides VCA library which allows to build customized
master and slave CANopen devices, connect internal CAN infrastructure
based on Virtual CAN API to different drivers etc.

CANopen programs build above VCA library provide implementation
of basic CANopen device and control/master/TCP bridge system.

Unique is ability of the provided generic CANopen slave device program
to mimic CANopen dictionary of arbitrary CANopen device if EDS file exists.
The device dictionary is build at program startup directly from EDS file.
The program even provides option to connect some of objects
in dictionary with real hardware by use of dynamically loadable
modules (shared libraries with predefined interface).

CANblaster program is bridge between CAN/CANopen communication
protocol and TCP based remote access to the CAN network
and allows remote access and monitoring of CAN/CANopen
network through Java base monitor program.

The build of CANmonitor is enabled by selecting respective
option in OMK config file.

  echo >>config.omk CONFIG_OC_CANMONITOR=y

  make

The functionality of OCERA VCA components can be tested
by running main programs in multiple tabs of KDE console
through invocation of test script

  ./test-vca-socketcan-in-konsole


Build of OCERA CAN/CANopen components with SocketCAN Support
===========================================================

To build code, next steps are required:
 1) ensure, that CAN/SocketCAN support is enabled in kernel
    and modules can-raw and vcan are build

 2) download latest OCERA VCA CAN code or use CVS
      cvs -z3 -d:pserver:anonymous@ocera.cvs.sourceforge.net:/cvsroot/ocera co ocera/components/comm/can
 2a) switch CVS code to standalone build

      cd ocera/components/comm/can

      ./switch2standalone
      
 3) add CONFIG_OC_CANVCA_IFC and possibly CONFIG_OC_CANVCA_IFC_socketcan to
    the config file

      cd ocera/components/comm/can

        echo >config.omk  CONFIG_OC_CANVCA_IFC=socketcan
        echo >>config.omk CONFIG_OC_LINCAN=n
	echo >>config.omk CONFIG_OC_ULUTKERN=n

    or if both LinCAN and SocketCAN support is required

        echo >config.omk  CONFIG_OC_CANVCA_IFC=multi
        echo >>config.omk CONFIG_OC_CANVCA_IFC_socketcan=y
        echo >>config.omk CONFIG_OC_CANVCA_IFC_lincan=y
        echo >>config.omk CONFIG_OC_LINCAN=y

    enable Java CANmonitor

        echo >>config.omk CONFIG_OC_CANMONITOR=y

    on some systems (i.e. x86_64) next option is required

        echo >>config.omk CFLAGS+=-fpic

  4) build project
         make
  
  5) run next script in KDE console
     ./test-vca-socketcan-in-konsole

You should see one CANopen device with DS-401 dictionary running
in one console, master/blaster in another and Java based monitor
should be started. If you open nascan.eds you can get model
of device dictionary and could use it to download and upload
values to dictionary objects.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks