USB Serial data via Serial-Tools

Question/Issue:
MacBook Air M1
Data stream coming in via USB
Protocol Description
Interface level: TTL Baud rate: 115200bps
Stop bit: 1
Data bits: 8
Parity check: None
Can see it in the Protocol analyzer

Any ideas on how to stream it to EdgeImpulse? The sensor device isn’t programmable.

Project ID:
The Mind Sauna
Context/Use case:

1 Like

Hi @Rich_Peacock

Welcome to the forum!

Here I can recommend using your M1 mac with our Data Forwarder

  1. 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.
  2. 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
  1. Run the Data Forwarder: Execute the Data Forwarder with the appropriate serial port and baud rate:
edge-impulse-data-forwarder --port /dev/tty.usb-B001J9VZ --baud-rate 115200

Also if this is in relation to a product, please contact our sales team to ensure you have the support required to get this to the next stage. If you need help with this please let us know.

Best

Eoin

Thanks Eoin,
I’ll give that a try. Here is the sensor in action.
https://indd.adobe.com/view/9ce81d9e-a913-45f2-ace4-c64be7489380
I’ll let you know.
Best,
Rich Peacock

Hi Eion,

  1. Install Edge Impulse CLI :
    (base) Southgate:~ apple$ npm install -g edge-impulse-cli

installed ok I believe:
added 378 packages in 35s

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

please advise.


Re: Salesteam—got a call logged. At the moment it’s an MVP on the Macbook Air

Thanks

Hi @Rich_Peacock

you will need to work from the Linux SDK custom sensor example in Python or C++, if you need help on furthering this then sales will help you get that to market:

Here is a video to get started with.

Best

Eoin

Ah @Rich_Peacock

You don’t need to install that it comes with the cli here are the full list of steps:

Best

Eoin

Thanks Eoin,
That’s great! I love Python.
I’ll get time to try this out this evening.
Looking forward to it.
I’ll let you know.
Best,
Rich

Hi Eoin,

Thanks for the info. All done.
The problem is I don’t believe Edge Impulse can see the data feed from this Seeed Sensor: MR60BHA1 60GHz mmWave Module

I note Edge Impulse can connect to a number of [Seeed Community Targets] but the 60GHz mmWave Module is not listed.

The data is coming in fine I believe but it’s just raw numbers at the moment.

I will check SEEED forums. Your expert thoughts would be appreciated.

Many thanks,

Rich Peacock

1 Like

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


)

1 Like

Hi @Rich_Peacock

Great to meet, hopefully you can get some data into a project :smiley:

  1. 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.
  2. 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
  1. 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.


Feel free to post pictures of your wiring for review

Best

Eoin

Hi Eoin,
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.
Screenshot 2023-12-05 at 13.43.16

Hi eion,

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).

Hi @Rich_Peacock

Where are the emails being sent, the email on my card? I dont see any in the junk box.

The Protocol Analyzer looks correct for that sensor, the baud rate is 115200, data bits to 8, parity to none, and stop bits to 1.

First try this

  1. trial an error - Auto RTS turned off and RAW mode turned on. This may produce a readable output
  2. ask on the seeed forum The datasheet doesn’t have much content on the sensor settings.

Look for an option to begin capturing or logging data and activate it, then paste the output here. Its hard to read that text

next if the first doesn’t get you progress an alternative to protocol analyzer

  1. read via microcontroller If the mac / data forwarding route isn’t working maybe try by connecting the sensor to an arduino or other microcontroller.

  2. python script Alternatively if you can get the sensor data to export to a CSV file then you can upload the output directly.

Do you want me to give you a sample program for the arduino or python script to export to CSV?

Best

Eoin

Hi Eoin
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,
Thanks again.
Rich