I2C lcd ( arduino ) with PICBASIC, help

[EarlyBird2]

Steve,
I am sorry for the delayed reply : I am not at home on those days.
I had a look to your code : it is a good work and I am waiting to check it soon when the hardware is arrived .
Thanks a lot for the assistance.
I think your work will help a lot of people .
Regards,
Ambrogio

You are welcome. More is on the way as I am now investigating embedded strings.

[EarlyBird2]

I tried using the on board EEPROM by using DATA and READ.

DATA "This is a string",0

but it stores only alternate characters. I was surprised it worked at all but the alternate characters? There has to be a reason for it to work this way.

[EarlyBird2]

I tried using the on board EEPROM by using DATA and READ.

DATA "This is a string",0

but it stores only alternate characters. I was surprised it worked at all but the alternate characters? There has to be a reason for it to work this way.

It looks like this was fixed back in 2010.

http://www.picbasic.co.uk/forum/showthread.php?t=12775

My PBP2.46 is from 2005.

[EarlyBird2]

It looks like this was fixed back in 2010.

http://www.picbasic.co.uk/forum/showthread.php?t=12775

My PBP2.46 is from 2005.

The plot thickens! Here is an extract from this thread http://www.picbasic.co.uk/forum/show...7143#post97143 using DATA with strings and it works.

EUREKA!
Thanks guys! You have been a huge help. I have finally figured it out.
My problem was more like 3 problems...

1. I have never done EEPROM stuff before so I was lost to begin with.
2. As Bruce pointed out, the mathematical order of operations in one line was not correct. I guess the BS2 thinks a little differently from PBP in that respect.
3. My PicBasic Pro compiler was Version 2.30 form 2000. It seems that v2.30 supports the PIC 16F628 but the PIC 16F628A was implemented in a later version. I have upgraded my PBP to version 2.47 and now the EEPROM features work correctly on the 16F628A. When I successfully tested a 16F84A using the same code, that lead me to question the compiler.

So for future generations and the benefit of other people like me, here's my WORKING code that is tested successfully on a PIC 16F628A with a 20MHz resonator compiled using PBP v2.47. It reads data from the Parallax RFID Reader Module, compares it against known values stored in EEPROM and allows or denies access accordingly. Enjoy.

CMCON = 7   
DEFINE OSC 20	'Set oscillator in MHz

' -----[ Variables ]-------------------------------------------------------

buf	VAR	Byte(10)	' RFID bytes buffer
tagNum	VAR	Byte	' from EEPROM table
idx	VAR	Byte	' tag byte index
char	VAR	Byte	' character from table

' -----[ EEPROM Data ]-----------------------------------------------------

Tag1	DATA	"100050A4B7"
Tag2	DATA	"1000508E0A"
Tag3	DATA	"10005091DC"
Tag4	DATA	"100050203A"
Tag5	DATA	"100050DA36"

' -----[ Initialization ]--------------------------------------------------

HIGH portb.3	' turn off RFID reader
LOW portb.6	' lock the door!
Low portb.4	'Turn off LED

' -----[ Program Code ]----------------------------------------------------

Main:

LOW portb.3				' activate the reader
SERIN2 portb.2, 396, [WAIT($0A), STR buf\10]	' wait for hdr + ID
HIGH portb.3				' deactivate reader

Check_List:
  FOR tagNum = 1 to 5			' scan through known tags
    FOR idx = 0 TO 9				' scan bytes in tag
    READ (((tagNum-1) * 10) + idx), char		' get tag data from table
    IF (char <> buf(idx)) THEN Bad_Char		' compare tag to table
    NEXT
    GOTO Tag_Found				' all bytes match!
Bad_Char:					' try next tag
  NEXT

Bad_Tag:
  tagNum = 0
  FREQOUT portb.5, 1000 */ $100, 115 */ $100	' groan
  PAUSE 1000
  GOTO Main

Tag_Found:
  HIGH portb.6				' remove latch
  High portb.4				' Light LED
  FREQOUT portb.5, 2000 */ $100, 880 */$100	' beep
  LOW portb.6				' restore latch
  Low portb.4				' LED OFF
  GOTO Main

[EarlyBird2]

Ambrogio

After more testing of the DATA command I have come to the conclusion that my very old setup is the cause. I have PBP2.46 and MCSP from ten years ago. Looking at my old code, ten years old, I used WRITE not DATA and I now believe that was because DATA never worked. I wrote a routine just to write to the EEPROM followed by the program fortunately my set up did not overwrite the EEPROM when the PIC was reprogramed, Bruce's FlashLab boards continue to perform flawlessly.

There are three options for the screen setup

1 LOOKUP
2 Embedded string
3 EEPROM

They all work but LOOKUP uses most code space and EEPROM the least.

[iw2fvo]

Steve,
I am very interested in test the programs but I am still waiting to receive the PCF expander.
It will arrive here after my summer holidays. I will let you know.
Thanks for all.
Regards,
Ambrogio

[Wirecut]

Ciao Ambrogio,

take a look here ... could help!

http://www.protonbasic.co.uk/showthr...ck-on-1602-LCD

Leo