nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: Testing your CanFestival installation nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210:
nico@210: nico@210: next nico@210: nico@210: up nico@210: nico@210: previous nico@210: nico@210: contents nico@210:
nico@210: Next: Windows Targets nico@210: Up: Linux Target nico@210: Previous: Virtual CAN interfaces (for nico@210:   Contents nico@210:
nico@210:
nico@210: nico@210: nico@210:

nico@210: Testing your CanFestival installation nico@210:

nico@210: Sample provided in /example/TestMasterSlave is installed into your nico@210: system during installation. nico@210: nico@210:

nico@210: TestMasterSlave nico@210: nico@210:

nico@210: Default can driver library is libcanfestival_can_virtual.so., which nico@210: will simply pass CAN messages through Unix pipes between Master and nico@210: Slave. nico@210: nico@210:

nico@210: You may also want to specify different can interface and define some CAN nico@210: ports. An other example using Peaks dual PCMCIA nico@210: (configure and install with -can=peak) : nico@210: nico@210:

nico@210: TestMasterSlave -l libcanfestival_can_peak.so -s 40 -m 41 nico@210: nico@210:

nico@210:

nico@210:
nico@210: epimerde nico@211: 2007-06-06 nico@210:
nico@210: nico@210: