Arduino Nano 33 Sense: Failed to start sensor fusion sampling

Help
#1

I have a student in the Coursera course who is running into a bug/issue I have not seen before. Any ideas on how to fix this?

Here is their description:

After collecting samples for over 5 mins, I began seeing ‘Sampling Failed’ error. I’m using the Arduino Nano 33 Sense Rev 2. I’ve attached the screenshot from Edge Impulse as well as the log snippet from the command line. The snippet has one successful log followed by the failures.

image

[SER] Configured upload settings
[SER] Sampling started
[SER] Sampling done
[SER] Device not connected to WiFi directly, reading from buffer (bytes 0 - 17505, expecting to read ~23340 bytes...
[SER] Reading 46% complete...
[SER] Reading 97% complete...
[SER] Reading from buffer OK
[SER] File is 17505 bytes after decoding
[SER] Uploading to https://ingestion.edgeimpulse.com/api/training/data
[SER] Uploading to https://ingestion.edgeimpulse.com/api/training/data OK
[WS ] Incoming sampling request {
  path: '/api/training/data',
  label: 'idle',
  length: 10000,
  interval: 16,
  hmacKey: 'c1a65367f33d01db231349a6b8b0dd6d',
  sensor: 'Inertial (Accelerometer / Gyroscope)'
}
[SER] Configured upload settings
[SER] Sampling started
[SER] Sampling failed ERR: Failed to start sensor fusion sampling
[WS ] Failed to sample data ERR: Failed to start sensor fusion sampling
[WS ] Incoming sampling request {
  path: '/api/training/data',
  label: 'idle',
  length: 10000,
  interval: 16,
  hmacKey: 'c1a65367f33d01db231349a6b8b0dd6d',
  sensor: 'Inertial (Accelerometer / Gyroscope)'
}
[SER] Configured upload settings
[SER] Sampling started
[SER] Sampling failed ERR: Failed to start sensor fusion sampling
[WS ] Failed to sample data ERR: Failed to start sensor fusion sampling
#2

Here is the project ID: 623442

#3

Hi @ShawnHymel !

Can you ask them to run in verbose and share the output? @ei_francesco @Arjan do you think that there is an issue with the rev2 sampling rate perhaps, or buffering? From what I understand its only the IMU that changed? Are there different sampling rates etc? Or is this the correct thing to review?

edge-impulse-data-forwarder --verbose

They could of course try reflashing the firmware and cleaning the cli before connecting again, and maybe that should be the first port of call.

Best

Eoin

#4

I don’t think he’s running the edge-impulse-data-forwarder, rather the edge-impulse-daemon tool. It looks like a heap memory related issue. We will look into it.

Thanks for sharing!
Arjan

#5

I’m using the daemon. I will try and capture verbose logs when I run into it again. Thanks so much for looking into it.