Thread: Foc.us - Lucid Dream Simulator - EILD

Thanks for the info.

Very interesting. I might get one later just for fun, it might be expensive but at the same time if it aids lucid dreaming it's be worth the risk.

I have it for some days. Had pre-lucid dreams with it, but only tried two nights with it already.
(developer) documentation is sparse, but support ist helpful. The device itself is nice and very customizable.
But the moovs-electrodes are very uncomfortable for sleeping, especially if you are a side sleeper like me.
As it has no REM detection, one must guess REM time or do REM-detection with a ZEO or other method.

Raipat, did you get anywhere with the developer documentation? I also looked into it some months ago but the Bluetooth calls were quite a mess... do you have a snippet to turn the device on and off?

Actually, yes. The code for the android app on github left me lost, although in their androidapp-master\app\src\main\java\us\foc\transcranial\dcs\b luetooth\ApiService.java file is everything you need. I promised a guy at klartraumforum.de to combine ZEO mobile API (REM-detection) and tACS trigger, but did not deliver anything useful, yet.
Then I bought O'Reilly's "Getting started with BLE" book, figured out the basics, that was very helpful.
I wrote foc.us support again for BLE specs, they send me this: foc.us Bluetooth Low Energy API *** Link changed by staff ***

For now, I can use my zeopi-device setup (ZEO Bedside plus raspberry pi+BLE dongle) to activate tACS during REM with bluez gattool and a shell script called from python code. You can fiddle with the services.

root@raspberrypi:/# gatttool -I
[ ][LE]> connect 78:A5:04:58:93:FB
Attempting to connect to 78:A5:04:58:93:FB
Connection successful
[78:A5:04:58:93:FB][LE]> primary
attr handle: 0x0001, end grp handle: 0x000b uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x000c, end grp handle: 0x000f uuid: 00001801-0000-1000-8000-00805f9b34fb
attr handle: 0x0010, end grp handle: 0x001c uuid: 0000180a-0000-1000-8000-00805f9b34fb
attr handle: 0x001d, end grp handle: 0x0021 uuid: 0000180f-0000-1000-8000-00805f9b34fb
attr handle: 0x0022, end grp handle: 0x0033 uuid: 0000aab0-f845-40fa-995d-658a43feea4c
attr handle: 0x0034, end grp handle: 0xffff uuid: 0000aa10-f845-40fa-995d-658a43feea4c

[78:A5:04:58:93:FB][LE]> char-desc 0x0033
handle: 0x0033, uuid: 00002902-0000-1000-8000-00805f9b34fb
handle: 0x0034, uuid: 00002800-0000-1000-8000-00805f9b34fb
handle: 0x0035, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x0036, uuid: 0000aa11-f845-40fa-995d-658a43feea4c
handle: 0x0037, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x0038, uuid: 0000aa12-f845-40fa-995d-658a43feea4c
handle: 0x0039, uuid: 00002902-0000-1000-8000-00805f9b34fb

basically you issue commands and then read the response
[78:A5:04:58:93:FB][LE]> char-write-cmd 0x0033 0x010000000000 // get time
[78:A5:04:58:93:FB][LE]> char-read-uuid 0000AAB2-F845-40FA-995D-658A43FEEA4C
handle: 0x0026 value: 03 03 00 00 00 00

hope this helps.

bye,
Raipat

To the mods: please do not remove links in this post. They point to useful documentation, not commercial pages.

Yeah, that is where I got lost last time!

My guy wants me to activate it and the settings should be Wave, tACS, 40 Hz, duration 30 seconds, current 0.125 mA, current offset 0, bipolar ON, 20 Volts.

Guess I'd need to do that with the programs and descriptors.

Then start the program with 0x020701000000. Is that what you use to activate it?

Thanks!

Originally Posted by Raipat

To the mods: please do not remove links in this post. They point to useful documentation, not commercial pages.

The URL pointed to a page with items for sale. We apologize, but such links are not allowed.

Edit/update: The link has been replaced to go to exactly the same information without the presence of a prohibited eCommerce site.

Raipat, don't worry - I managed to get the link to the BLE specification before *** Removed staff name-calling ***

anderj101, the URL really didn't point to a page with items for sale... it pointed to technical documentation - the entire page didn't have any product, pictures or links on it - just raw documentation. You'd have to ban just about every URL if behind some links in the footer or header or somewhere else on the site there exists a store with items for sale. It's like saying we aren't allowed to go the library or Barns and Nobles because there is a Starbucks or coffee shop in it!

Anyway, for those tinkerers that follow, if you were to enter bluetooth-low-energy-api and focus into Google you should find the spec we were talking about... like this:
*** Prohibited Link Removed ***

Hi Guys any one getting some consistant Lucids with this devise yet?

Yes, you configure "programs" and then start them. I guess 60 seconds (1 minute) is the shortest duration configurable. But you could abort the program after 30 sec with another command. I had to disable BT security to be able to talk to the device from Raspberry as I could not figure out how to "pair" properly. This needs of course to be fixed if I use the setup outside my home
I will blog about my progress soon at my Schlafhacking blog and put my zeopi shit on github. It is ridiculous that I am not allowed to share links to technical documentation here. Obiously this is the wrong platform to effectively and collaboratively work on sleep hacking projects.

Originally Posted by IAmCoder

.. anderj101, the URL really didn't point to a page with items for sale... it pointed to technical documentation - the entire page didn't have any product, pictures or links on it - just raw documentation. You'd have to ban just about every URL if behind some links in the footer or header or somewhere else on the site there exists a store with items for sale...[/url]

Same issue again and again.... after one of my links were removed for the same reason, I had the same (private) conversation with anderj101 and he said he does see my point - which is the same with yours - and discuss it with the admins. Unfortunately it seems that nothing has happened. It's so simple: only direct links to products for sale should be banned. Pages with links to commercial pages... are virtually every page on the web - even Dream Views is not add-free (i.e. it links to commercial pages...). So we cannot post a link to another DV page, correct? Don't you mods-admins see that this is problematic?

well, I don't do BS discussion, also there is a forum "rule" here to not discuss moderation decisions, I just want to share knowledge. Take it or leave it.

The owners of the site decide which google ads are displayed on each page, and have instructed staff to remove any links that point to a site that sells stuff. When the mods who saw the original link reviewed their browser history, they found that the link for that "foc.us v2 controller BLE API" pointed to a page that lets you have an account/shopping cart etc. I'm looking at it right now and I can tell you for sure, that's the exact type of link that's not accepted. That's why it was removed. We weren't trying to be rude or confusing, it's just part of the job we agreed to do for the owners.

In the future, just link to it like this, to avoid hassle:
https://docs.google.com/document/d/1...?embedded=true

If there's still confusion about why the link was deleted, please direct the question to http://www.dreamviews.com/talk-staff/