EX_RS485.c CCS C [Solved]

[diode_blade]

Main Hardware: 2 Mikroe Easypic v7 Boards: no Glcd's/LCD's Plugged into either board

PROC: 18f46K22 both boards
Using MPLAB 8.92 with the ICD 3 on one laptop
and PCWH with ICD U80 on other laptop
Compiler version used on both 5.093

1 - Microchip ICD3 Plugged into board 1 for debugging etc
1 - CCS ICD U80 Plugged into board 2 " " "
2 - RS 485 Click boards plugged into the mikro bus socket 1 on each board (mikro-989 5V version) 1 board has the bias in place, the other not, both boards with termination jumpers left in place

2 - laptops 1 conected to each debugger for each board






















using the USB UART I/F conection on each V7 board for the RS232 to laptop

Confirmed I can comunicate with both laptops to each board through the RS 232

Here are changes made to 1st EX_RS485.c

[Ttelmah]

The RS485 'turn round'. The signal that controls whether a board is
transmitting/receiving, is the R/T pin on the board you have. This
needs to be controlled by the RS485_ENABLE_PIN.
Without this either both boards will be receiving or both transmitting.
RS485, is half duplex. It must have the turnround.....
It is pin 16 on the connector. Marked as PWM.

[diode_blade]

Thanks Ttelmah,
I have assigned (well think I have) that pin already to in the RS485.c file to the correct PWM on the Mikrobus socket I am using on the V7 board.
Regards
dave

[temtronic]

curious question....

i see you have used....
#include "18F46K22.h"

but the EasyPIC boards come with the 18F45K22( I downloaded the datasheet)

did you upgrade the PICs to 46k22 ??
If not, you may have 'problems' later on with more complicated programs that need more memory.

[diode_blade]

[temtronic]

good to hear... it's my 'Swiss Army Knife' PIC !!! I've yet to run out of memory or pins, got real close last year though....1 spare pin !
I dedicate ICSP pins for, well, ICSP......saves a few headaches .
it would be nice to find a 'protoboard' with good layout for smaller projects, especially 'proof of concept' projects that need real world testing.

[diode_blade]

I have used the Mikroe "Ready for PIC" boards. They do a 28 pin and 40 pin for small projects I have done before. It has a small prototyping area to one side, as well as access to ISCP pins and a USB Uart.

[Ttelmah]

Obvious one thing not said. You need to be enabling INT_RDA2, not INT_RDA.
Another change needed in rs485.c

Now, thinking about it, if I remember correctly the K22, has the ICSP pins on
the UART2 pins. You talk about using the IDE, which suggests a possible
clash?.

Then there is another potential issue. The internal #USE RS232 lines
default to being loaded in rs485.c - Have you removed these?. If so
double check, since there are two sets of these.

[diode_blade]

[Ttelmah]

I Think what I would do, is not edit rs485.c, but instead setup your
own 'version', that has your own initialisation, and then copy and paste
the functions across, checking each once for 'port specific' code as I went.
Much more likely to work...

[temtronic]

Mr T brings up a very important point..
always...
ALWAYS...
copy and rename drivers BEFORE you edit them !!!
NEVER,EVER modify the original CCS or other supplied drivers.
I can't stress that enough

Mind you IF you want to lose a lot of hair and several nights of sleep..just make 2 or 3 'simple' changes to a driver at the same time at the end of a marathon coding session.....

Jay

[diode_blade]

Thanks for the tips guys, after having a few days away from it, am going to try again. Yes I do make copies of the driver/header files i use for each project, they have their own directory.
So I am going to strip right back and just try to do the basics first.
Thanks
dave

[Ttelmah]

I was actually trying to suggest going 'slightly further'.
The point is that what you are doing is much more fundamental than
just a mod to the file. You need different initialisations, different interrupt
enables and usage, etc. etc..
So I'd be looking at building rs232com2.c, and actually copying the routines
from the code example, modifying each one as it is brought across.

[diode_blade]

Right first of all a big big thank you Ttelmah and temtronic.
I did as suggested stripped everything back, just did simple code. I have both RS485 and RS232 working. Ok even with the 485 it's just point to point, but it's a working start. Both using hardware UART/UART2 respectively on each V7 board along with their RS485 click boards. I can talk to both boards from laptops and see RS485 data I send (just a count figure).
Using serial buffered routines as in ISR_SISR example for both Int_RDA and INT_RDA2.
So thanks gents, really appreciate it.

[Ttelmah]

Well done.