P164 IP assignment

[joelwitkowski]

Hello all,

I cannot seem to assign the IP address on this p164 device, or change the configuration to DHCP. 

I could connect to the device's web GUI in default config mode, after adding an address in the same network segment.

I then connected the device using USB/Serial and I can make changes, apply, read them back, and that all seems to work -I'm connected.  But upon changing the address, I do not connect if trying to use the IP address in the control software thereafter.  The web GUI likewise doesn't load and no response from a ping request.

I think I might be missing something with the Special WIZ network config button.. Or perhaps the "Connect to" must be populated with the PC I am trying to establish the connection with?

I'm missing something.  Any guidance you can offer is appreciated greatly.

Thanks!

Also, RDS2, can I flip this on in the United States now?

[Jan]

The IP configuration is easy.

Using existing connection (either USB or Ethernet), go to Device Setup - LAN Settings in the Magic RDS 4.

Fill the network parameters as required and click on Apply button. After 20 seconds, the device is available on the network, with the new parameters applied. Existing IP connection is closed.

The device supports status via UDP broadcast, so in local network you can click on the ConfigTool button to see current status, e.g. current IP address assigned by DHCP. That is all.

Hardware watch-dog timer is available as well, if you enable the Fail-safe monitor. Whatever happens with the network, the device will always restore the connection once the network is operating again.

Older encoders should be updated to firmware version 2.2e to ensure compatibility with latest Magic RDS version.

We are not following the RDS2 progress in particular countries. As a manufacturer, we only guarantee compliance with latest IEC 62106 standard release. Not all countries have it implemented yet. We would recommend to consult that with national authority before going on-air with the station logo. I'm having some opinion but it may not be relevant.

[joelwitkowski]

I can seem to assign the unit IP address, either statically or set for DHCP and have the unit apply the settings, but I do not see the device upon scanning the network thereafter, and cannot then establish any connectivity outside of the USB/serial link with the MagicRDS software.  What information can you offer about the Port 2 configuration settings?

I'm certain the network hardware was working with the default static assignment when I pulled it form the box.  Apologies, but I am not sure what it is I am missing here..

[Jan]

There's nothing special about the network setup. In a general sense, Ethernet is not trivial.

After clicking on the Apply button the device indicates new configuration loading by blinking the Operation LED (- - - - - instead of . . . . . ) for about 10 seconds.  OK?

Then, the new configuration is active.

You can verify it by clicking on the ConfigTool button. This diagnostics tool uses UDP broadcast for searching the device so it shows up also in the case the device is not accessible due to incorrect IP etc.
If you cannot see the device in the ConfigTool, it is probably attached to different network or not attached at all (cable failure, auto-negotiation issue etc.).

For successful connection, the IP assignment must be within the local segment and correct connection mode must be set on both sides (client->server or server<-client). If you use a firewall, corresponding port and application must be included in the firewall exceptions. (For the default Windows firewall the Magic RDS installator does this automatically.) Special care must be taken for PC computers with multiple network adapters.

For further help with the network setup I would need more information/screenshots:
from the router: DHCP setup page, LAN setup page
from the Magic RDS: LAN setup, ConfigTool

[joelwitkowski]

I'm certain my network is issuing DHCP -but with that configured, or a static config on the local lan, I cannot see the device with, for instance, Advanced IP scanner.  Is the device only thereafter accessible with MagicRDS software and a configured client-server IP link and not in any other way 'discoverable'?

[Jan]

Unfortunately, I don't know. I never needed such tools. I don't think they are useful for such simple task.

Please send the screenshots so that I can distinguish whether it is a bad configuration or software or device. The device must be visible in the ConfigTool. If it is not listed there, the network connection probably does not exist at all, and any attempt to configure the device will not be successful.

[joelwitkowski]

I apologize profusely for causing confusion.  I am simply going to post the screens, I may be looking at this config tool all wrong.  I'm sure the unit is working right.  I'm sure I am overlooking something.  I've not populated anything in the config-tool screen in the shot attached.

[Jan]

Thanks. The device seems to work properly, but it is in the factory default configuration.

Please go to Terminal and type SETLAN. Post me the reply.

Also type VER and make sure the RDS firmware version is 2.2d or later.

[Jan]

I think I found the problem. The configuration from the Magic RDS 4 does not load under certain conditions. It is a bug in the Magic RDS 4 version 4.1.8. I apologize to all users, if somebody else had the same issue. It will be fixed soon.

Thank you for all information. Pls wait for further instructions.

[Jan]

The encoder is ok, the problem was in the Magic RDS 4 control software.

Update to the latest version here: http://pira.cz/rds/magicrds/MagicRDS_Setup.exe

[joelwitkowski]

I will do that.  Sorry I have not had a chance yet to revisit this.  I would like to use the device, once configured, without using the MagicRDS software, with IP packets direct from the automation system (or XML export?), as the streaming/RDS PCs are allowed to auto-update, then get stuck on a Windows boot to set up some stupid Microsoft thing that I don't care about.  So I am likely to generate... numerous additional posts requesting further guidance.

I appreciate greatly the support and will report my findings upon circling back to the P164!  Thanks Jan!