RS232 and Bit/Byte Maping Questions

[RatherBeFlying]

Please excuse me if these are a newbie questions, matter of a fact, I am that to PIC and CCS, also excuse different topics, I just put all my questions rather than keep asking questions in different posts.

1) I understood from #Bit & #Byte that I can map a variable to an I/O pin (a bit of a port) and this will allow me to change the output to high/low just by making it = 0 or = 1 without having to use Output_High(PIN) or Output_Low(PIN), I am unable to do that unless my understanding it wrong about #bit or #Byte.

2) By testing, it seems the #int_RDA to interrupt when a byte received from RS232 only interrupt on hardware UART. How can we enable this for Software UART (which was setup using the #use rs232(�.) and defining other pins than the HW one.

3) All RS232 related functions such as getc, printf and such can have a stream option, how can I use the kbhit() to test a specific stream for incoming byte, I couldn�t find a stream option in the manual for kbhit(). Note for questions 2 and 3, waiting forever using fgetc wouldn�t be possible as the PIC needs to do other stuff, so either an interrupt or a separate task, but I understand that CCS is not supported for PIC Salvo RTOS

4) I setup a MAX232CPE with the proper Caps to communicate with an RS232 device which uses RS232 Voltage Level. Its not a PC, I thought I would be able to use any I/O pins from the PIC side as I provided a MAX232 circuit for level conversion, however it only work with the HW Pins (PIN_C6,PIN_C7) and the device wont work correctly with any other pins, of course it wont work correctly with HW if I removed the MAX232 circuit.

Thanx for any help

[SherpaDoug]

1) For port mapping look at the help file "Common questions and answers" under the topic "How does one map a variable to an I/O port?"

2) I don't think you can use interrupts at all with a software UART. Use polling with kbhit().

3) Pass the stream name as an argument.
if (kbhit(compass)) {...

4) With a software UART you should be able to use any "normal" I/O pins. Beware some pins have odd characteristics. It is useful to have a scope here, but if you run at a very slow baud rate (like 300 or 10) you can see a lot with a logic probe.
_________________
The search for better is endless. Instead simply find very good and get the job done.

[RatherBeFlying]

Thanx SherpaDoug for prompt reply

Reg. the manual and bit/byte map, that what i refered to when i said it was not working! it should work, but i have no idea why it is not. Simple example just like the manual, pin connected to LED (with resistor 1K), using Output_high/low, LED goes on and off, but using #bit for that pin number and = 1 and = 0, nothing happens!

Thanx for the tip about kbhit. I thought it should do that but i didnt actually try it as the manual did not show Kbhit(stream).

I agree about the scope, going to try to get a PC scope as those seems to be cheaper than a normal scope. I am using 9600 baud. Its a PIC16F876A with 20Mh Crystal, MAX232CPE with 5 x 1uF 100V, dont think the 100V rating for the Caps will do any harm compared to the 25V Caps normally used for MAX232.

Thanx again SherpaDoug

[rwyoung]

[Neutone]

Look at the standard and fast IO options.

[SherpaDoug]

Port mapping has always just worked for me. Double check you have the TRIS register set properly.

If you have an idea what you want look at scopes on EBAY. You should be able to get something that will do for under US$100. A TEK 453 is a scope no atom bomb can kill (fully transistorized!).
_________________
The search for better is endless. Instead simply find very good and get the job done.

[Guest]

I have to admit that the MAX232 issue sounds strange, yeah, pins used are I/O pins that do not have any secondary functions and are not open drain outputs. when using pins other than the HW UART, no results at all! not even wrong results. just dead lines. I think the scope would give more insight.

Will try the Fast_IO again, but i was more focused on the MAX232 issue that i didnt spend enough time debugging the BIT/Byte issue.

Thanx all for the replies.