Edge-impulse-daemon -Error

After installing Edge impulse cli , When I run the command - edge-impulse-daemon, I am facing this issue

C:\Users\Manivannan>edge-impulse-daemon
C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\bindings\bindings.js:135
throw err;
^

Error: Could not locate the bindings file. Tried:
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\build\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\build\Debug\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\build\Release\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\out\Debug\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\Debug\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\out\Release\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\Release\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\build\default\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\compiled\14.15.4\win32\x64\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\addon-build\release\install-root\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\addon-build\debug\install-root\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\addon-build\default\install-root\bindings.node
→ C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\lib\binding\node-v83-win32-x64\bindings.node
at bindings (C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\bindings\bindings.js:126:9)
at Object. (C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\lib\win32.js:1:36)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings\lib\index.js:6:22)
at Module._compile (internal/modules/cjs/loader.js:1063:30) {
tries: [
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\build\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\build\Debug\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\build\Release\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\out\Debug\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\Debug\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\out\Release\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\Release\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\build\default\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\compiled\14.15.4\win32\x64\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\addon-build\release\install-root\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\addon-build\debug\install-root\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\addon-build\default\install-root\bindings.node’,
‘C:\Users\Manivannan\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\@serialport\bindings\lib\binding\node-v83-win32-x64\bindings.node’
]
}

@Mani could you post the output of

npm uninstall -g edge-impulse-cli
npm install -g edge-impulse-cli

Hey @janjongboom , the issue get resolved , when I upgraded the Visual studio C++ to the latest version. Thank you

1 Like

hey what is your visual studio version
which version is suitable to run edge impulse daemon command

internal/modules/cjs/loader.js:883
throw err;
^

Error: Cannot find module ‘C:\Users\khush\AppData\Roaming\npm\node_modules\edge-impulse-cli\build\cli\daemon.js’
←[90m at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)←[39m
←[90m at Function.Module._load (internal/modules/cjs/loader.js:725:27)←[39m
←[90m at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)←[39m
←[90m at internal/main/run_main_module.js:17:47←[39m {
code: ←[32m’MODULE_NOT_FOUND’←[39m,
requireStack: []

i am still getting these errors what to do

Hi @01fe20bec237,

It looks like the Edge Impulse CLI was not correctly installed. Please try the steps found on this thread: Cant find data forwarder

now i am getting these errors continously even after updating the edge impulse cli

[SER] Connecting to COM5
[SER] Serial is connected, trying to read config…
[SER] Failed to get info off device Timeout when waiting for > (timeout: 5000) onConnected
[SER] Serial is connected, trying to read config…
[SER] Failed to get info off device Timeout when waiting for > (timeout: 5000) onConnected
[SER] Serial is connected, trying to read config…
[SER] Failed to get info off device Timeout when waiting for > (timeout: 5000) onConnected
[SER] Serial is connected, trying to read config…

Hello @01fe20bec237,
Did you uploaded the Edge Impulse firmware to your device correctly? Which hardware target are you using by the way?
The issue can also come from a bad usb cable.

Best,

Louis

Hello Louis,

I am attempting to connect my Arduino Nano with plate number 1 to Edge Impulse. I am using Ubuntu 22.04 operating system and following the steps for the setup provided below :

Here are the steps I have followed so far:

  1. Executed the command “curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash”
  2. Installed Node.js by running “nvm install node”
  3. Installed Edge Impulse CLI globally using “npm install -g edge-impulse-cli --force” and “npm install -g edge-impulse-cli”
  4. Started the Edge Impulse daemon using “HTTPS_PROXY=… edge-impulse-daemon”
  5. Updated the system using “sudo apt update”
  6. Installed snapd using “sudo apt install snapd”
  7. Installed Arduino CLI using “sudo snap install arduino-cli”
  8. Flashed the Linux shell using “sudo bash flash_linux.sh”
    9.sudo apt install git

brew update
brew install arduino-cli

Adding Environment variable to your path :
echo ‘export PATH=“/home/dsg/bin:$PATH”’ >> ~/.bashrc
echo ‘export PATH=“/home/dsg/bin:$PATH”’ >> ~/.bashrc

However, when I am getting the error, (base) nelum@nelum-X510UA:~$ edge-impulse-daemon
Segmentation fault (core dumped)

Hello @Nelum,

Could you share your project ID.
I suspect that your model is too big to run on the Arduino Nano (by the way which version of the Nano do you use?)

Best,

Louis

Hello @louis ,

My project Id is 286469. I am using Arduino Nano 33 BLE. It is not connected to Edge Impulse yet.

I am getting the below error when installing edge impulse cli
(base) nelum@nelum-X510UA:~$ npm install -g edge-impulse-cli
npm WARN deprecated @zeit/dockerignore@0.0.5: “@zeit/dockerignore” is no longer maintained
npm WARN deprecated request-promise@4.2.4: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported

changed 378 packages in 31s

14 packages are looking for funding
run npm fund for details

Hello @Nelum,

These are just warnings, your CLI seems properly installed.

Best,

Louis

I’m having a similar issue to OP. I’m using Homebrew on WSL to install node/npm.

$ node -v
v23.3.0

$ npm -v
10.9.0

$ npm config get prefix
/home/dmullett/.npm-global

When installing the CLI using npm, I get these depreciation warnings, but no errors. (I have attempted reinstalling the CLI and got the same result.

$ npm install -g edge-impulse-cli --force
npm warn using --force Recommended protections disabled.
(node:41114) ExperimentalWarning: CommonJS module /home/linuxbrew/.linuxbrew/lib/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /home/linuxbrew/.linuxbrew/lib/node_modules/npm/node_modules/supports-color/index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
npm warn deprecated osenv@0.1.5: This package is no longer supported.
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated move-concurrently@1.0.1: This package is no longer supported.
npm warn deprecated @zeit/dockerignore@0.0.5: "@zeit/dockerignore" is no longer maintained
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated figgy-pudding@3.5.2: This module is no longer supported.
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm warn deprecated request-promise@4.2.4: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated gauge@2.7.4: This package is no longer supported.
npm warn deprecated @xmldom/xmldom@0.8.8: this version has critical issues, please update to the latest version
npm warn deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142

added 529 packages in 17s

48 packages are looking for funding
  run `npm fund` for details

When attempting to run the CLI, the daemon is not found by npm

$ edge-impulse-daemon
node:internal/modules/cjs/loader:1242
  throw err;
  ^

Error: Cannot find module '/mnt/c/Users/dmull/AppData/Roaming/npm/node_modules/edge-impulse-cli/build/cli/daemon.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1239:15)
    at Function._load (node:internal/modules/cjs/loader:1064:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v23.3.0

I’ve tried reinstalling node/npm with the same result. Any tips on how to get the daemon to install? Most of the tips I’ve seen are reinstalling node and the CLI, but I’ve already tried those

HI @duneslayer

I’ve managed to get it running on WSL pretty recently try with npm v20 or v21 then follow : Installation | Edge Impulse Documentation

its likely you will have either missed a step, but try with 20 or 21 first to rule out a version issue.

Best

Eoin