Protect your radios from unexpected downtime with two-way radio services for. Radio Management Software programs multiple radios at one time. Entire radio fleet programming status, along with the configuration history for each device to.
. The Radio Management Database - This stores all the data about the managed devices.
Usually abbreviated to RM. It uses Microsoft SQL Server Express as a basis for managing relational data. Job Processor - This gathers the required information from the RM Database and sends it on to the Device Programmer.
If the PC which hosts the Job Processor has more Processor Cores, it will be able to handle more concurrent jobs.You can have a single or multiple Job Processor PCs connected to a server. The Device Programmer - this takes the information sent from the Job Processor and sends it out to a device. You can have a single or multiple Device Programmer PCs connected to a server.
You can also allocate a certain number of radios to be OTAPed (or programmed) from a specific Device Programmer PC. On non-Capacity Max systems, you would also use Device Discovery and Mobility Service (abbr. DDMS) to process ARS messages from radios, and send this information on to the Device Programmer. DDMS would also only really be used when you use OTAP since it helps Radio Management to figure out which radio is on or not.
MNIS would be used on systems that don't use a Control Station (read further) but instead use NAI (or VRC on Capacity Max). Hi Wayne,I have just installed CPS 15.5 and trying to update about 80 DP4801 to new firmware. The problem I'm facing is once I upgrade firmware on the template I am unable to apply the template with updated fw to all the radios that the template was previously applied to, it only lists about half of the radios to apply the new template to.
And after I updated all those radios it lists if I try again it says 'no available radio to upgrade' even though the template is clearly showing as in use by the remaining radios. There is no difference between the radios that work and the ones that don't, all same model, running same fw with exact same template. Hi Wayne, We have a TRBOnet dispatcher/Watcher solution running on a server and the Swift/Control station for Audio Paths etc. Now the system is running great however I am now trying to get our LCP system to do Radio Management.
I have a separate workstation with the dispatcher and watcher client which is also the CPS programming station and has RM and DDMS installed. Anyway I have searched forums high and low and before I throw this at my dealer I thought I'd ask the Guru Wayne. When I start the RM Monitor app and configure it (like your video) even after successful configuring it is still saying across the top of the screen 'RM Device Monitor(2.8.14.0) Repeater IP Programming Status There is no system available to be connected'. I have my TRBONet watcher on in the background so I can see what is transmitting to whom etc, but the Rm will not work OTA (OK on USB) I have read the System Planner, Your OTAP 1-5 and every forum or instruction I can find including all the documentation by the 3rd party application manufacturers and I still get nothing. I am a little disappointing by the lack of documentation for the RM and the poor design of the app.
Especially trying to clean it all up and start again. You can't even uninstalling it - it does not clean uninstall and therefore retains all all old jobs used to try and test it (which failed). I am having to completely re-image the computer to get a fresh start.Have you any idea what can be the problem with the error above and where I can get better documentation from Motorola regarding the RM setup and how it works to understand the fault.
It would also be better to use the Swift control station as the control radio for the RM too. But as you can guess, there is very little documentation. There is unfortunately no Installation Guide for Radio Management. There is however a fair bit of training material. The difficulty with creating an installation guide is that there are endless possible configurations for Radio Management and it would be near impossible to describe how to set up each one of them. None the less, it's something I'll take up with our documentation team (I have to be careful as suggesting stuff sometimes gets me volunteered/seconded:-))The uninstall for Radio Management is a little quirky. You have to uninstall each component; completely uninstall Microsoft SQL then, to be safe, I find that cleaning the registry is also a good idea.
No Windows redo needed.A quick check to determine the root cause of OTAP failing, is to ping the radio IP. There is a post coming up on this topic but each Radio has an IP address made up of the CAI number and Radio ID. For example, Radio ID 1 will (by default) have an IP address of 12.0.0.1 and Radio 5320 will have an IP address of 12.0.20.200. The rule is, if you can ping the radio from the Device Programmer PC, you can OTAP it.
If you cannot ping the radio, try pinging the MNIS tunnel IP which should be 192.168.10.1 (I think) or the Control Station radio which should be at the same address.If you're using a Control Station, make sure you can call it using an individual call from another radio.If you're using MNIS, you should be able to send it a radio check (not sure on this point).Another thing to check, is to make sure there's a static persistent route between the 192 and 12 subnets. MNIS (and the ping test) needs this. There are a number of howto's on this point, just Google 'static persistent route windows'.That's all I can think of for now. As a test, try reading the radio using (standalone CPS) from the PC that's hosting the device programmer.
If the read runs normally, then the PC to radio connection is good.Connect a radio to the Device Programmer host PC, power it on and go to the network connection for the radio and disable IPv6. Try scheduling a read now and see what happens.If Radio Management and the Device Programmer are on different machines, install and run Wireshark on the device programmer PC. Schedule a read and look (filter) traffic to and from the radio management PC.If Radio Management and the Device Programmer are on the same machine, make sure there aren't any other (unnecessary) services running at the same time e.g. Skype; Google Chrome.If you are using RM2.0 (Configuration Mode) make sure the job pacing setting is set to a reasonable value (I would suggest 1 for starters).Make sure there is enough free memory.Make sure Windows 10 has updated - if you are using Windows 10.If none of these work then you'll need to contact technical support (see https://cwh050.blogspot.com/p/support.html).
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |