Page 1 of 1
Connecting bluetooth and lcd eblocks to a PCB
Posted: Thu Mar 17, 2011 1:53 pm
by stephenmccarthy
Hi guys,
I'm using an 18f448 to calculates a BPM value and send it to the LCD and then to hyperterminal via bluetooth.
Everything works pretty well on eblocks,
So my problem now is when I put my 18f448 on the breadboard and power it. Connect the appropiate pins to a female serial ports that I wired myself and then connect this to the bluetooth eblock and LCD eblock. I cannot get anything from the lcd eblock or the bluetooth eblock will now not connect to hyperterm.
Ive only just tried this and this is the result,
So what I plan on trying next is putting a max232 between the micro and the female serial ports,
Do ye think this will correct the problem?
Thanks
Stephen
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Thu Mar 17, 2011 4:36 pm
by Jan Lichtenbelt
Dear Stephen
Did you connect the power to the LCD and bluetooth blocks?
Regards
Jan
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Thu Mar 17, 2011 5:01 pm
by Benj
Hello Stephen,
Do you have a LED or something similar that you can flash to ensure the chip is running. Could be that the oscillator circuit or something else fundemental is not working and this is causing everything else to fail. Once you know your chip is running at the correct speed etc then you can start to troubleshoot the peripherals one at a time until you get to the source of the problem.
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Fri Mar 18, 2011 12:04 pm
by stephenmccarthy
Hi guys,
Hi Jan. Yes, I've ran 13.5 volts to my breadboard from a psu and passed this to the de7805 regulator, i have the micro powered by this and also connected both eblocks to this power. The bluetooth dongle will acknowledge a com port to the bluetooth eblock when it is powered but will not connect it to hyperterm. As for the LED it is powered but the screen will not print.
Hi Ben, yes I have actually just used an LED to check the power is getting to the termianls, and i will now try the led test you recommended on another thread to me, I will let ye know how this goes.
Thanks for both replies!
Stephen
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Fri Mar 18, 2011 4:51 pm
by stephenmccarthy
Hi lads,
I solved the problem, it was that I tought the 18f448 had an internal crystal also i did not use the pull up resistor or tie mclr to high, so I adjusted my code to allow me use an external crystal, I know have a 12Mhz crystal tied to pin 13 and 14. Now both my LCD and Bluetooth work with the micro on breadboards. The only problem to this is I am not sure how to adjust the clock speeds on flowcode to have everything working in sync again?
Regards
Stephen
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Wed Mar 23, 2011 6:40 pm
by Benj
Hello,
Clock speed setting is adjusted in the View -> Project options menu. If Bluetooth is working then the baud rate is being calculated correctly which means your clock speed is already probably correct.
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Thu Mar 24, 2011 10:47 am
by stephenmccarthy
Hi Ben,
I adjusted the clock speed to 12000000 and i can connect to hyperterm but now it will not print messages or values? any idea where i might have gone wrong?
I have not looked at flowcode in a few days because I have been designing the PCB for the micro and sensor. Is there any other setting beside the config and clock speed i might need to alter?
Thanks
Stephen
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Fri Mar 25, 2011 12:49 pm
by Benj
Hi Stephen,
Have you seen the Bluetooth manual and examples available from here.
http://www.matrixmultimedia.com/lc_bundle_manuals.php
They should show you how to get up and running.
Re: Connecting bluetooth and lcd eblocks to a PCB
Posted: Fri Mar 25, 2011 2:09 pm
by stephenmccarthy
Hi Ben,
I have actually went through the recommended documents thoroughly. So i was quite confused with the problem, however it seems that i have to occasionally reprogram the Bluetooth module on the multiprogrammer again with the example 1 program. Then reprogram it with my project program for it too work. I'm not quite sure why I have to do this? I'm assuming it might have something to do with the volatile memory you mentioned to me on another thread?
Thanks again,
Stephen