If the drones use e.g. laser rangefinders to measure the distance to 2-3 known reflectors, and maybe to each other, with sub-mm accuracy, that may be enough.
Deploying an antenna that's effectively 50 or 100 m wide by lifting 10-20 drones, after some simple ground preparations, could be invaluable in many scenarios, especially for the military, of course.
The same technique as he uses here for synchronizing the receivers would work. Common reception and triangulation of a strong local beacon would enable positioning at much better than GNSS precision, both because of the SNR advantage itself and because you'd have more options for dealing with carrier phase ambiguity.
I$ pressure from bloating machine code with such high-volume information.
Though c.f. prefetch and clflush instructions, as well as the concept (s) of non-tenporal and write-combining stores.
There are some stateless things that are also called NAT, sure, but that's not what we're talking about here. (Fairly obviously, since a stateless mapping doesn't and can't save addresses).
But this feels tautological. It's been reduced to "If you want to use NAT with features that only a firewall gives you, then that forces you to use a firewall".
I suspect when people talk about "NAT" in the context of a residential connection, what they actually mean is a "default-deny firewall with connection tracking".
Feel free to replace "NAT" with "the kind of NAT that permits you to share an address between multiple devices" if you feel the need to be pointlessly pedantic about it. The point is that any device that allows sharing a single IP between multiple devices will necessarily implement connection tracking, and will therefore be capable of functioning as a firewall.
(Are you going to point out that statelessly blocking a fixed IP range used to be called "firewalling" so a device without connection tracking can still technically be a "firewall" next?)
I have firewalls in v4 and v6 networks which don’t do any natting (well other than some 6-4 between them). They track sessions for security purposes, and they time them out for both security and memory reasons.
Not if the end user isn't in control of the firewall. (And if they were, then they could just forward dedicated ports for the devices they need.) It might not be as bad as the CGNAT situation, but there are plenty of big WANs that can't be reconfigured at will.
Do they maybe also mandate ownership of a valid suitable (for voting) form of ID?
Because then it's something you need regardless of voting, so you aren't using right to vote to force it onto people.
I'm not sure if it is mandated but it is certainly relatively easily obtained. You will need a birth certificate and it will often differ in name for married women. The relative ease with which it can be obtained is important for voting, I suspect.
Thanks, I'll see about Box-PF when trying to get IMU-filtered indoor-localization working (once I hopefully get that far with the UWB firmware [0]). Accounting for clock drift across the "satellites" is going to be "fun", but at least it's both useful in practice and of manageable complexity/scope.
PF is a great tool for UWB. Even without IMU data and instead adding uniform diffusion of the particles between updates tracking worked well in a 2D environment. It sounds like you're working on TDOA for UWB?
Eventually I'll get to actually rolling a POC/tech demonstrator that just has less modules at perhaps less current density, for showing that even several kV DC can be efficiently transformed not just on paper to few or sub kV DC. At enough voltage grounding is no longer optional anyways, so might as well do essentially an auto transformer plus extra protection to protect humans against electric shock (RCD doesn't work directly, but the functionality can still be offered, it just has to sense quite differently).
Why DC? An overhead line only limited by peak voltage (arc) and thermals can carry twice the power when running DC instead of AC, assuming both measured relative to ground.
Also, you can run you transistors completely steady-state at all frequency components between their own switching fundamental and your load transients.
No more over provisioning just to make up for legacy 50/60 Hz AC.
Also, to a degree, you can just plug raw batteries in with that be DC grid, at most having a little bit of DC regulation to force the voltage a bit higher/lower than the batteries.
Like, a power supply basically rated to a couple percent of the battery input/output max power: only need to move the small extra voltage, though ofc at the full current.
Lastly, DC converters are just way smaller and lighter, so you could avoid the heavy bulky transformers in trains and alleviate power limiting from them. Relevant for fast double-decker trains because you'd prefer to have human space where you currently park the transformer.
I have to say though, novel development of technology by pulling recent innovations in the fundamental/material science fields underlying the target, is very not an easy thing to do.
I wish me a budget 10000 mAh size "phone slab format/shape" power bank with like 18W output at 9~12V kind of "fast charge" style, and a built in Google air tag.
They already have a button and a battery and a case; only need to add the BLE and the Google-mandated buzzer.
I'd pay 5 bucks more than for the competition without the integrated tracker. That should easily cover the cost, right?
I'm looking for a source of like ~100 UWB-only ones aiming for about 2~3 weeks of battery runtime on a pack of 2~3 AA batteries. Mostly depends on what voltage end the chips handle better: 2V low end, or 4.5V high end.
The aim is to keep track of where shared equipment is during the logistics phases of 39c3.
And, also, using the quite possibly wall-wart-piwered base station network to provide what's essentially rather precise indoor-GPS to users with sufficiently open FiRa hardware.
reply