Dear all
I worked with flowcode V4 many times on PIC18F4550 and it's worked fine, I bought a bluetooth solution with PIC16F1937; the kits pre-programmed with a testing program and it's worked
I tried to developed my own application but nothing worked, I tried to download the test files and project included on the CD and nothing worked; I can found the bluetooth device but the LCD not display any things;
after that I tried to make a simple program that worked with LCD only - as a test- but the LCD display a random number and I tried all the possible configuration, the LCD worked on the internal OSC=500Khz but the problem that I need to operate the solution using the 19.6608M crystal to work with the CD examples
when I use the HS configuration I got the following caution
Caution: argument of 'delay_us' calls must have a value of 1 or more
Caution: Delay inaccurrate: 'delay_us', Delay overhead:0ms, Unit delay:0.00101725ms, Delay resolution:1 units
Caution: Delay inaccurrate: 'delay_10us', Delay overhead:0ms, Unit delay:0.0101725ms, Delay resolution:1 units
Caution: Delay inaccurrate: 'delay_ms', Delay overhead:0ms, Unit delay:1.00016ms, Delay resolution:1 units
the delay values =0 !!!!!!!
can anyone have an idea or suggestions ??
Regards
flowcode- LCD problem with bluetooth solution
flowcode- LCD problem with bluetooth solution
- Attachments
-
- lcd_test.fcf
- my test file - LCD and flashing leds
- (7.5 KiB) Downloaded 334 times
-
- BLUETOOTH_TEST.FCF
- the original test file
- (18.24 KiB) Downloaded 332 times
Last edited by sami_asd on Thu Apr 04, 2013 1:48 pm, edited 1 time in total.
Re: flowcode- LCD problem with bluetooth solution
Hi
Please can you attach your flowcode progam as it will help people to help you, also please only post once as theres no need to post the same post twice,ive deleted your other post
Regards
Dazz
Please can you attach your flowcode progam as it will help people to help you, also please only post once as theres no need to post the same post twice,ive deleted your other post
Regards
Dazz
To sign up to the V5 forum follow this link http://www.matrixmultimedia.com/forum_upgrades.php
Re: flowcode- LCD problem with bluetooth solution
thank dazz
I attached the test file and my own program
I attached the test file and my own program
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: flowcode- LCD problem with bluetooth solution
Hello,
The RC / XTAL switch on the EB006 can sometimes be slightly temperamental. Try sliding it into the RC position and then back again to see if this allows your programs to function correctly.
The RC / XTAL switch on the EB006 can sometimes be slightly temperamental. Try sliding it into the RC position and then back again to see if this allows your programs to function correctly.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: flowcode- LCD problem with bluetooth solution
for my test file
the flashing led work fine with 19.6608 HS but the LCD not
when I config to work on RC or internal osc the LCD work fine
the flashing led work fine with 19.6608 HS but the LCD not
when I config to work on RC or internal osc the LCD work fine
Re: flowcode- LCD problem with bluetooth solution
I have the solution for the LCD module "thanks for Mr. David A"
he send me the correct way to change the LCD code and it's worked now --> change MX_CLK_SPEED >= 32000000 to MX_CLK_SPEED >= 16000000 in the definition macro
but the bluetooth not worked till now and i think the same problem appear--> the problem in the OSC (19.6608M)
any suggestions ???
he send me the correct way to change the LCD code and it's worked now --> change MX_CLK_SPEED >= 32000000 to MX_CLK_SPEED >= 16000000 in the definition macro
but the bluetooth not worked till now and i think the same problem appear--> the problem in the OSC (19.6608M)
any suggestions ???