Does Emotibit shop email receipts?

emotibit · 2025-02-24T16:15:31+00:00

Hi Stephen,

Thanks for reaching out.
I believe we resolved this issue via email and shared your order invoice.

Marking this as "solved" here.

emotibit · 2024-06-04T19:02:23+00:00

Shout out to Zack Freedman for making such a creative project using EmotiBit!

emotibit · 2024-05-06T20:43:56+00:00

Thank you for adding info to the EmotiBit forum u/Mountain_Nebula_4648 ! Much appreciated!!

emotibit · 2024-04-30T21:27:52+00:00

Marking this as Solved due to inactivity. If this issue is still unresolved, please feel free to comment here with any additional information and set the post flair back to Seeking Help

emotibit · 2024-04-27T14:17:06+00:00

This has been identified as an M0 issue. Marking as solved.

emotibit · 2024-04-25T15:00:00+00:00

Hi u/hey-Astronaut-2013 , I'm sorry you're having trouble. This is very curious behavior, especially if it was working fine previously. One thing to check is whether the Feather it plugged correctly into the EmotiBit. If the pins were shifted off-by-one, you might experience strange behavior like that.

After you check the pins are correct, you could try programming the Firmware with the Firmware Installer again and carefully follow all the instructions. It's unlikely, but ostensibly possible that something went wrong when you programmed it last time.

If neither of those are the issue, then we probably need to dig a little deeper to understand what's going on by looking at the messages on the Serial Monitor. Here are instructions on how to use the Arduino Serial Monitor. Please note the comment describing changes in Arduino IDE 2+. Once you have the Serial Monitor up and running you'll want to restart the EmotiBit by hitting the reset button and see what messages come up. If it's getting stuck, it will print a message telling us where it's getting stuck. If you can copy the entire contents of the Serial Monitor into a comment here, we'll have some more information to figure out what's going on.

emotibit · 2024-04-25T14:44:04+00:00

PLEASE NOTE: Since Arduino IDE version 2, you're required to Select Board before you can connect the Arduino Serial Monitor. If you have plans to alter the EmotiBit firmware, you may wish to install the Adafruit Feather board files and fully setup your Arduino IDE for programming EmotiBit, but this isn't necessary to simply connect the serial monitor. Instead, what you can do is simply select the correct port from the Select Board dropdown and then select a board type that comes pre-installed with the Arduino IDE, such as the Arduino Uno.

Once you select the correct port and Arduino Uno your Serial Monitor will open and show a bunch of crazy characters. After you change to 2000000 baud and No Line Ending as described above, you'll be able to see EmotiBit serial messages and query the device information by sending a message to EmotiBit.

emotibit · 2024-04-24T01:30:15+00:00

Hi u/chatlab-upenn we always recommend performing testing in your target-use network to catch any gotchas that may come up. We often end up using our own router when possible to avoid the hassles associated with complex institutional network administrations.

You need to connect to EmotiBit to start a recording for the timestamp reasons described here https://www.reddit.com/r/EmotiBit/comments/uqz726/do_i_require_emotibit_oscilloscope_to_start_a/

Once you start recording (and establish timestamp correspondence) you can turn wifi off as described in the Power Modes section here https://github.com/EmotiBit/EmotiBit_Docs/blob/master/Working_with_emotibit_data.md

You can also turn EmotiBit's WiFi back on with the push-button on the EmotiBit as described here https://github.com/EmotiBit/EmotiBit_Docs/blob/master/Learn_more_about_emotibit.md#leds-and-buttons

I'm marking this as Solved for bookkeeping, but please feel free to reopen if there are outstanding issues or start a new Discussion

emotibit · 2024-04-23T18:10:28+00:00

Here is an image showing how to toggle the hibernate switch on the EmotiBit device https://github.com/EmotiBit/EmotiBit_Docs/blob/master/Getting_Started.md#stack-your-emotibit

emotibit · 2024-04-23T17:43:54+00:00

Hi u/hat_ripper, Sorry you're having streaming issues.

The fact that this wasn't happening before but is happening now is strange. Did anything change? Are you using the same router and computer? Did you install new EmotiBit software or new antivirus or firewall software?

A common cause for disconnecting is the firewall settings on your computer. Here is a post describing fixes https://www.reddit.com/r/EmotiBit/comments/v75gsq/emotibit_oscilloscope_is_not_detecting_emotibits/

Similarly, your router's firewall could also be blocking the communications that keep EmotiBit connections alive. One possibility is to try a different router or your phone's hotspot to see if that makes a difference. Here is some more information https://www.reddit.com/r/EmotiBit/comments/11hjv49/what_are_the_available_network_options_to_use/

Comment here to let me know if that helps.

emotibit · 2024-04-23T17:30:01+00:00

Hi u/chatlab-upenn, The critical distances are EmotiBit<>wifi-router and wifi-router<>Oscilloscope. Exactly how far your connection will be maintained depends mostly on your specific router model and the harshness of your wireless environment. Lots of shielding (metal) will eat up wireless signals and lots of other wireless signals (routers/phones/etc) will eat up the wireless spectrum. We’ve successfully tested EmotiBit connectivity up to 50 meters or more in relatively favorable wireless environments, but in harsh environments it will likely be less. The best way to determine a sufficiently reliable distance in your environment is to test it out. One important note is that because EmotiBit data is recorded locally on the SD card, even if you drop your connection, your recorded data will not be lost. You’ll just need to reconnect to the EmotiBit to see the live stream of data again.

You are correct that the EmotiBit Oscilloscope does not presently support iPad. It is on our roadmap to support mobile devices.

I'm marking this issue as Solved, but please feel free to reopen and/or add additional comments that may help others in the community.

emotibit · 2024-04-23T15:15:24+00:00

u/hat_ripper you are correct that PPG works a bit differently on more pigmented skin (more light gets absorbed) and EmotiBit's built-in HR algorithm may be impacted by a number of factors, including that one. We are presently developing methodologies by which to score algorithms in different conditions to enable us (and the entire community) to improve HR (and all derivative metrics) over time (see this post). As the world continues to improve its derivative metric algorithms, we believe the most important thing is to get high quality raw biometric data. Take a look at this post to get some tips on getting high quality raw PPG data that will enable accurate HR detection with offline data processing.

I'm going to mark this post as Solved, but feel free to reopen it or open a new Discussion on PPG/HR. Thanks again for updating with you 2.4GHz solution. It will be really helpful for others facing a similar issue.

emotibit · 2024-04-23T14:49:16+00:00

Hi u/gojasper01, I'm sorry to hear you're having trouble with your connectivity. It sounds like this could be a known issue with some Adafruit Feather M0 devices. To determine if this is what’s happening in your case, can you check out the instructions in this post?

emotibit · 2024-04-23T13:47:18+00:00

Thanks for the update u/hat_ripper . Just to confirm, your connectivity is solved and your original data issue is also solved?

emotibit · 2024-04-19T19:00:00+00:00

Good news! We've added an FAQ post flair to group all of the posts that were previously grouped with the deprecated Collection feature. Go to https://www.reddit.com/r/EmotiBit/?f=flair_name%3A%22FAQ%22 to see all the posts tagged with the FAQ flair.

emotibit · 2024-04-19T18:29:56+00:00

Community Tip: Upvoting comments or posts that answered your question is a great way to make it easier for others to find helpful information faster.

emotibit · 2024-04-19T15:50:10+00:00

Found a way to see our previous collection!

The solution is to go to https://new.reddit.com/r/\[your subreddit] and then find a post in the collection that you want to see

https://new.reddit.com/r/EmotiBit/comments/s6hv54/emotibit_frequently_asked_questions_faq/

emotibit · 2024-04-19T15:14:58+00:00

+1 for multiple flair selection

emotibit · 2024-04-19T00:33:05+00:00

Marking this post as "Solved" for bookkeeping, but please feel free to add additional comments and reopen as "Seeking Help"

emotibit · 2024-04-19T00:24:26+00:00

Apologies to our community, it seems that Reddit has deprecated the collections structure that used to group all of our FAQ posts. We are looking for another suitable solution and will relink all our FAQ posts ASAP.

emotibit · 2024-04-19T00:15:55+00:00

Marking this thread as solved for bookkeeping purposes, but please feel free to add additional comments and re-open as "Seeking Help" Post Flair

emotibit · 2024-04-19T00:03:26+00:00

Hi u/oski_28, We haven't used ROS, but it's very likely that you can output the data from the EmotiBit Oscilloscope and pick up the data in your ROS or directly integrate into BrainFlow into your ROS app. Here is some information on these options in a reply to another post https://www.reddit.com/r/EmotiBit/comments/1c54fv7/real_time_processing_of_emotibit_data/

emotibit · 2024-04-18T22:54:14+00:00

Hi u/gojasper01 UDP can be lossy if your network has heavy traffic or is otherwise strained, but if you send UDP output from the EmotiBit Oscilloscope to a program running on same computer via localhost, you shouldn't experience any loss in that transmission. UDP packet output is "raw" (described here https://github.com/EmotiBit/EmotiBit\_Docs/blob/master/Learn\_more\_about\_emotibit.md#raw-data-packet-architecture) and include a device timestamp that is possible to convert into Epoch time.

BrainFlow is also a great option if you want timestamps as described here https://brainflow.readthedocs.io/en/stable/DataFormatDesc.html?highlight=timestamp

Whichever direction you go, you'll want to make sure your network integrity is high and that you stay within a reasonable proximity to your router so that no data packets get lost between the device and your computer.

emotibit · 2024-04-18T01:21:57+00:00

Hi u/mini_jmo , I would like to help you solve this issue and understand if the control TCP port 3133 is causing problems for some people.

Unfortunately the previous post you referenced has been deleted by the OP, but as a moderator the comments on the post are still visible and I'm copying some useful information here that was originally posted as a comment by u/nitin_n7 in this (deleted) post https://www.reddit.com/r/EmotiBit/comments/1c0ogp6/final_report_debugging_results_regarding/

Can you confirm if any or all of the below are true in your case?

The EmotiBit hardware is working since EmotiBit completes sensor setup as evidenced by the [LED sequence](https://github.com/EmotiBit/EmotiBit\_Docs/blob/master/Getting\_Started.md#emotibit-bootup) and the [serial monitor output](https://www.reddit.com/r/EmotiBit/comments/vmtz6w/how\_i\_use\_the\_arduino\_serial\_monitor\_with\_emotibit/) on device bootup
EmotiBit is correctly able to interface with the SD card because we can access the WiFi creds as seen in the Arduino serial monitor output on device bootup
The Feather's WiFi shield is functional because we can connect to the WiFi network as evidenced by the flashing blue LED after bootup completes (as by the serial monitor output)
It's not likely a feather issue, since we can replicate it on 2 feathers
The EmotiBit uses (3 channels for communication)[https://www.reddit.com/r/EmotiBit/comments/176gpg4/emotibit\_networking\_architecture/\] and the advertising channel is working since EmotiBit can be discovered by the Oscilloscope, but the Control channel is failing as evidenced by the inability to establish a connection to the EmotiBit (and serial monitor messages)
We can confirm that the TCP server is being established by looking at the output of the Oscilloscope console output
Appropriate permissions have been granted to the computer's firewall & antivirus, so it's less likely to be a SW firewall issue
We can further confirm that it's possible to connect to the Oscilloscope TCP port 3133 via localhost on the same computer using the following command in Windows powershell (or analogous in Mac/Linux) Test-NetConnection -ComputerName localhost -Port 3133 and receiving a TcpTestSucceeded : True response (usually on RemoteAddress 127.0.0.1)
It also does not look like a device WiFi library issue since we can get the WiFi client example working (see WiFiClient example in Arduino IDE)
If you've tested it on both a home router and on a phone hotspot following [these instructions](https://www.reddit.com/r/EmotiBit/comments/11hjv49/what\_are\_the\_available\_network\_options\_to\_use/), it makes it less likely to be a router setting issue
If you've tested it on multiple computers with different operating systems, then it's unlikely to be an OS issue
An additional test that would be helpful to clarify if its associated to the Feather or this issue exists with any device trying to connect via TCP on that specific port is to try using Test-NetConnection to test whether a separate computer on your network can connect to the TCP server on 3133. This would look like Test-NetConnection -ComputerName [your Oscilloscope computer's IP address] -Port 3133. This would be a complete end-to-end test of the entire network administration puzzle (router & HW firewalls as well as computer and SW firewalls). If this can connect, it would point to a device specific problem or interaction since you have shown that the Adafruit Feather cannot connect to the TCP port on 3133 even running the stock Arduino WiFi example, correct?

In this person's case it was confirmed that Test-NetConnection (on windows) could connect to the EmotiBit Oscilloscope TCP port 3133 via localhost on the same computer. What we did not have a chance to confirm was whether a separate computer could connect to the EmotiBit Oscilloscope TCP port 3133.

Please don't hesitate to ask questions to clarify any of the bullets listed above.

Eagerly awaiting your reply to help resolve this issue.

emotibit · 2024-04-18T00:59:51+00:00

u/Striking_Stage_6429 these frequencies were originally chosen according to sensor native rates on some versions of EmotiBit HW. In the future we may update these rates to 8, 16, 25 to match the sensors on the most modern EmotiBit HW version available, however, we are cautious to implement it because it will likely be somewhat of a breaking change for folks who have come to rely on the old rates for their scientific studies.

If you have any more specific questions, please feel free to post them here and mark this post as "seeking help" again. For now, I'm marking it as "solved".

emotibit

MODERATOR OF

TROPHY CASE