Hi,
The quiescent level should be 1.8V, pulsing to 0V.
There was an issue before the "always-on" option was added. Idle cameras would sink large currents, and confuse the others. The workaround was to use a fairly hefty pull-up supplied by a Raspberry Pi.
The "always-on" parameter is supposed to put a stop to that -- as long as all the Raspberry Pis are powered on, then the cameras should be as well; they should all be weakly pulling XVS up to 1.8V; all currents should be well below 1mA.
Our documentation is a bit broken -- the recommended pull-up resistor values may not work for more than 2 cameras, it doesn't mention always-on or the timeout -- I need to revise it!
I don't have any experience with such long wires, but I don't see why it shouldn't work. Ground loop currents could be more of a problem than losses. If the cameras are far apart but have a network connection then the software method is worth trying.
The quiescent level should be 1.8V, pulsing to 0V.
There was an issue before the "always-on" option was added. Idle cameras would sink large currents, and confuse the others. The workaround was to use a fairly hefty pull-up supplied by a Raspberry Pi.
The "always-on" parameter is supposed to put a stop to that -- as long as all the Raspberry Pis are powered on, then the cameras should be as well; they should all be weakly pulling XVS up to 1.8V; all currents should be well below 1mA.
Our documentation is a bit broken -- the recommended pull-up resistor values may not work for more than 2 cameras, it doesn't mention always-on or the timeout -- I need to revise it!
I don't have any experience with such long wires, but I don't see why it shouldn't work. Ground loop currents could be more of a problem than losses. If the cameras are far apart but have a network connection then the software method is worth trying.
Statistics: Posted by njh — Tue Mar 25, 2025 10:09 am