CANbus

[Timmoore]

Thanks Joe S for the links, I already looked at most of Microchip data sheets and Application notes. Lots on M2510 but not much on ECAN.

Just checked the 18F4580 Errata, but there is nothing in there wrt CAN.

INSE, I just had a look at the 18F248 data sheet and the CAN module has the same basic register set as the 4580 ECAN module. The CAN module is more appropriate to my requirements and my code should not require any major changes to run on 18F248. I have ordered a few of them today - did you have any problems or did you find everything pretty straightforward ?

[inse]

Hi Tim,

I suggest you start setting up communication in one direction first and add the reply function in the next step.
Make your receiver blink a LED or put out something on a terminal when it has successfully received data.
I have been debugging my CAN settings with a Microchip MCP2515 eval board that I won on a exhibition years ago.
CAN is not that easy if you start from zero, so it was very helpful to have something at hand that HAD to be working...

My CAN node sends data to a unit and only acknowledges incoming messages.

while (RXB0CON.7 = 1) or (RXB1CON.7 = 1) 'check receive flag and wait for silence on CAN-Bus
RXB0CON.7 = 0
RXB1CON.7 = 0
pause 100
@ clrwdt
wend

After that the PIC shuts down, maybe you can implement a check of the receive flag to blink a LED...

How does your CAN setup look like?
My init sequence:

CANCON = 128 'Config Mode
brgcon1 = $01
brgcon2 = $BF
brgcon3 = $07
ciocon = 32 'CANTX recessive high

TXB0SIDH = $AE 'Identifier für Klemmenstatus =$575
TXB0SIDL = $A0 'Identifier für Klemmenstatus
TXB0DLC = 1 ' Länge 1 Byte

CANCON = 0 ' Normal Mode

I got the BRGCON values from the Microchip calculator for 100 kBaud and 10MHz clock.

I see from your post, that you more or less already tried out the tips I could give you.

I also noticed that the terminator resistor disturbed transmission, so I skipped it.
Which CAN transceiver are you using?
Can you post some snippets of your code?
If your PIC has internal PLL, did you configure it correctly?

Regards,

Ingo

[Timmoore]

Hi Ingo

Code wise, I am doing the same configuration with the exception that my BRG con values are for 125Khz and 16Mhz. Beyond that I am setting data byte values for tx. I will send you code for perusal in due course.

I think given what I am seeing with the scope, it is clear that there is something fundamentally wrong with timing. You are correct in your suggestion about the PLL. This is the first time I have used this particular pic. I have just checked the data sheet and it looks like I may have to set the configuration. Need to read up a bit as there are a few registers involved.

The transceiver is MCP 2551, I am seeing very clean signals on the twp so I dont think the resistors are presenting a problem. Depending on the outcome of the PLL investigation, I can remove one, then both to check the effect.

Rgds

Tim

[Timmoore]

Hi Ingo,

Update for you,

Received two 18F248 today. snatched half an hour to quickly try out, but no bus activity at all. getting the same results as for 18F4580 otherwise.

Also tried using your configuration ( modified to 16Mhz OSC)


FYI, here is my transmit code for 18F4580



define OSC 16

TRISB = %00000010 'Set portb.2 output (cantx) ,b.2 input (canrx) 18F248/4580
'************************************************* ***************
' Include "CanRxDeclarePic18.bas"
'************************************************* ***************
TXB0DLC = $00
TXB0D0 = $00
TXB0D1 = $00
TXB0D2 = $00
TXB0D3 = $00
TXB0D4 = $00
TXB0D5 = $00
TXB0D6 = $00
TXB0D7 = $00

'************************************************* ***************************
' Include "CanVarsPic18.bas"
'************************************************* ***************************

DataBytesTx VAR BYTE 'number of bytes to transmit from SPI / MCP2510
DataBytesTx = 0
CanDataTx VAR BYTE[8] '0 - 7 data bytes to send (xmit)
k var byte

for k = 0 to 7
CanDataTx[k] = 0
next


TREQ var bit
TREQ =0


CanStatusReg var byte
CanControlReg var byte
RxBuffer0Control var byte
ExtCanControl var byte
BaudRateGenControl1 var byte
BaudRateGenControl2 var byte
BaudRateGenControl3 var byte
CanIOControl var byte
PeripheralInterruptReg3 var byte
PeripheralInterruptEnable var byte
CnfgReg1 Var byte
'************************************************* ***************
' CanConfig
'************************************************* ***************

CANCON.7 = 1 'Request configuration mode (looped on CANSTAT)
CanStatusReg = CANSTAT

'Set Data Rate based on 16Mhz OSC See page 332
'125 kbs:
BRGCON1 = $07 'brp = 7(16 mhz), jump 1 TQ (SWJ): 8Tq = 1x10.6/8 = 125Kbs data rate
BRGCON2 = $90 'freely programmable , sample once, 3TQ seg1,propogation time 1Tq
BRGCON3 = $02 '3TQ seg2
BaudRateGenControl1 = BRGCON1
BaudRateGenControl2 = BRGCON2
BaudRateGenControl3 = BRGCON3

'CIOCON see page 314

CIOCON = $30 ' bit 5 set, CANtx drives vdd when recessive, bit 4 set,enable CAN capture
CanIOControl=CIOCON
TXB0SIDH = $10 'b7 - b0 = SID10- SID3
TXB0SIDL = $10 'b7 = SID2, b6 = SID1, b5 = SID0, b3=EXIDE = 0 for SID, 1 for EID



CANCON = $08 'request normal mode set tx buffer 0
CanControlReg = CANCON
CanStatusReg = CANSTAT



'************************************************* ***************


k=1

'------------------------------------------------------------------------------

' Program Loop Program Loop

'------------------------------------------------------------------------------


Main:
PeripheralInterruptEnable =PIE3
if k >=256 then k=0
'*********Transmit Data **************************



' CANCON = %00000000 'clear WIN bits
' CanControlReg = CANCON
' CANCON = %00001000 'select TXbuffer0 WIN bits b3 hi, b2-b1 low
CANCON.3=1 ' set win bit to txbuffer 0
CanControlReg = CANCON
CanStatusReg = CANSTAT
PeripheralInterruptReg3=PIR3

if TXB0CON.3 = 0 then 'last message is clear (bit 3 is TXREQ)

DataBytesTx = 4 ' experiment with changing DLC
TXB0DLC = DataBytesTx
CanDataTx[0] = K
CanDataTx[1] = K+1 ' each byte has a different value
CanDataTx[2] = K+2
CanDataTx[3] = K+3
CanDataTx[4] = K+4
CanDataTx[5] = K+5
CanDataTx[6] = K+6
CanDataTx[7] = K+7
k=k+1

TXB0CON = %00000011 'tx highest priority
TXB0D0 = CanDataTx[0]
TXB0D1 = CanDataTx[1]
TXB0D2 = CanDataTx[2]
TXB0D3 = CanDataTx[3]
TXB0D4 = CanDataTx[4]
TXB0D5 = CanDataTx[5]
TXB0D6 = CanDataTx[6]
TXB0D7 = CanDataTx[7]


TXB0CON = %00001011 'request a send highest priority
TREQ = TXB0CON.3



PeripheralInterruptReg3=PIR3
endif


CANCON.3=0 ' set win bit back to default rxbuffer 0
CanControlReg = CANCON
CanStatusReg = CANSTAT

'TXB0CON.3 = 0 'clear txreq - for test purposes only

gosub blink
Goto main
'************************************************* ******************************
'************************************************* ******************************
'************************************************* ******************************
'************************************************* ******************************
'************************************************* ******************************

End

'************************************************* ***************************




Blink:

high portb.0
pause 100
low portb.0
pause 150
return

[inse]

Hi Tim,

I had a look at your code and noticed two things:

one major bug:
TRISB = %00000010 'Set portb.2 output (cantx) ,b.2 input (canrx) 18F248/4580
should read TRISB = %000001000 "setportb.2 output, portb.3 input

and one thing I don't understand:
CANCON.3=1 ' set win bit to txbuffer 0
what's this exactly good for, do you really need it?

I didn't check your BRG settings, but if you set up transmitter and sender the same, it should work anyway :-)

Regards,
Ingo

[Timmoore]

Hi Ingo,

Well spotted on the major bug . I dont know how many times I checked that - obviously not looking properly - either I was misled by the bogus bus activity which convinced me the output pin was correctly configured , and / or was counting the bits from 1 rather than zero - whatever the reason - a rookie error.

SO, it is all working beautifully now ! I have eight bytes being sent and received, I have tested the code running on 2 x 18F248, 1 x 18F248 and 1 x 18F4580 and finally 2 x 18F4580. All running nicely.

Glad my understanding of the workings of the registers is validated but have a red face for not checking the TRISB setting.

Thanks Ingo - I would rather have a red face AND working code than the other way around.

CANCON.3=1, you are probably correct, this may not be necesary for the simple test program. see page 276 of the 4580 datsheet. bits 3,2 and 1 are called WIN bits, which set the particular transmit or receive buffer . Code 100 sets tx buffer0. I suspect I may have to set these bits depending on the tx buffer I wish to use, equally on the rx side I can use these to place data in a particular rx buffer. I think there may be a degree of automation to this process but have yet to play with the system to fully understand the workings.

Now I must stop calling it the CANT bus and give its real name CAN bus !

Got some work to do now, adding data transfer functionality and structuring code.



Thanks again - Once done, I will send you a copy of my working system if you PM me or provide an e mail address.

[zx81sp]

I've post in PBP pro but nobody seems to know, so let me post here since is a CanBus question:

I've a small proto board (without datasheet) connected to a Can network and I'm trying to make a very simple app but I don't know how to do. It has a 18F258 (20Mhz clock) and MC2551 and I want just send a CAN command, nothing else. I know that the bus works at 100k, can anybody help me? just a help to start, I'm using now a CanUSB adapter with a PC but I want to use something lighter.

I've read the code above but sincerily, I don't understand it.

Regards