CraigR
lvl.4
Australia
Offline
|
Cetacean Posted at 2017-9-4 15:03
Aloha Craig,
You are flying a network of three computers, the RC, AC and your device. All three computers have firmware and the device has an app. The parts of the network have to interact properly with each other. That means that the more powerful firmware that is shown to work very well thousands of times a day on remote controllers and aircraft needs an appropriately powerful device to process the input from the more powerful firmware on the RC and AC. The new firmware increases calculations exponentially and that stresses the device. The device can be streamlined to only operate with the RC and AC and with no background apps or downloads but that can only go so far until it needs more powerful processors and more RAM.
No, you're incorrect. The firmware is running on the RC and the AC and not on your tablet/phone. But, what would I know? I've only been paid as a systems level and embedded programmer for 25 years and unpaid for maybe 10 years before my 4 years of university.
You are seriously misunderstanding how things work, I'm afraid.
If you think that the behaviour of the drone shown at the beginning of this thread is caused by the tablet/phone then that is incorrect.
When many people first start programming professionally they might tend to "blame the user" when they do not experience a reported issue or problem themselves. Yeah, sure, sometimes it is the client/user's fault; maybe even often. But jumping to that conclusion is a road towards pain, misery and failure. If one of my clients report an issue with firmware that I've programmed I investigate it, even if I'm not experiencing the problem myself on my hardware. If the number of client's reporting issues after a firmware upgrade that I've programmed (or helped program) and pushed exceeds a fairly low threshold and I can't within a reasonable (very short) period come up with a solution then I pull the firmware out of release (call it a digital product recall if you like) and start pushing the previous release of the firmware to clients (e.g. basically a rollback). This is the responsible thing to do.
Anyhow, I get the impression that you don't want to listen because you're still insisting that the firmware runs partially on the phone/tablet, so I don't know what else I can say.
|
|