Recent Posts

Pages: [1] 2 3 ... 10
1
P132, P164, P232(U) and P332 RDS Encoders / Re: TCP/IP Connection
« Last post by Jan on Yesterday at 09:47:41 pm »
Great, thank you. I'm already out of office for today so I'm not able to track how this happened but I can say that the story ends. What is certain is that the firmware version 2.2 has never been intended for P132/P332. It was written for the P164, before all these models were unified at the firmware level.

Current firmware version for entire family of RDS encoders is 2.2b which can be downloaded at https://pira.cz/rds/p132fwup.zip

Once you apply this FW via serial port, reconfigure again the PORT3/PORT4 parameters and reset the device.
2
P132, P164, P232(U) and P332 RDS Encoders / Re: TCP/IP Connection
« Last post by Nemosity on Yesterday at 09:24:48 pm »
Also, here is the serial number and mac of the unit I am working on today.

Serial number:   14095E92
MAC address:   0003941DA2C8
Socket status:   I/(-200,-200,-200,-200,-200,-200,-200,-200,-200,-200)
3
P132, P164, P232(U) and P332 RDS Encoders / Re: TCP/IP Connection
« Last post by Nemosity on Yesterday at 09:23:21 pm »
Thank you for your prompt response, this has been quite frustrating.  Please see the response and information in red below:

You do not mention supplier of the units, MAC or order number so I cannot track the units. Please send me the complete listing from the web GUI, section Status - Version.   

 RDS encoder firmware version 2.2
Embedded website version 2.1a
Build 2018-10-05
Ethernet module firmware version ID811d17 20.6.2016
Bootblock version 0801 9.6.2009

Next, go to section Tools - Terminal, and type following commands there, each confirmed by Enter:
Code: [Select]
SETLAN
SETPORT3
SETPORT4
SETCTO
MEM 7D,6
MEM 7E,6
Copy and post the replies to us.

Here are the replies to the terminal commands Listed above:

15:20:12 Code: [Select]
15:20:13 Command not accepted
15:20:22 SETLAN
15:20:23 AT+iFD$AT+iWEBP=80$AT+iWPWD=*$AT+iRPG=1234$AT+iNTS1=time.nist.gov$AT+iGMTO=-5$AT+iDSTD=02.LSun.03;03.LSun.10$AT+iNTOD=1$
15:20:27 SETPORT3
15:20:28 OK
15:20:31 SETPORT4
15:20:32 AT+iLTCP:10001,1$
15:20:49 SETCTO
15:20:50 1,1
15:21:01 MEM 7D,6
15:21:02 FF
15:21:13 MEM 7E,6
15:21:14 FF
4
P132, P164, P232(U) and P332 RDS Encoders / Re: TCP/IP Connection
« Last post by Jan on Yesterday at 06:44:01 pm »
This is a real mystery. We are very sorry that you have to solve this issue. From more than 5000 units sold this is a first report of that kind. The working web GUI is a proof that the unit can establish TCP connection without problems, because the web is still the server-client TCP communication. Thus there's no problem with the hardware, it is only software or configuration issue.

You do not mention supplier of the units, MAC or order number so I cannot track the units. Please send me the complete listing from the web GUI, section Status - Version.

Next, go to section Tools - Terminal, and type following commands there, each confirmed by Enter:
Code: [Select]
SETLAN
SETPORT3
SETPORT4
SETCTO
MEM 7D,6
MEM 7E,6Copy and post the replies to us.
5
P132, P164, P232(U) and P332 RDS Encoders / Re: TCP/IP Connection
« Last post by Nemosity on Yesterday at 04:43:41 pm »
I am at wits end here.  I can put a borrowed Innovonics 730 inline and it takes the data from my studio with no issues.  Yet, both Pira332's that we recently purchased are unable to connect through TCP/IP.  There is no network issue, I can ping the units at each site from the site computer.  I can pull up the web gui of each unit from outside the transmitter sites, and from the computer at each location.  Yet when using Magic RDS3 or Magic RDS4 I am unable to connect from the PC at each site through TCP/IP.  Serial connections work, web GUi's work, TCP/IP connection with the encoder set to be the server will simply not work.  These units are either defective, firmware was incorrectly loaded or there is a setting in them that is wrong, everything else has been tried.  The networks have been checked, rechecked, and checked again.  The fact that an Innovonics 730 works and connects without issue also shows the network and config is correct.

screen shots attached.  Both of these units, at two completely different sites exhibiting the same exact issue, hangs on connecting.
6
Release News / Re: Release News
« Last post by Jan on November 26, 2020, 08:33:00 pm »
Version 4.0.20

http://pira.cz/rds/magicrds/MagicRDS_Setup.exe

  • Web-server has been implemented (at this time a simple status page only). Enable in Preferences.
  • In the Terminal, there's a new button which allow to send a file to the encoder which contains ASCII commands (each command on separate line). Useful for example for quick pre-configuration of many encoders.
  • Recent events show also current date
  • RDS Spy is no longer launched if cannot operate (on uni-directional connections or on connections below 19200 bps)
  • Bug fixes: 'Trying speed 1200' on closed serial connection, some buttons were sometimes mixed, Bridges no longer show options valid only for encoders
7
Configuration Options / Re: Triggering TA via TCP, Telnet?
« Last post by davidmb on November 25, 2020, 10:33:44 am »
Hi,

it worked perfectly.

Had only a bit of a problem with syntax - I forgot to add ":" to sendto source: command.
   
Thank you for your help.

Data splitter also looks like an awesome option - did not try it yet - but will definitly consider it.

Great software! :)

Br, David
8
Configuration Options / Re: Triggering TA via TCP, Telnet?
« Last post by Jan on November 24, 2020, 09:19:53 pm »
Don't forget that you can also control all the encoder's directly by a single TCP connection.  :)
This method is described in m4vp.pdf, section Data Splitter for RDS Encoders.

If you type the command TA=1 followed by [Enter] in any TCP terminal, all the RDS encoders will receive it, translated to individual RDS encoder's communication protocol, where applicable.

Not all methods have been tested yet, don't hesitate to let us know if something is not working as expected or if something is not clear.
9
Configuration Options / Re: Triggering TA via TCP, Telnet?
« Last post by davidmb on November 24, 2020, 09:15:26 pm »
Hi Jan,

thanks for fast reply and recomendation.

Ok, will try it tomorow and report.

Br, David
10
Configuration Options / Re: Triggering TA via TCP, Telnet?
« Last post by Jan on November 24, 2020, 09:06:33 pm »
Any RDS service, incl. the TA, can be controlled by any available external text source: local file, remote file, TCP, serial etc.

  • Configure a new external text source.
    For TCP, follow the file m4vp.pdf in the application doc folder, section Redirecting to External Text Sources.
  • In the external text tool, go to Text Conditions, select the external text source from step 1 and fill the condition and command.

For sending TA to all encoders, the command is
Code: [Select]
send connection:"*" command:"TA=1"
The command is automatically translated to the encoder's communication protocol, depending on the encoder's model (ASCII PIRA, UECP, MicroRDS etc.).

The new External text tool, which is being developed, will bring further options.
Pages: [1] 2 3 ... 10