Posts made by Lazar Demin

Why do different coloured objects show up better/worse in the depth map?

Different colours (even on the same material) will affect how well an object is detected because of reflectivity.
(If you're unclear on how LiDAR and Time-of-Flight devices work, we suggest reading our short explainer on the subject)

Different coloured objects will absorb and reflect the IR light from the Tau differently, resulting in better or worse depth detection. Dark coloured objects and low reflectivity objects (grass, leather) will be harder to detect.

(There's no escaping from physics )

For better detection of these objects, try increasing the 3D integration time as much as possible.
The trade-off is that reflective or very close objects will be saturated.

What does purple represent in the 2D depth map?

This means the data point is "saturated." That is, the illumination from the Tau's IR light source that's reflected off the object is too strong to calculate a depth for that point.

If you're using Tau Studio, you'll notice the point cloud struggles to correctly handle these points since they have indeterminate depth.

To reduce the saturation, try reducing the 3D integration time. This is the same principle as reducing exposure time on a regular camera - it will reduce how much reflected light the Tau captures for depth measurements, hopefully bringing it into a usable range.

When the integration time is reduced, you'll immediately see more detail in the Grayscale and Amplitude frames coming from the camera.

There is a trade-off though: with a reduced integration time, there will be worse detection of far away objects and objects that reflect light poorly.

If reducing integration time doesn't help significantly, the object may just be too close. Or perhaps too close for how reflective it is, you'll have different results with more and less reflective objects. In both cases, try moving it farther from the camera.

@chronobob here is the emission spectrum of the LEDs:

Can I ask what is your intended use case?

@chronobob The light source is made up of 3 near-infrared LEDs. The wavelength of the light centres around 850nm.
Will have more information on the power later this week.

@Mark-Fisher the example code might be for the C version of LVGL?

As far as I recall, they had pretty sparse documentation for the micropython port. But that might have changed, I haven't looked into it in quite some time.

I agree with @crispyoz, your best bet is to go straight to the source and try posting on the lvgl forum. Let us know how it goes!

@ArgusR Awesome! What's the intended use case for your board?
Make sure to post some photos when it's done!

@jonty again, there's a difference between extending storage and extending memory

The boot from external storage guide will give you more storage space to work with. This is required if what you're trying to install can't fit on the Omega's internal flash storage.
Not sure how if this is needed for the AWS IoT Python modules since I don't know how big they are.

Judging by your screenshot, it looks like pip is running out of memory. Try going through the extend the available memory guide and running the install again.

@Nagarjuna-Reddy See the product pages for more info
North America Model: https://onion.io/store/omega2-lte-na/
Global Model: https://onion.io/store/omega2-lte-g/

And there's volume discounts, get the latest pricing here: https://onion.io/quote/

@jonty said in AWS IoT Python SDK v2 Installation:

even though I have extended my Omega's memory with a 4GB USB drive.

There's a nuance here. Did you set it up to boot from external storage or extend the available memory with a swap file?
You'll want to do the latter.

@sscalf fill out the quote form and respond to the email that we send you!

@jossvall The UART TXD0 and TXD1 pins fall into the "must be floating or pulled down at boot time" category. That should be satisfied by most UART devices.

Excerpt from the Omega2S Datasheet:

+1 to @jossvall's response

For reference, this is also mentioned in our documentation: http://docs.onion.io/omega2-docs/using-gpios.html#boot-pins
And in the Omega2S datasheet - see Section 3.3.1 - System Boot Pins

@eblasband you can also reference the mechanical drawing in the Omega2S datasheet: https://github.com/OnionIoT/Omega2/blob/master/Documents/Omega2S Datasheet.pdf

See our documentation article on opkg for more info: http://docs.onion.io/omega2-docs/using-opkg.html

@jossvall is right, the Omega2 modules do have 1x USB 2.0 Host

@ArgusR the Omega2S+ and LTE module on the Omega2 LTE are connected by USB (see the USBD+ and USBD- nets in the schematic), that's why there's no host port.

@Rohit-P Judging by the 000000000000 mac address, it looks like your factory partition was erased.

To get this device back up and running I would suggest:

1. Use a working Omega2 device to make an image of the factory partition (cat /dev/mtd2 > factory.bin)
2. On the device that's not working boot into web recovery mode by following steps 1 to 4 in this docs article
3. Then, click ART Update and flash the factory.bin you created in step 1

Note this is not a permanent solution since the device will have the same MAC address as the device in step 1, but it should get you to booting again.

@eblasband said in Built in Wifi antenna for Omega2S+ SMT:

My recommendation would be to put this detail (or whole section) in the Omega2S Hardware Design Guide as well.

That's a good suggestion, thanks! We'll make this update in our next round of documentation revisions.

@eblasband said in Built in Wifi antenna for Omega2S+ SMT:

Also side note about the documentation, is there a specific place to be posting recommendations?

Definitely! You can create an Issue on the Omega2 Repo on GitHub with your documentation feedback: https://github.com/OnionIoT/Omega2/issues

Btw, the datasheet and hw design guide actually include "Give Feedback" links at the bottom of each page that lead to this same GitHub repo. Is there anything we can do to make that more noticable?

What is the operating temperature range for the Tau Camera?

All of the components used in the Tau LiDAR Camera are rated for -40° to 85°C

@eblasband how can we improve the docs to make it clear that an external antenna is required?

If you run into Issues with the Tau Camera

Take a look at the Resources & Useful Links post, it has a ton of helpful information.

If you still can't resolve your issue, post here on the Community. The team will be around and will do their best to help you out. And best of all, the entire community will benefit from the conversation!

When posting, try to include as much helpful information as possible:

• What type of host computer you're using
• Installed Python version
• Version of installed Tau LiDAR Camera libraries
• A brief description of the issue you're experiencing vs what you expect to happen
• Steps to reproduce the issue
• Any other info, photos, or screen grabs that you think might be helpful

Reporting Software Bugs

If you've found a software bug, post a Bug Report issue on GitHub.

• Issues relating to the Tau Studio web app: https://github.com/OnionIoT/tau-lidar-server/issues
• Issues relating to the TauLidarCamera Python module: https://github.com/OnionIoT/tau-lidar-camera/issues

We also welcome all suggestions and Pull Requests!

Giving Feedback

We would love to hear all of your feedback and suggestions!

If it's something general, please make a new thread right here on the Onion Community.

If it's related to the Tau Camera software, get in touch by posting an issue on GitHub:

• Tau Studio web app: https://github.com/OnionIoT/tau-lidar-server/issues
• TauLidarCamera Python module: https://github.com/OnionIoT/tau-lidar-camera/issues