• To anyone looking to acquire commercial radio programming software:

    Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.

    If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.

    To obtain Motorola software see the Sticky in the Motorola forum.

    The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.

    For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).

    This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.

Wifi and Trbo radio management woes

ffexpCP

wizard of odd
Database Admin
Joined
May 15, 2004
Messages
748
Reaction score
58
Location
Michigan
I have a small fleet of Trbo radios linked up with radio management. Server is on a dedicated machine for Motorola stuff, like battery fleet management (for a mix of Trbo and APX).

I have 9 locations, all with VPN on the same network. All the wired PCs (including remote locations) work fine for BMS. My problem is the WiFi for RM. Sometimes it works, then eventually it stops. I’m not entirely sure when it dies, as I send a job and forget it for a few months until another change needs to be made.

Firewall on the server is totally off. I gave up messing with letting individual ports through when I found windows updates were re-securing them. I can ping the server from the SSID the radios are on. I can ping the radios from the server. Server has static IP.

For ease of troubleshooting, I’m focusing on the local network that has one of the wifi APs and the server. No sense bothering with the more complex VPN / remote locations if it doesn’t work locally.

A handful of remote Pcs also have RM suite installed, minus the server part. Radios will instantly program if a job is pending when plugged into USB. So, I know there’s some communications occurring over the network to and from the server, I’m just having an issue with the Wi-Fi side. I’m using default ports in codeplugs and each part of the RM server stuff. In the codeplug, it is directed to the correct IP for the server.

Any ideas?
 
Last edited:

Firebuff880

Member
Joined
Aug 28, 2006
Messages
803
Reaction score
216
Location
Boynton Beach, FL
Jobs getting hung up on a specific IP or Device Programmer is a fairly common problem, unfortunately --

Check the TTL for your DHCP handing out IPs to the Subscribers --

Try clearing the ARP cache on the DP System, and on the RM server, this often helps --

Also, when scheduling a JOB, try not to use the ANY option.
 

TampaTyron

Beep Boop, Beep Boop
Joined
Feb 1, 2010
Messages
1,206
Reaction score
505
Location
Phoenix, AZ
Are you using 5353 or another port? Are you explicitly defining the Device Programmer IP or letting wifi "figure it out"? We have started auto closing and restarting Device Programmer service as stuff gets hung. We moved away from 5353 as it is a commonly duplicated port (try 5454 instead, but you have to retouch everything).

I would also setup a NTP server somewhere or the users with R7s will be updet their time is off.

TT
 
Top