aribes
About
- Username
- aribes
- Joined
- Visits
- 165
- Last Active
- Roles
- Member
Comments
-
@Eric said: @aribes said: 1) Isn't it a bug given that IMU_PLUS still uses acc/gyro to get the sensor orientation? https://mbientlab.com/community/discussion/2664/firmware-v1-4-2#latest Thanks, we had 1.4.1 ins…
-
(deleted post, moved content to original post for clarity)
-
Ok, I made it to work in some other way. The problem was that the eventListenerse must be removed if the connection resets while board is not initialized. As of the events, I managed to make the led blink red on disconnect. But looks like the eve…
-
@Eric said: Monitor the BT adapter to see what is going on at the Bluetooth level during connectAndSetup. You mean with hcidump? It sounds like the connection is still being flooded with sensor fusion data upon reconnect so you prob…
-
I have added the serialize code right after the connectAndSetup succeeds (inside its callback) and now I pass it as a second parameter as you said. Still, makes no difference when the process is killed (like when a sigkill is issued or when the r…
-
I think the best is to serialize the board right after a successful connection, but before setting any sensorfusion or whatever handler. Am I right? How can i use the mbl_mw_metawearboard_serialize call? I tried with the following code, but I …
-
@Eric said: Ok, I'll see what I can do with that script. Thank you On a side note, if the NodeJS app needs to crash / unexpectedly exit in order for this board to be put in the aforementioned limbo state, perhaps your main focus sho…
-
I found a list of HCI error codes in https://mynewt.apache.org/network/ble/ble_hs/ble_hs_return_codes/#return-codes-hci According to this, errors that I am getting so far are: 19 - Remote User Terminated Connection --> after a normal disconne…
-
The following code adds the sensor fusion configuration to my previously sent code. If you ctrl-c right after the "Configuring sensor fusion" message, it should enter in this "limbo state", that is, if you then re-run the code, it should not connect…
-
@Eric any update in this topic? Sometimes, in normal app functioning, I am getting a sudden disconnect with error code 8, then it tries to reconnect, gets an error code 19 and from then it cannot reconnect anymore. In this case, if I close the …
-
Looks like it is very important to wait for the disconnect before finishing the process. So I have added code to capture the stdin and using it to issue a mbl_mw_debug_disconnect command. Then in the disconnect handler, I trigger the process.exit(…
-
@josh said: Thanks for that information. I couldn't find any clear information about Unity when I searched the forums. I think many people would be interested in a guide to use these sensors with Unity. I'm glad to share what I've learned working…
-
@aribes said: Now it seems to work better. However, sometimes I encounter this error: Connecting to E2:3E:DD:94:99:5F [E2:3E:DD:94:99:5F] Disconnected (error code = 19) Device already discovered, reconnecting Timeout discovering Stopping disc…
-
@Eric said: The disconnect issue was patched in a C++ SDK update; the JavaScript SDK must still be referencing an earlier release. Maybe you will reference this message regarding my previous post. I manually updated the node_modules/metaw…
-
Now it seems to work better. However, sometimes I encounter this error: Connecting to E2:3E:DD:94:99:5F [E2:3E:DD:94:99:5F] Disconnected (error code = 19) Device already discovered, reconnecting Timeout discovering Stopping discover Device alrea…
-
I will ask the question in a simpler way: "How can I implement reconnection using the JavaScript SDK?" I modified the led.js example code to make a simple reconnect: var MetaWear = require('metawear'); MetaWear.discover(function (device) {…
-
If I try to update the javascript sdk using npm, it still uses (I think) the 0.11.4 version. If I try to install Javascript SDK from git+https, I get an error when it tries to download the submodule. I downloaded from git the latest JavaScript SDK…
-
@Eric said: Use discoverAll and stopDiscoverAll https://github.com/noble/noble-device#discovery-api The problem is not only with discover, but with connect. Sometimes the device disconnects after trying to connect using connectAndSetup…
-
In fact, the device is discovered, but it is the connectAndSetUp function that "hangs" without any disconnect, error, timeout.
-
I would like to know if, inside the nodejs app I can reconnect in some way. That is, when I call discoverByAddress, after a timeout I was doing a process.exit(-1), but now I would like that the same process cancels in some way the discoverByAddress …
-
It is due to the architecture I am using. The design of one process per sensor is because I have a sensor manager process that scans for sensors and manages connections. In python it was better to have separated processes because I can use better th…
-
No, each process uses the same HCI device. In fact, I realized that maximum two processes can access to the same HCI interface, the third one starts giving problems. I guess it is a limitation of the noble library and/or any of the underlying sys…
-
Ok, I have found something more. I tried with the multi_devices example, putting 4 devices and it connects to all 4. Then, I basically took the same code but this time the address (only one) to connect to comes from command line. If I start 4 proc…
-
What about the devices becoming frozen?
-
I added a process.exit(-1) when a disconnect is received or a maximum timeout is exceeded (using setTimeout and checking a global variable that indicates if it is connected). However, sometimes I encounter that the device takes too long to connect…
-
Do you mean add it manually using Noble api? MetaWear is using it on background, so I don't know where to start from. Any idea about how to implement that?
-
Ok, then even though I cannot get an image, could you provide me with the versions of the critical packages? I guess kernel and bluez versions should suffice, but maybe there are other packages that play a role into the problems I am experiencing.
-
By the way, could you provide me with info of what versions of what packages are shipped in the SensorHub? Could I get a downloadable image of it?
-
apt-cache show bluez gives this output Package: bluez Version: 5.43-2+deb9u1 Architecture: armhf Maintainer: Debian Bluetooth Maintainers Installed-Size: 3364 Depends: libc6 (>= 2.15), libdbus-1-3 (>= 1.9.14), libglib2.0-0 (>= 2.31.…
-
Raspbian kernel is Linux 4.9.59-v7+ #1047 (from uname -a)