Posted by: Jan
« on: February 24, 2024, 09:30:23 am »The encoder's internal website seems to display properly, so I would start by checking the point 2) from the above.
News:
Thank you for using this forum as the technical support base for your device.
● You can format the text and attach screenshots, photos and RDS Spy records
● Faster reply: 50 % of questions are answered within 30 minutes
● You don't need to register (but registration is possible)
● The members represent a wide range of experts
● The resolution will be helpful to other users
● You'll be notified by email about new post
Posted by: Larry Fuss
« on: February 24, 2024, 12:38:28 am »Thanks Jan, Kirk says he will look into the network adaptor issue. The power adaptor being used is the one we purchased with the unit.
Posted by: Jan
« on: February 23, 2024, 10:41:30 pm »Thanks Kirk, I already received some additional info from Larry.
The encoder seems to be ok, the problem is in the software setup. There are two specific issues:
1) The Magic RDS 4 currently does not support multiple network adapters in the same PC. In other words, you cannot choose the adapter directly in the application, the application uses such adapter for the connection which is assigned by Windows routing table. (The route can be set up in Windows if necessary.)
Thus, you should verify that the connection is really established between the Magic RDS 4 and the encoder. The Magic RDS 4 must indicate 'Connected' and the encoder must indicate the connection by the TCP LED. This is essential.
2) Although the encoder supports several methods of Ethernet setup, it is preferable to use the method as described in the manual (section 6.3.2), i.e. using the USB cable and the Magic RDS 4 - Device Setup - LAN Settings. The reason is simple - the Magic RDS 4 will not allow invalid setup for some advanced parameters (for example, the UART speed must be 19200, not 115200).
3) It was not mentioned yet (and I do not really believe that this is applicable here) but the power adapter may be wrong.
4) Theoretically, you may be experiencing Ethernet auto negotiation problem. Although I have never experienced it personally, auto negotiation failure is known to be relativelly frequent. It happens when link speed and duplex are not correctly arranged between the network devices, which causes dropped packets, slower throughput and session drops. Not all devices allow the auto negotiation configuration so common solution is to add an extra Ethernet switch between them (different brand/model).
The encoder seems to be ok, the problem is in the software setup. There are two specific issues:
1) The Magic RDS 4 currently does not support multiple network adapters in the same PC. In other words, you cannot choose the adapter directly in the application, the application uses such adapter for the connection which is assigned by Windows routing table. (The route can be set up in Windows if necessary.)
Thus, you should verify that the connection is really established between the Magic RDS 4 and the encoder. The Magic RDS 4 must indicate 'Connected' and the encoder must indicate the connection by the TCP LED. This is essential.
2) Although the encoder supports several methods of Ethernet setup, it is preferable to use the method as described in the manual (section 6.3.2), i.e. using the USB cable and the Magic RDS 4 - Device Setup - LAN Settings. The reason is simple - the Magic RDS 4 will not allow invalid setup for some advanced parameters (for example, the UART speed must be 19200, not 115200).
3) It was not mentioned yet (and I do not really believe that this is applicable here) but the power adapter may be wrong.
4) Theoretically, you may be experiencing Ethernet auto negotiation problem. Although I have never experienced it personally, auto negotiation failure is known to be relativelly frequent. It happens when link speed and duplex are not correctly arranged between the network devices, which causes dropped packets, slower throughput and session drops. Not all devices allow the auto negotiation configuration so common solution is to add an extra Ethernet switch between them (different brand/model).
Posted by: Kirk Harnack
« on: February 23, 2024, 10:10:42 pm »Larry Fuss mentioned that Support has requested "the settings on the router".
Well, the router is not involved in this connection. The computer running Magic RDS does have 2 network cards. One of them is on our "business" network at 192.168.1.43. The Gateway for this network is 192.168.1.1. This is a /24 network.
The other network card is at 10.0.0.43. This network is an internal LAN only, not connected to any router. The Pira P164 has been set to 10.0.0.113, but as an experiment I believe they tried it at 10.0.0.93. Both of these IP addresses are otherwise unused on the 10.0.0.0/24 network. The Pira P164 replies to pings just fine.
Larry mentioned that the connection was "slow". This is a mischaracterization. Speed or bandwidth is not determined. He means to say that the Magic RDA software reports very little data is shown in aggregate as being received or sent to the P164. This would be expected if the P164 is not - for whatever reason - responding to the Magic RDS software communications.
I'm at a loss to guess why this problem is exhibited. Communication between the comuter with Magic RDS and any other device on the 10.0.0.0/24 network is uninhibited as far as I can tell. We communicate perfectly fine with several other devices on this private LAN.
Best,
Kirk
Well, the router is not involved in this connection. The computer running Magic RDS does have 2 network cards. One of them is on our "business" network at 192.168.1.43. The Gateway for this network is 192.168.1.1. This is a /24 network.
The other network card is at 10.0.0.43. This network is an internal LAN only, not connected to any router. The Pira P164 has been set to 10.0.0.113, but as an experiment I believe they tried it at 10.0.0.93. Both of these IP addresses are otherwise unused on the 10.0.0.0/24 network. The Pira P164 replies to pings just fine.
Larry mentioned that the connection was "slow". This is a mischaracterization. Speed or bandwidth is not determined. He means to say that the Magic RDA software reports very little data is shown in aggregate as being received or sent to the P164. This would be expected if the P164 is not - for whatever reason - responding to the Magic RDS software communications.
I'm at a loss to guess why this problem is exhibited. Communication between the comuter with Magic RDS and any other device on the 10.0.0.0/24 network is uninhibited as far as I can tell. We communicate perfectly fine with several other devices on this private LAN.
Best,
Kirk
Posted by: Jan
« on: February 23, 2024, 09:04:34 pm »Yes, sorry, only registered members can see emails 
Posted by: Larry Fuss
« on: February 23, 2024, 05:53:40 pm »Not seeing your web address. Shoot me an e-mail - larry at larryfuss.com
Posted by: Jan
« on: February 23, 2024, 11:11:08 am »From the web browser:
The encoder website, the router DHCP settings and DHCP client list
The encoder website, the router DHCP settings and DHCP client list
Posted by: Jan
« on: February 23, 2024, 11:10:34 am »Please send the files to my email (the address is here on the left side under the envelope icon).
If I am to analyze the behavior of the network, I would need as much information as possible (screenshots are ok). The samples are attached below.
From the Magic RDS 4:
Device Overview, Edit Connection, LAN Settings, ConfigTool
If I am to analyze the behavior of the network, I would need as much information as possible (screenshots are ok). The samples are attached below.
From the Magic RDS 4:
Device Overview, Edit Connection, LAN Settings, ConfigTool
Posted by: Larry Fuss
« on: February 23, 2024, 02:48:49 am »The network guy has already looked at it and found nothing wrong. Where should I send the files?
Posted by: Jan
« on: February 21, 2024, 10:16:24 pm »So the hardware is ok. Please send me the Magic RDS connection settings and the encoder TCP settings.
If there's no problem with other locations, you should consult the issue with your network administrator.
If there's no problem with other locations, you should consult the issue with your network administrator.
Posted by: Larry Fuss
« on: February 21, 2024, 10:02:53 pm »We tried all that. No change.
Posted by: Jan
« on: February 20, 2024, 07:04:25 pm »No such issue has been reported yet. Start by replacing the UTP cable.
Next, try another unit from the order to rule out possible failure of the Ethernet connector.
Also check for possible MAC address conflict. The unit uses Ethernet chip which has unique MAC address but in the Magic RDS 4 this address is rewritable by the user. This is useful feature but must be handled with care.
Next, try another unit from the order to rule out possible failure of the Ethernet connector.
Also check for possible MAC address conflict. The unit uses Ethernet chip which has unique MAC address but in the Magic RDS 4 this address is rewritable by the user. This is useful feature but must be handled with care.
Posted by: Larry Fuss
« on: February 20, 2024, 06:08:24 pm »Situation: New Pira P164 keeps reporting a timeout. Magic RDS 4 says the unit is connected, but I keep getting the timeout error. RX and TX speeds are incredibly low. Other than that, all settings look normal and there is no IP address conflict. I'm baffled. Any ideas?