@Anco-van-der-Kolk I will be writing the library in C/C++
While I am far from being an expert in Python, I believe the bulk of my library will be callable from Python just as is done with the current code for Neopixel control.
Though I have no idea as to how the interrupt from the Arduino to the Omega could be handled in Python - sorry :-(
Regarding using a resistor bridge for change from 5v to 3.3v - yes, since the signal is only needed one way (Arduino -> Omega), this would be feasible if it is really needed.
Two suitably chosen resistors in series - one end to GND the other end to the Arduiono pin and the mid-point to the Omega pin
Thank you! Now I guess for me, to have these work as household agents, I need to be either plug free or electrical system snap-ins. Otherwise, it's my parents' Christmas tree all over again. (You know the tree with 20 strands in an octopus tangle of plugs and extension cords.)
Maybe as a request to the Onion team or beg my EE friends to come up with a Onion dock or extension that puts the transformer there instead of at the end of the cord.The connectors would be splicing agents that would ride on the 120-volt wires.
I just realized that specific software driver profile loadouts could be housed on custom and small flash drives that could ship all needed packages (which opkg could later update once installed) for a specific hardware kit ordered from the store. Really, for the above to make sense, I do believe that we'd need to tweak the OS to allow for running packages installed outside of root, such that the 16MB root partition can house only the absolute essential bootstrapping tech, while the external usb hub is required to run the actual application/project software necessary.
root@Omega-24CF:/# fdisk -l
Disk /dev/mtdblock0: 0 MB, 131072 bytes
Disk /dev/mtdblock1: 1 MB, 1150464 bytes
Disk /dev/mtdblock2: 15 MB, 15429632 bytes
Disk /dev/mtdblock3: 7 MB, 7929856 bytes
Disk /dev/mtdblock4: 0 MB, 65536 bytes
Disk /dev/mtdblock5: 16 MB, 16580608 bytes
For me everything is a bit learning by doing now. So I think to put this info's in to the wiki could help several persons. But before i do so, please correct if i see something wrong or to simplified ;)
For whatever it's worth, the most common issues with UVC cameras is lack of power. Consult your technical documentation for minimum voltage and current requirements then make sure you have enough to support your camera's operation. Otherwise, you'll be chasing these issues for a while.
@Kit-Bishop Yeah, I remember writing that part.
I went back and double-checked that there wasn't an extra rounding (missing cast to float) that might have been eating up some of the precision. But the code looks clean :)
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to Community was lost, please wait while we try to reconnect.