Mornin' gents, I have a client with a Monroe One-Net running the older 2.6 OS, with CAP and CAP+. (they don't have the $4K to fork out for a new system). Their EAS/CAP has been running perfectly until about 30 days ago when they stopped getting CAP messages. (the same problem occurred in July, 2020...lasted about 40 days, then resolved itself) EDIT: The unit is a R189se.
They're configured for IPAWSOPEN, 2.0 Get, have the latest CA files loaded (2021), DNS is enabled...they system goes in to "polling" mode, then returns a "not connected". I borrowed a duplicate unit, slapped it on my net, configured it the same and it works fine. Monroe's interface is a bit obtuse to say the least, but it's navigable and nothing is jumping out at me in terms of configuration. It looks good, smells good, pumps EAS messages...but CAP is a no-go (licenses are valid).
Any ideas on why this guy refuses to play nice with FEMA?
Thanks for your input, anyone that can help me out here...I can probably dig up a vintage t-shirt for your trouble, or my wife makes a mean pesto sauce we'd toss in.
Kind thanks for your input (Monroe said "load the latest CA then ignored me)
They're configured for IPAWSOPEN, 2.0 Get, have the latest CA files loaded (2021), DNS is enabled...they system goes in to "polling" mode, then returns a "not connected". I borrowed a duplicate unit, slapped it on my net, configured it the same and it works fine. Monroe's interface is a bit obtuse to say the least, but it's navigable and nothing is jumping out at me in terms of configuration. It looks good, smells good, pumps EAS messages...but CAP is a no-go (licenses are valid).
Any ideas on why this guy refuses to play nice with FEMA?
Thanks for your input, anyone that can help me out here...I can probably dig up a vintage t-shirt for your trouble, or my wife makes a mean pesto sauce we'd toss in.
Kind thanks for your input (Monroe said "load the latest CA then ignored me)
Last edited: