Learning to Fly
- May 3, 2017
- Reaction score
- Ellicott City, MD
Mike -The Cedar sales guy was a bit cringey describing the Max family, but this does look like an improvement over the Max360.
"We have specific firmware that can go in here, not only because of added bandwidth that wifi downloading gives us over bluetooth, but also because we tweaked some of the processing that goes on in here" - Eh, OK, maybe they rev'ed the hardware design, but that wireless bandwidth stuff leading to better firmware is pure BS.
Here's what I'm wondering. Are Escort's firmware developers better than their mobile app developers? Escort Live on both iOS and Android have had plenty of road bumps and lack of progress. Can their firmware developers do a better job? They added a wifi chip, had to write a TCP/IP stack, HTTP tools, and logic for Escort Live and firmware updates on the RD, while neither their firmware nor mobile app developers have a great track record. On mobile at least the network stack and tools are already there for you... but maybe you can license these tool sets for common chipset and devices these days? Any thoughts @FWGuy ?
Escort Live, RD firmware, Defender Database updates, are all familiar. VeilGuy is hinting that other network services will be coming, I wonder what else there could be down the pipeline?
I don't think band segmentation is going to transform the M6 and justify a $700 price from a performance stand point, but at least Escort is still developing their products and appears to be listening to their customers when it comes to filtering, and is attempting to lead the market in technologies consumers are familiar with even if they're of questionable worth at the moment.
Their wireless "shifters" sound like they're attempting to solve one of the major hurdles to purchasers, hopefully they add a timeout and educate their customers on JTK before they're banned everywhere...
You're making a pretty insightful comment.
First - sorry for not responding sooner. I don't get emails when someone uses the @ sign any more. That started with the website migration and I've checked all my settings. I have no idea why I don't get emails anymore. There's no setting that says "emails in response to @ sign" so I don't know what to do.
Anyway, I only see @FWGuy when I'm reading a post these days.
So, onto what you mentioned - firmware developers and Andriod/iPhone developers are two different breeds. Much like GUI developers are a different breed than fw guys.
Nevertheless, it'd be really rare for someone (especially a fw developer) to have to write a TCPIP stack these days. In every case I've seen, the chip vendor provides the TCPIP firmware free of charge if you're using their chips in your product. And of course, the vendor takes some precautions so that their TCPIP ( or Bluetooth or WiFi or ZigBee) stack can only be used with their chips.
If you look closely at pictures of the Max360 circuit board, you'll notice that the Bluetooth portion is really a small circuit board mounted on the larger Max360 "motherboard" (mainboard). This is because Escort is buying what's called a "module" from a vendor. The module performs the Bluetooth functionality but also hides the Bluetooth details behind a simple serial interface. So the Escort firmware people have commands like "pair" and "send/receive data" that they use to deal with the Bluetooth interface.
Same (probably) with WiFi. A number of vendors sell a packaged solution (what I'm calling a "module") so that the people who want to use WiFi don't need to know the nitty-gritty details.
It's a little more expensive hardware-wise to purchase one of these modules rather than just a chip but it saves a lot of cost in terms of fw development time. The fw developer doesn't need to come up to speed on Bluetooth/WiFi'/whatever and then write and debug code. This saves a lot of time and cost.
One thing that matters, besides writing and testing fw is time to market. If the fw guys had to learn the details of Bluetooth or WiFi, the learning curve would be months long. Most companies don't have that kind of time so the company is willing to take a small hit to the cost of the hardware to save the time in development.
As for why Escort would go to WiFi - I don't know. WiFi is certainly faster than Bluetooth but Bluetooth seemed to be fine for EL. And as far as being connected to the internet 24-7, I guess that's valuable for alerts but other than that, why do we need to be connected 24-7 - for the fw updates that come out every 2 or 3 years?
I never cared to use my phone with my detector and maybe I'm not the only one who felt that way. So the WiFi is a step in the right direction but it doesn't make me want to upgrade.
Honestly, I'm hoping Uniden fixes their DB and laser detector on their next product.
--- Post updated ---
When segmenting results in not scanning, you'll get a performance increase. When segmenting means the processor just isn't reporting that segment, there's no performance increase."Again. "Segs" do not do anything on a MAX digital detector other than mute alerts. They are NOT for performance gains. Disabling the entire Ka band on a MAX will not increase X and K performance."
Not scanning is what makes a detector faster. Reporting (or not) on what's been scanned isn't going to save much time.