BLE NANO 33 SENSE Rev2 RegisterForByte crash

MIT App Inventor Help
21

That's not nice - wish you a swift recovery.

Just use my "_edit" version of your App as-is.

22

Okay i tried that... this is what i get:

Screenshot_20240829_1458151
Screenshot_20240829_14581511080×2340 113 KB

Bluetooth is indeed turned on :wink:
But maybe there's something somewhere telling the app that it isnt - i cant rule that out.

23

Oh hey Chris.
Check out ewpatton answer here:

Im using this BLE extension version: 20230728

I think i better try the 20240822 version

24

Yes! Try it with the _edit file - you just have to install it, everything will update.

25

Dang.. I really thought we had it there.
I tried it on your BLE_Controller and my own program and both still crash when they connect.

26

Can you upload your Arduino Sketch (.ino file)

27

Here it is
BLE_Uint32.ino (2.2 KB)

28

Make sure this isn't an issue too:

29

Hmm everything to work perfectly on my board, the only thing that isnt working is on the app side whenever the RegisterForByte/Integer/float block is called.

30

That's good.

31

When was the last time you updated the Arduino Boards Manager? There are often updates for the 33 Sense.

Edit: Mbed OS Nano Boards version should be 4.1.5

32

image
Seems ok :slight_smile:

33

I might try and build a new app from scratch instead of just "updating" the BLE extension.. maybe there could be an issue with updating the blocks when the extension is being updated. Bit far fetched but worth a shot i guess.

34

I wouldn't bother. If the registration is at fault, nothing will work for streaming but read should still work. I'm just going through your .ino and there are a few errors.

35

So try the _Edit App version with the latest BLE extension loaded, with this Sketch:

BLE_Nano33.ino (2.5 KB)

... I just swapped out the ino with the correct ino :upside_down_face:

36

the BLE_controller still crashes when RegisterForInteger is called, and the BLE_controller_edit opens up and writes the same thing as in the picture above

37

If RegisterForIntegers fails, we can use ReadIntegers instead:

BLE_controller_edit2.aia (203.7 KB)

38

hehe yeah that's been my backup solution, i was just hoping to get the notify functionality to work, but maybe it's time to move on :slight_smile:
edit: by the way i already have a version of my app where i use a clock to call the ReadInteger block and that works perfectly

39

We can also send C strings to the App - that has thus far been infallible. The Nano 33's have a bit of a checkered history, when first launched nobody could interface with them.

40

Yeah i think ill try C strings tomorrow and then if it's giving me trouble move on to ReadIntegers and see how that feels.
Ill let you know the result when i get it done :wink: