#1 issue Monitor -> Wireless The most critical part of an install page and it's slow, confusing, auto refresh scrolls up. Vomit.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Jan 20, 2015 at 12:15 PM, Vlad Sedov <[email protected]> wrote: > This has been one of our biggest complaints from day one. > The interface, while it has gotten slightly more usable, is still complete > garbage. It's unpredictable, slow, and inconsistent.. Let alone the > features that just don't work. > > Why on earth did they not just stick with a field-tested, fast, usable > interface from the Canopy line? Nobody buys a radio for it's slide-out > menus and pretty HTML5 crap. > We need, fast, intuitive, consistent.. Forget the shiny. > > grr > > Vlad > > > > On 1/20/2015 10:57 AM, Nate Burke wrote: > >> Ok, Cambium, this is a little sad. My Field Laptop, a Lenovo S10-3t, >> Atom Processor with Windows 8.1 cannot load the EPMP WEB Pages in a timely >> manner. We're talking 40-60 seconds for initial load, and 20-30 seconds >> per screen refresh/menu change. Since I'm going to have to go to the boss, >> and tell him that I need a new laptop to do any field troubleshooting for >> these new radios, what are the minimum system specs for a machine to view >> the EPMP Screens? Unless Cambium is going to get their Web interface under >> control as of Yesterday. >> >> They still swear that the GUI was all developed in house and not >> purchased (something I still can't believe). I'd like to know who the >> engineers/managers are who signed off on that design. I can only imaging >> that there was a group of guys sitting around the conference table, >> watching the presentation on the GUI on the projector up front, all nodding >> their heads in agreement, "I think this is a wonderful layout, the field >> tech's won't mind waiting a couple extra minutes for the pages to load so >> they can look this pretty!!" >> >> I think that Cambium should step up and get engineers from ALL aspects of >> product development out into the field. 40 seconds waiting for the page to >> load is fine when you're sitting in the office, but not when you have the >> laptop balanced on a stack of firewood in the freezing rain trying to get >> to the monitoring page to see why a radio isn't linking up. I think that >> every WISP on this list would be more than happy to host an engineer for a >> day. Heck, even if they go into the parking lot and assemble it on the >> tailgate of someone's Pickup, they'll get some idea of what we experience. >> >> I have a feeling that if all steps of the Dev process took a week in the >> field, We'd have a radio that had a GUI that responded instantly on any >> device, and radios that assembled and mounted (and unmounted) with 1 gloved >> hand. >> >> </rant> >> Nate >> > >
