Page 1 of 1
Possibly Busted Eblock
Posted: Wed Feb 19, 2014 5:35 pm
by marcbernz
Hi,
I have been working on the e blocks bluetooth board as an upgrade to the formula flowcode buggy. I have ordered 2 Eblocks the Bluetooth Board(EB0124) and the LCD Board(EB005). The LCD board is working just fine, its the bluetooth that bothers mi. The led of the bluetooth won't light nor powers on after it is already supplied. When both are connected (Bluetooth and LCD), only the lcd displays and the bluetooth wont initialize. The pogram I am using is the one that can be dowloaded in the Matrix Multimedia website.
Is it possible that the bluetooth is busted?
Attach is a pic of how we connected the bluetooth.
https://www.dropbox.com/s/zyk7a1ktrj6a9 ... .36.26.jpg
Marc
Re: Possibly Busted Eblock
Posted: Wed Feb 19, 2014 6:29 pm
by Benj
Hello Marc,
The LED on the Bluetooth E-block only comes on when the Bluetooth is paired.
Can you attach your program so I can have a look and see if I can spot anything, the demo file will be using the hardware UART, you will need to change this to instead use the software UART on pins RD6 and RD7.
Re: Possibly Busted Eblock
Posted: Wed Feb 19, 2014 6:37 pm
by marcbernz
Re: Possibly Busted Eblock
Posted: Wed Feb 19, 2014 6:49 pm
by Benj
Hello,
Right the Bluetooth component in v5 doesn't expose the software mode so you can either do what I have done and hard code it in via the custom code option or you can use the RS232 component.
In the attached file I have fixed the UART to software mode on pins RD6 and RD7 so hopefully it will start working for you now and be discoverable.
Example of the C code mods I made to the Defines section of component code.
Code: Select all
#ifndef MX_UART_REF1
#ifndef %a_MX_UART_UREF
#define MX_UART_REF1
#define %a_MX_UART_UREF 1
#define MX_UART_CHANNEL_1 0//%b
#define MX_UART_TX_PIN_1 6
#define MX_UART_TX_PORT_1 portd
#define MX_UART_TX_TRIS_1 trisd
#define MX_UART_RX_PIN_1 7
#define MX_UART_RX_PORT_1 portd
#define MX_UART_RX_TRIS_1 trisd
Let me know how your getting on.
Re: Possibly Busted Eblock
Posted: Wed Feb 19, 2014 7:05 pm
by marcbernz
Thanks benj, this is really a life saver.
Will try this out.
Re: Possibly Busted Eblock
Posted: Thu Feb 20, 2014 5:53 am
by marcbernz
Hello Benj,
I tried the program and still no luck. I can't detect the device nor it has initialized.
I have set up the Bluetooth board together with the LCD just to see if it has initailize. But still no luck.
I have attached a picture of how I I had set it up.
https://www.dropbox.com/s/l3bm8k7sakz3q ... .50.18.jpg
Re: Possibly Busted Eblock
Posted: Thu Feb 20, 2014 10:17 am
by Benj
Hello Marc,
The E-blocks won't work in this configuration, the Female D-type socket on the Bluetooth board is for an audio codec. You will need an E-blocks splitter cable to allow you to connect both boards directly to the D-type on the formula flowcode.
Re: Possibly Busted Eblock
Posted: Thu Feb 20, 2014 3:54 pm
by marcbernz
Hi Benj,
Is it okay if I make my own? The Eblocks splitter cable is not available here.
Will the program that you have attached work without the LCD board? Because I tried having the bluetooth board only and I can't detect it nor make a pairing on a device. Is there a need to insert an address to the program? If there is, where should I insert it and how?
Thanks.
Marc
Re: Possibly Busted Eblock
Posted: Thu Feb 20, 2014 8:04 pm
by JohnCrow
Re: Possibly Busted Eblock
Posted: Fri Feb 21, 2014 1:33 am
by marcbernz
Hello John,
What I meant was the cable is not available here in my country. It would take weeks to arrive if I order the cable.
