I'm not a beginner at both, is only microblock that I just started using. And is not just me working on the project. We have just few days to wrap up.I have attached a video of what happens.
And please i don't mind working on the two platforms. Thanks.
It is using the same service
Hello, I'm still unable to solve this problem
Sorry, I lost track of what you are trying to do and whether you want to continue with the microblocks from Peter. If you just want to stay with makecode and .hex files, please attach your latest .aia and .hex
(btw. there was a problem with the BLE extension and the latest Java release, a temporary fix is here: Crash with BluetoothLE and micro:bit on Android 14 - #7 by extremerotary
We are not going with the microblock.
Then, attach your latest .aia and .hex so that I can take a look.
Hi,
There is no way I can see what is wrong with your communication issues if I do not have the AppInventor side of the communication, therefore:
To export an aia from your Project to your computer
Choose File | Export Project to export the source code (blocks) for your project. The source code is downloaded in an .aia file.
Then, upload that .aia here.
What are you trying to do? Connecting to a micro:bit as if it were an ESPxx??
That cannot work. If you really want to learn how to connect to a micro:bit, do this tutorial: The Internet of Things: Data Acquisition and Analysis
Try the easy communication as exaplained in this tutorial, then look at your .aia again, and realize that it cannot work. There is no easy way for me to repair it.
I was wondering about your .hex file too. You are never sending anything to your app, except for the first test message, how is it supposed to work?
I am trying to get the Device to pick up the message sent from the Micro:Bit as even though the Micro:Bit is sending the message I don't understand how to make my app receive that same message. The Micro:Bit is connecting to the Bluetooth.
That is what I am trying to tell you: your app inventor app is not capable to receive micro:bit messages. Do the tutorial I pointed you to!! It contains an example that exactly does what you want.
I did a quick version with the MicroBlocks extension.
Used only the images from the topic to work from.
This is the MicroBlocks code on the micro:bit
This is the App Inventor code
microbit_messages.aia (225.9 KB)
sendmessageappinventor.txt (4.8 KB)
Rename the txt file to ubp to be able to load it in MicroBlocks.
Interesting!
I hope it is not too confusing Elleanda!
@Elleanda This is also a route you can take, but it requires a new investment in learning.
Yes, that is also what I was thinking. But I think the MicroBlocks route is much simpler for a lot of users I see here on the community wanting to use BLE, that is why I offered an alternative way.
Hi @Elleanda if you want to continue with Peters' approach, that is fine with me, but depending on why you are making this project, it may not be what you want. Therefore some tips:
First, in the .hex, go to project settings (click on the little round weel at the top right)and set "no pairing required". This will save you a lot of grief. Reload the .hex on your micro:bit.
Then, here is my latest UART app, it is almost what you need, you have to add the name stuff and you may not want the temperature stuff.
BTReadWrite4_strings.aia (296.9 KB)
Then,you could update your BluetoothLE extension, by downloading the latest .aix file here:
Update the extensionby importing it (it will overwrite the old one), but maybe, if you do not have the super latest Android on your phone, you may not need to do that,
Let us know how you go.
Thank you @Ghica and @Peter
I found a way to fix my problem as It seems that I had a unnecessary block that was disrupting my code therefor it wasn't picking up the message.
Here is my final code
microbit-20241120-quickchat---Trying-to-get-BT-working---Copy.hex (1.3 MB)
QuickChatTest.aia (307.4 KB)
Yes, I saw that block. However, your latest .aia and .hex do not work. One reason is I cannot connect to my microbit, you really need to set ‘no pairing’ in your .hex project, and on the app inventor side you need to stop scanning and not stop advertising. Furthermore, there is the BT client and the ESP stuff. Maybe harmless, in any case ugly.
I wanted to repair your project, but something in your code really upsets my companion. I do not have time the next few days.
That's ok, thank you for your help
