Admin at 22:15, 12 December 2014

2014-12-12T22:15:47Z

Admin at 08:29, 24 August 2013

2013-08-24T08:29:07Z

Admin: Created page with "= Action = Configures the CAN bus mode. =
2013-08-24T08:28:22Z

Created page with "= Action = Configures the CAN bus mode. = <sp..."

New page
= Action =

Configures the CAN bus mode.

 

 

= Syntax =

CONFIG CANBUSMODE =mode

 

 

= Remarks =
<div style="padding: 0px; margin: 0px 0px 0px 4px;">
{| width="604" cellspacing="0" cellpadding="1" border="1" style="border: 2px solid rgb(0, 0, 0); border-spacing: 0px; border-collapse: collapse;"
|- style="vertical-align: top;"
| valign="top" width="13%" style="width: 75px; border: 1px solid rgb(0, 0, 0);" |
mode

| valign="top" width="100%" style="width: 520px; border: 1px solid rgb(0, 0, 0);" |
The CAN bus can be set to 3 different modes.

- ENABLED : TxCAN and RxCAN are enabled.

- STANDBY : TxCAN is recessive and the receiver is disabled. The registers and mobs can be accessed.

- LISTENING : This mode is transparant for the CAN channel. It enables a hardware loop[ back from the internal TxCAN to the RxCAN. It provides a recessive level on the TxCAN output pin. It does NOT disable the RxCAN pin.

|}
</div>
 

The CAN commands are intended for the AVR processor AT90CANXXX series.

You need to terminate the bus with 120 ohm at both ends.

 

Your code always need a number of statements.

CANRESET

Will reset the CAN controller. Use this only once.

 

CANCLEARALLMOBS

Will clear all message objects. This is best to be done right after the CANRESET.

 

CANBAUD

All devices on the bus need to have the same baud rate. Set the BAUD right after you have cleared all objects.

 

CONFIG CANBUSMODE

Now you chose the mode the bus will work in. This is ENABLED in most cases.

 

CONFIG CANMOB

Here you define the properties of each Message Object. This need to be done only once.

 

CANGIE , ON CAN_IT

Since the interrupt TX, RX and ERR interrupts are used you need to assign a value of &B10111000 to CANGIE.

You also need to assign an interrupt routine to the CANIT interrupt.

 

In the main code you can send data using CANSEND.

 

The interrupt routine.

The CANPAGE register is saved into the _CAN_PAGE variable. This is required since the interrupt may not change the CANPAGE register.

Then CANGETINTS is used to retreive all message object interrupt flags. The value is stored in _CAN_MOBINTS.

 

Since multiple Message Objects can cause an interrupt we check all message objects with a For.. Next loop to test all bits. If the bit is set, the Message Object is selected with CANSELPAGE.

Then the CANSTMOB register is tested for a number of bits/flags.

If bit 5 is set, it means that a frame was received. For the demo the ID is read with CANID.

The CANRECEIVE function reads the data from the frame into a variable. In the example the variable is a PORT which will change value depending on the receive data byte.

After this the CONFIG CANMOB is used with a value of -1 to indicate that the operation must be done on the current selected MOB.

The object is put back into receive mode.

 

If bit 6 is set it means that data was transmitted with success. Again, we use CONFIG CANMOB so the object can be used again. For transmitting we put the object into DISABLED mode.

 

And lastly we test bit 0, the MOB error bit. It if was set it means there was an error when data was sent using CANSEND. We must use CONFIG CANMOB so the MOB can be used again.

 

We must clear the CANSIT1 and CANSIT2 flag registers before we exit the interrupt routine. We also need to reset the interrupt flags inCANGIT. This is done by writing the same value back to CANGIT. A one will clear the flag if it was set.

Last we restore the CANPAGE register by writing _CAN_PAGE back to it.

 

While the interrupt routine shows some PRINT statements, it is not a good idea to print inside the/a interrupt routine. You should keep the delay as short as possible otherwise you might not be able to process all CAN frames.

 

 

 

= See also =

[[CONFIG CANMOB|CONFIG CANMOB]] , [[CANBAUD]], [[CANRESET]], [[CANCLEARMOB]], [[CANCLEARALLMOBS]], [[CANSEND]], [[CANRECEIVE]] , [[CANID]], [[CANSELPAGE]], [[CANGETINTS]]

 

 

= Example =

<source lang="bascomavr">
'------------------------------------------------------------------------
' CAN-Elektor.bas
' bascom-avr demo for Auto-CANtroller board
'------------------------------------------------------------------------
$regfile = "m32can.dat" ' processor we use

$crystal = 12000000 ' Crystal 12 MHz
$hwstack = 64
$swstack = 32
$framesize = 40

'$prog &HFF , &HCF , &HD9 , &HFF ' generated. Take care that the chip supports all fuse bytes.
Config Porta = Output ' LED
Config Portc = Input ' DIP switch
Portc = 255 ' activate pull up

Config Com2 = 19200 , Synchrone = 0 , Parity = None , Stopbits = 1 , Databits = 8 , Clockpol = 0
Open "COM2:" For Binary As #2

Dim _canpage As Byte , _canid As Dword , _can_int_idx As Byte , _can_mobints As Word
Dim Breceived As Byte , Bok As Byte , Bdil As Byte

On Can_int Can_int ' define the CAN interrupt
Enable Interrupts ' enable interrupts

Canreset ' reset can controller
Canclearallmobs ' clear alle message objects
Canbaud = 125000 ' use 125 KB

Config Canbusmode = Enabled ' enabled,standby,listening
Config Canmob = 0 , Bitlen = 11 , Idtag = &H0120 , Idmask = &H0120 , Msgobject = Receive , Msglen = 1 , Autoreply = Disabled 'first mob is used for receiving data
Config Canmob = 1 , Bitlen = 11 , Idtag = &H0120 , Msgobject = Disabled , Msglen = 1 ' this mob is used for sending data

Cangie = &B10111000 ' CAN GENERAL INTERRUPT and TX and RX and ERR
Print #2 , "Start"

Do
If Pinc <> Bdil Then ' if the switch changed
Bdil = Pinc ' save the value
Bok = Cansend(1 , Pinc) ' send one byte using MOB 1
Print #2 , "OK:" ; Bok ' should be 0 if it was send OK
End If
Loop

'* CAN CONTROLLER INTERRUPT ROUTINE
'multiple objects can generate an interrupt
Can_int:
_canpage = Canpage ' save can page because the main program can access the page too
Cangetints ' read all the interrupts into variable _can_mobints

For _can_int_idx = 0 To 14 ' for all message objects
If _can_mobints._can_int_idx = 1 Then ' if this message caused an interrupt

Canselpage _can_int_idx ' select message object

If Canstmob.5 = 1 Then ' we received a frame
_canid = Canid() ' read the identifier
Print #2 , Hex(_canid)

Breceived = Canreceive(porta) ' read the data and store in PORTA
Print #2 , "Got : " ; Breceived ; " bytes" ' show what we received
Print #2 , Hex(porta)
Config Canmob = -1 , Bitlen = 11 , Msgobject = Receive , Msglen = 1 , Autoreply = Disabled , Clearmob = No
' reconfig with value -1 for the current MOB and do not set ID and MASK
Elseif Canstmob.6 = 1 Then 'transmission ready
Config Canmob = -1 , Bitlen = 11 , Msgobject = Disabled , Msglen = 1 , Clearmob = No
' reconfig with value -1 for the current MOB and do not set ID and MASK
Elseif Canstmob.0 = 1 Then 'ack error when sending data 'transmission ready
Print #2 , "ERROR:" ; Hex(canstmob)
Config Canmob = -1 , Bitlen = 11 , Msgobject = Disabled , Msglen = 1 , Clearmob = No
End If
End If
Next
Cansit1 = 0 : Cansit2 = 0 : Cangit = Cangit ' clear interrupt flags
Canpage = _canpage ' restore page
Return

</source>

{{Languages}}

[[Category:BASCOM Language Reference]]

@@ Line 41: / Line 41: @@
 &nbsp;
-Your code always need a number of statements.
+Your code always need a number of statements. The best solution is to use the can-elektor.bas sample to get started.
 <span style="font-weight: bold; color: rgb(51, 102, 255);">CANRESET</span>
@@ Line 69: / Line 71: @@
 <span style="font-weight: bold; color: rgb(51, 102, 255);">CONFIG CANMOB</span>
-Here you define the properties of each Message Object. This need to be done only once.
+Here you define the properties of each Message Object. This need to be done only once. But after the message object has been used, you need to configure it again so the new MOB can be used again.
 &nbsp;
@@ Line 115: / Line 117: @@
 &nbsp;
-We must clear the&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANSIT1</span>&nbsp;and&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANSIT2</span>&nbsp;flag registers before we exit the interrupt routine. We also need to reset the interrupt flags in<span style="font-weight: bold; color: rgb(51, 102, 255);">CANGIT</span>. This is done by writing the same value back to&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANGIT</span>. A one will clear the flag if it was set.
+We must clear the&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANSIT1</span>&nbsp;and&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANSIT2</span>&nbsp;flag registers before we exit the interrupt routine. We also need to reset the interrupt flags in&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANGIT</span>. This is done by writing the same value back to&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANGIT</span>. A one will clear the flag if it was set.
 Last we restore the&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">CANPAGE</span>&nbsp;register by writing&nbsp;<span style="font-weight: bold; color: rgb(51, 102, 255);">_CAN_PAGE</span>&nbsp;back to it.
@@ Line 125: / Line 127: @@
 &nbsp;
-<span style="font-family: Arial;">&nbsp;</span>
+As you can see in the sample, the MOB's are configured at the start AND once they are used so they can be re-used.
-<span style="font-family: Arial;">&nbsp;</span>
+In the example all lines are important except for the PRINT lines.
 = <span class="f_Header">See also</span> =

@@ Line 217: / Line 217: @@
 Return
-</source>
+</source> {{Languages}}
-−
-&#x7B;&#x7B;Languages&#x7D;&#x7D;
 [[Category:BASCOM Language Reference]]

CONFIG CANBUSMODE - Revision history

Admin at 22:15, 12 December 2014

Admin at 08:29, 24 August 2013