Strange things happened with my DGP5550/XPR7550

[Yoshisan]

Hi there, best regards to all of you. I had some strange things with my DGP5550, and if the same could happen to you, I want to share it here.

Yesterday night, I was programming my new Handy trough a Bluetooth link, was my first attempt to do it without the use of a physical cable. So I started associating the Windows 7 with the radio, I read some tutorials out there and I knew the typical tips for that.

I found the radio without problem, and I knew that the full pin code entered in the DGP/XPR would not be accepted by the PC, but at the third try, Windows would associate them with no code.

The process was carried out smoothly as I read and seen on Youtube, but when connecting to handy as a PAN gateway, an error was displayed saying it was not possible to communicate with the device, and I might repeat the whole process again. I tried a lot and a lot of times, always the same.

Then, I supposed Windows created the device and it supposed they were associated but the radio didn't think the same. I deleted the device, I begun all again and I choose the second option, “create mi own code”, I entered only five digits “5550”, and then the DGP5550 shows the input screen, I entered this code and the association concluded successfully, allowing me connect to it like the PAN gateway.

But the problems didn't end there, now, when I tried to read the radio after I activated the Bluetooth, Windows said that no device was found. I opened the command shell and with IPCONFIG I checked the TCP/IP addressing, so I found that the Gateway address was different than 192.168.11.1, It were 192.168.11.3.

With a ping to the 192.168.11.1 I received no echo, but to the gateway 192.168.11.3 I received full echo from the DGP5550.

Since the router is the rig I wanted to get, I changed the address in the CPS by the 192.168.11.3 that TCP / IP registred, and finally I was able to connect to the radio.

I hope to help more than any of you, the strange thing is that the process were did by two colleagues with the same model, the same platform, the same firmware, the same patches; but only mine generated so much trouble. After this, both radios are working very well. 73.

 

[Yoshisan]

Thank you very much Mars, for the warning about all the mistakes in my first post. 73 and good Dx.

 

[Mars]

Thank you very much Mars, for the warning about all the mistakes in my first post. 73 and good Dx.

Just to be clear: you were not warned. You did not do anything wrong. I was letting you know as a courtesy. No infractions were issued against your account.

 

[pboyd04]

FYI, My guess is that you changed the Radio IP on the Network page. The Bluetooh IP is derived from that. From the CPS help file "The IP value is not editable. It is derived from the Radio IP. The value in the third octet of this IP is always one value greater than the value of the third octet of Radio IP. For example, if the Radio IP is 192.168.1.1, the Bluetooth IP is derived to be 192.168.2.1." So my guess is that you set your Radio IP to 192.168.10.3 which would explain your IP address in bluetooth mode.

 

[Yoshisan]

Thank you very much dear pbody04, you're absolutely right, how I can forgot that!! I must admit that I am completely addicted to Motorola digital equipments, I have three VHF MotoTRBO radios and two P25 UHF XTS3000 in 800MHz. And for my future experiments I've programmed the three DMR radios for different network IP address, and this is the fact. And that's all about what's happening.

You're right, the blue tooth address comes from the network address, I read that!! Thanks a lot! Now I stay calmer with my last rig, it's working pretty well. Long time ago my best radio I've ever had, was an HT1000 with an original long heliflex antenna; but after a time the battery begins to fail, and I changed this radio with a new Yaesu FT60R, certainly a lot of more Ham's radio. I stayed away from there, with the professional line of Motorola radios, until the last time that I have become completely into the digital world.

And off course I've returned to the king Motorola. 73 and good Dx!

 

[Yoshisan]

Dear pboyd04, I was thinking more about. You're absolutely right with the TCP/IP address change, nothing more to say about that.

But... How you could explain about the no association to Windows, without PIN codes? My friend who bought the same radio from the same provider, same firmware, and so on the same thing. Got association at the first attempt!! So with a long PIN code I guess.

I will appreciate any hypothesis, for keep learning more about these radios. In advance... Thanks a lot, 73.

 

[com501]

The third octet change applies equally to the USB IP address also when using USB connections to third party equipment. The primary address will always be incremented for the subsidiary ports, and the USB and WiFi ports will have different IPs from the primary.

 

[Yoshisan]

Hi com501 thanks, really. Yes you're right, the IP address is statically defined based in the IP address of the radio, for the PAN accessory and LAN accessory. Mi radio works pretty well, in fact there is no problem with it. But I'm referring in my last comment, about the strange and particular way of association compared with other radio quite similar.

At this point the device it's only a RFCOMM device, so it have no network address, the TCP/IP addressing begins only when I defined the radio like a PAN gateway. Thanks so much to all of you. 73.