MacBook Air M1
Data stream coming in via USB
Interface level: TTL Baud rate: 115200bps
Stop bit: 1
Data bits: 8
Parity check: None
Can see it in the Protocol analyzer
Verify Device Recognition: Ensure that your MacBook recognizes the USB device. You can do this by opening the Terminal and typing ls /dev/tty.*. This command lists all connected serial devices. Your device should be listed here. Yours seems to be: usb-B001J9VZ.
Install Edge Impulse CLI: If you haven’t already installed the Edge Impulse CLI, you can do so by running:
npm install -g edge-impulse-cli
Run the Data Forwarder: Execute the Data Forwarder with the appropriate serial port and baud rate:
I’m getting an error for stage 3:
(base) Southgate:~ apple$ npm install -g edge-impulse-data-forwarder
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/edge-impulse-data-forwarder - Not found
npm ERR! 404
npm ERR! 404 ‘edge-impulse-data-forwarder@*’ is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
I believe I have the latest npm
(base) Southgate:~ apple$ npm install -g npm@latest
changed 14 packages in 1s
I installed and updated node.js via Homebrew
Re: Salesteam—got a call logged. At the moment it’s an MVP on the Macbook Air
Hi Eoin, It was great to meet you in London last week. So I am closer to forwarding the data but it says it is the wrong frequency. I have tried to change it to 10. Any advice? getting close now! (see: google doc
Great to meet, hopefully you can get some data into a project
Wiring the Sensor to the FTDI USB Input: Ensure that the TX and RX pins of the sensor are correctly connected to the RX and TX pins of the FTDI, respectively i.e. rx to tx and tx to rx. The VCC and GND should also be correctly connected to supply power to the sensor.
Baud Rate Configuration: The baud rate specified is 115200bps. This rate should be configured both on the sensor (if it allows configuration) and within the forwarder.
The correct command to start the Data Forwarder is edge-impulse-data-forwarder --port /dev/tty.usb-B001J9VZ --baud-rate 115200
Issues with Data Frequency (not the current problem, again this appears more of a wiring fault here):
I think you have a problem here with the GP wiring check their doc > The human presence status output interface. You can use the level of these two pins to determine the current human movement in the environment.
GP2 output: high level - occupied, low level - unoccupied.
GP1 output: high level - active, low level - stationary…
Ensure the sensor is correctly wired to the FTDI interface, verify the baud rate settings, and also you can post on the SEED forum if there is any issue with the wiring steps in their guide.
Thanks very much for your considerate reply. I think I have the wiring okay as I get data as shown in the previous link. I can also connect via minicom in the terminal and I can see that it is connected. I’m out all day but I wanted to thank you quickly. I’ll have time this evening to check.
I have just seen that when I post links to the sensor working and the data feed your system flags it as “advertising” and spam folders it. It makes it slightly difficult to discuss as you have replied but included advice that you wouldn’t have if you’d read the emails which are being junked. They show the data is coming in but not being forwarded. Not sure what I can do to show you the links (they only go to the hosted video of the sensor working).
Thanks for your reply. I will 100% try this over the weekend. On the clock to a funding application deadline in three days — based around being able to pay Edge Impulse (ie you) for your time. BTW the messages were “flagged by the community but are now restored by staff”. They just show a video of the radar.
I’ll be in touch by Wednesday,