Communications Support Forums
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.
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.