This seems to be done on Nodered or a similar platform.
Let me take a better look and we'll see it come out.
Ok...
- I translated the page completely, and explicitly in this link, it says that:
Detailed list
- Download MakeApp from PlayStore and connect the device you purchased (BLE + VBR)
- Then test your device from the app (it will show it to you on the screen)
- There's a video showing how to do it.
- Customize your app with Appinventor (you don't necessarily have to make it/create it):
What does that mean?
-
BLEB has many types of boards and devices for IOT, which can be used alone or combined.
-
In the jargon, that means that if you want to use a wide range of products or devices, you can literally create your own app, since they provide you not only with the hardware, but also with the software and the interface (which in this case is an extension for Appinventor).
-
In the same link (section: Appinventor, as there is also Node-Red and web). They say that "For those who are interested, they have demo App's and documentation" to which they only have to contact them to acquire it.
-
And that documentation and demo App's it's what we need to know what kind and type of parameters send and/or receive. Because we need to know how the software and hardware work, in order to create the middleware correctly (Set parameters).
In this world (programming)... Everything is documentation.
- I also took the job of creating an App that I "think" works (due to the lack of documentation regarding BLE and VBR).
The App
-
The gui is the simplest thing that exists, it has no format, colors, etc. because it is designed to test if it works or not.
-
As you will see, it is only 6 sliders and 6 labels (and their layouts), as it is what allows you to configure the VBR from the extension.
-
Obviously it has its components not visible (Notification, BLE, VBR and the basics).
-
As for the logical part (programming in blocks), I did it in the most orderly and legible (but also fast and scalable) way possible, so that it is completely understandable.
-
Could we do better? Yes, obviously, we have a full range of tools and ways to achieve this, But for now we must see if it works.
-
You should not forget that when you open the project (AiA), you must make sure that the extension (AiX) is loaded, otherwise... Import it.
-
The components of the extension that are necessary are those that are in the red box.
- Here's the project and extension, so you can CHECK out.
Details to take into account before even compiling the App
-
Remember that first you must download the App from the PlayStore, pair the device you purchased (via bluettoth).
-
Get the missing documentation, to be able to set the parameters that must be sent/received from the device.
-
Otherwise, the device is likely to break.
Ardof.aia (520.9 KB)
I look forward to comments, criticisms, questions, opinions, and input, as well as peer review.
- Thank you, I found it helpful.
- A drugged monkey would have done better.
0
voters
It is surprising that the company does not present this extension itself on App Inventor and thus automatically refer to and promote its corresponding products (associated with the extension).
(A possible language barrier should hardly be a problem here.)
1 Like
Hi Jonathan, good morning. I tried the program you sent to me last night but it seems that something is going wrong. Just after I make the connection to the Companion I get the following screen: I am sorry but I don't know how to enclose a picture to this message
Basically, no one (neither a normal user nor a power user) should post an extension here that he/she did not create himself/herself. Reference should always be made to the relevant extension via a link.
If there is explicit permission from the developer, reference should be made to it.
1 Like
Dear Anke, it seems to me that I made something wrong. If that the is the case I apologize I made this because I a not familiar with this kin of forums. I'll never dio it again, I promise
1 Like
anyway he alarm I get is the following: Error 908:The permission BLUETOOTH_CONNECT has been denied. Please enable it in the Settings app.
1 Like
I dont think so, it's just; select text>right click>translate.
My fault, sorry, i didn't know.
In the Asker procedure, change Bluetooth_connect text by BLUETOOTH_CONNECT, same for others permissions.
Then Compile the Apk Again.
What do you mean? writing Bluetooth-connect in capital letters?
1 Like
These are the correct permission names (as strings). But you can also use the helper blocks (as I inconsistently did with ACCESS_FINE_LOCATION.)
1 Like
Thank you for your help Anke, But I don't understand how I can solve the problem. Probably I am more stupid than what I think.
1 Like
Where is the problem using my blocks?
1 Like
the problem is that I don't understand which are your blocks to be used
At some point the app asked you for access to Bluetooth???
(And I imagine you clicked "Yes" or "Accept")... Don't you???
Because if you don't give it permission to access Bluetooth, it will never connect via Bluetooth.
It seems that the extension does not request these permissions automatically (at least not on Android 12+).
1 Like
In addition, it seems that the extension does not declare these permissions in the Manifest. Permissions can only be requested if they are declared in the Manifest.
1 Like
... so add the AI2 BLE extension, which declares these permissions in the Manifest.
1 Like