Why not just use DEBUG for transmit & DEBUGIN for receive?
These commands work 100% with a 4MHz oscillator up to 19200 bps, offer the same modifiers as SERIN2/SEROUT2, and produce much smaller code!
Why not just use DEBUG for transmit & DEBUGIN for receive?
These commands work 100% with a 4MHz oscillator up to 19200 bps, offer the same modifiers as SERIN2/SEROUT2, and produce much smaller code!
Bruce just cought me. These two commands would be the next step to suggest.
astanapane is struggling with the basics so I did not put him to code changes. Debug need DEFINES declared on top of the code.
Ioannis
Yes that's true,
i will focus at the moment to the basics and then i will try to your suggestions. In first place it is needed to understand the code itself. Then to get the datasheet from the RFID module and check everything in there step by step.
For your info the module ID-12 can be run at 9600 as from the datasheet. The boundrate code for that it seems to work on SERIN2 portb.1, 84. I tried to use the 16468 but didnt do anything.
Regards,
For the Serin2 the 84 is for True RS232 signal. The 16468 is for inverted signal as is the case with the ID-12.
I could not find in the manual where is the speed of the serial port.
Does it clearly state 9600? I found the part that says the signal is inverted and no driver is required.
Ioannis
ok,
I use the OEM 125Khz reader See http://www.picshop.nl/rfid.html
This Reader has a CP signal, Before the 10-byte is serial out, the CP signal will be High. Then I have 210ms time to readout the reader. The PIC in the application is a 16F887.
buf var byte (10) ' RFID bytes from tag
Main:
If PORTA.7 = 0 then Read_Tag ' CP signal of the OEM reader, read within 210 mS
' Here other program lines
Goto Main
' ----- [ GOSUB ] -----------------------------------------------------------
Read_Tag:
' Wait for Hex 02 . . .
serin2 PORTB.0, 84, [WAIT($02), str buf\10] ' Read 10 byte from ECO-125
return
Dear All,
thank you very much for your help. Ioannis helped me out to identify my mistakes on the code and he also gave me the right instructions in order to solve the problem.
i would like also to thanks, Joe, Bruce and Gevo for their support.
Please find attached pictures of my circuit.
now the next and most difficult part is to configure the code for GLCD use.
But i havent seen any library for GLCD. Some users in here have been working for many hours to built a standard code for GLCDs.
the problem is that there would be much better if a library were available from PIC BASIC.
i know and understand that will take place on the pic chip but in nowadays we all using more powerfull pic's.
Regards,
Leonardo
Bookmarks