696 karma · joined July 28, 2015
I also pay thousands of dollars to live in a cool place, and now I am finally getting to enjoy it, and enjoy it with my SO.
At the end of the day, maybe I am less "productive", by normal standards, but maybe I didn't need to be in an office for 8+ hours every day to get the parts of my job done that need getting done.
There surely are parts of this that I want to change or can't wait to change, but at the end of the day I am grateful for the forcing function to working from home full-time.
To use 1password on a new device, you need a "secret key" that is provided to you when you create your account which serves as a basic form of 2FA for your whole account. Not a perfect system, but it is not as simple as just getting your password and having access to everything.
Our core products are our cellular modules, as the certification burden on them far outweighs the process for WiFi modules (PTCRB, carrier certs). While we definitely have customers that use our WiFi products in a production capacity, generally our customers use our WiFi portfolio to prototype in their offices and then migrate to a cellular module for their end product. Saves cost and complexity when you just want to get something working, and our DeviceOS allows you to use the same or similar publish APIs regardless of the underlying connectivity technology.
When you purchase one of our modules, you are buying into a proven and tested platform that is guaranteed to work with our cloud. You just need to make your hardware and set up your backend. We handle the rest. Additionally, we don't make a lot of margin on our hardware - it's not the business we are in.
In terms of processing power, we target applications that don't need to crunch numbers. A great way to describe our platform is a "pipe" that takes your data from some sensor out in a field and drops it in your cloud backend/database. Our best applications are ones in which someone needs to answer "where is my device?" or "how is my device functioning?". In these verticals, it's all about data transmission rather than processing. Often these devices are battery powered and geographically hard to access. They spend a lot of time asleep, and when awake want to consume as little energy as possible.
The IoT landscape is vast, and we have narrowed in on a set of solutions that work well with specific verticals. Our product isn't a fit for every situation, as you have pointed out. For the ones it does fit for, we can provide significant value as a platform.
Our offering comes down to three things:
1. Pre-certified hardware modules (open source [2]) that support WiFi or Cellular in a few form factors.
2. An on-device OS (also open source) that handles communication in the background and abstracts away the hardware using an Arduino-like API.
3. A cloud-based "command center" (closed source) that allows you to link up your backend services with events flowing to and from your devices via webhooks, manage over the air updates, and see connectivity metrics across your fleet. No data is stored - just ferried between your devices and the other end of the pipe that you configure.
Oh, and you can buy our devices off-the-shelf in small volumes and get them up and running in a few minutes!
Thanks for the memory!
I'm so happy to see innovative and less invasive treatments for common diseases being approved.
According to JPL[2] at least one scientific instrument will continue functioning until about 2025, and the crafts will remain in range of the Deep Space Network until 2036.
[1] https://en.wikipedia.org/wiki/Radioisotope_thermoelectric_ge...
[2] https://voyager.jpl.nasa.gov/frequently-asked-questions/
However there is a workaround if you are willing to disable SIP and play around with a program called SwitchResX. You can customize the display timings in such a way that allows 4K60 video to just sneak in under the bandwidth limits of the Thunderbolt ports. It also requires a Thunderbolt to HDMI 2.0 adapter, and a compatible monitor. If you like fiddling around this is one way to do it, but I have found it finicky and not really worth it.
[1] https://www.co2meter.com/products/k-30-co2-sensor-module
Additionally, when I do my designs, I place the BME280 sensor as far away from other components as possible (I see it is close to a SOIC chip on your board) and I route a cutout in the board around the sensor to reduce any heat conduction from the board. I also ensure that I have no power planes on the little resulting "island" PCB, and use small traces (with local decoupling) to further reduce any conductive heat. See the image in [2] for an example of what I am talking about.
Another alternative I pursued in situations where convective heat was an issue is to stick the sensor on a little remote board and use an off-the-shelf wire to connect the two (check out the Sparkfun Qwiic wires[3])
Overall you want to increase airflow around the sensor as much as possible so leaving it "hanging out" somewhere is the best approach to getting accurate measurements.
I hope that helps!
[1] http://www.kandrsmith.org/RJS/Misc/Hygrometers/calib_many.ht...
[2] https://www.instructables.com/id/How-to-Measure-Temperature-...
Organic doesn't mean nothing is applied. It's just a different category of product that is approved.
Company: https://vemo.com/
Article: https://www.bloomberg.com/news/articles/2019-04-09/college-g...