A place to talk about anything and everything Omega related
4040
Topics
21878
Posts
@nreyes According to the documentation the Arduino dock uses UART1 to communicate so you need to use ttyS1.
https://docs.onion.io/omega2-docs/arduino-dock-2.html
https://docs.onion.io/omega2-docs/uart1.html#uart1
Hello, We have the same goal.
Right now I only have ways to tell you how it doesn’t work. I hope in the next few days I can tell you something more.
I think that with the Onion package, you can only read the PN532 from the UART.
Our goal now is to compile version 1.8 of the libnfc (https://github.com/nfc-tools/libnfc/releases/tag/libnfc-1.8.0) to use the PN532 from I2C and then replace pn532 with pn7150, which is more current and cheaper.
If you get anything publish it please, I’ll keep you informed.
Regards
Go-to resource for frequently asked technical questions
51
Topics
87
Posts
Np!
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
I guess this is just cloning and injecting the overlay into a "fresh" omega right?
The target device can be not "fresh" since this will overwrite the overlay partition (on /dev/mtd3). But just to be safe try to make sure the target device is fresh.
For more info on openwrt flash layout, see this OpenWRT Docs article
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
Are there any concerns about using the same firmware version on both source and target?
You raise a good point! I would recommend making sure you're using the same firmware version on both source and target. I've edited the procedure above to mention this.
This process will only clone the overlay partition, that is, changes you've made to the device. This could potentially cause issues if the packages in the firmware of the target are a different version than on the source.
@Lazar-Demin Thank you for replying!
I shall see if i can use the data_depth method to do what I need.
But wouldn't the points_3D be more useful? Since I am trying to find two points on the screen to measure the distance. The 2 points most likely won't be on the same axis, so in order to get the distance between points wouldn't it be better to use the points_3D fuction, as it returns 3D coordinates in meters? Because as as far as I can tell the data_depth method returns how far the point is away from the camera (correct me if I'm wrong).
I shall also let you know if I make any progress using data_depth to get the distance, thanks!
