Posted by: Jan
« on: July 30, 2018, 10:22:00 pm »Nice to read that the unit is finally working. So far we didn't have any faulty P232. After you've tried several cables and PC's the problem worried me 
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: w0kie
« on: July 27, 2018, 10:38:42 pm »Null cable replaced with a $5.67 Amazon null serial cable. Problem solved. 
Posted by: w0kie
« on: July 25, 2018, 09:54:48 pm »Two different power bricks were used with correct voltage and polarity. See private email that was sent to you this date.
Posted by: Jan
« on: July 25, 2018, 07:41:56 am »Please follow my post from July 20th.
From previous posts, it appears that the device was not used in accordance with the instructions (improper power supply at least). From that point we cannot guarantee function and I can not help as I wish because I don't know real status of the device, if there was some electrical modification made etc.
From previous posts, it appears that the device was not used in accordance with the instructions (improper power supply at least). From that point we cannot guarantee function and I can not help as I wish because I don't know real status of the device, if there was some electrical modification made etc.
Posted by: w0kie
« on: July 25, 2018, 01:59:43 am »Replaced the FTDI adapter with a new dual port serial card in our production XP machine. Options/Preferences appeared to be properly working with the new serial card but still could not get bidirectional serial communication to occur, nor could we get the module to save one directional data from Magic RDS. The module seem to light the LEDs as expected and send the word *RDS* to a car radio display.
Posted by: Jan
« on: July 23, 2018, 07:29:09 pm »It does not need to be enabled. But you have no feedback from the unit, that is you have no confirmation if the unit receives the data. So you have to check it on the receiver. Does it update?
Posted by: w0kie
« on: July 23, 2018, 03:58:49 pm »Does the bidirectional option need to be enabled in order to receive the now playing data from the automation software (station playlist)?
Posted by: Jan
« on: July 22, 2018, 11:32:38 pm »When you turn off the Bidirectional option, you always get no error. Also with no encoder connected.
Posted by: w0kie
« on: July 21, 2018, 11:31:01 pm »Computer number 3 results according to a friend who ran the communication test: "When I turned off Bidirectional and Auto speed detect it no longer gives errors when testing."
Will his serial settings compromise the use of the rds module?
Will his serial settings compromise the use of the rds module?
Posted by: Jan
« on: July 20, 2018, 10:28:10 pm »The product was found to be functional before packing. As a manufacturer, we cover the product by warranty but we are not able to provide more services related to installation and setup of this product which is not designed for end users. Please contact us by email for return and refund.
Posted by: w0kie
« on: July 20, 2018, 12:35:51 am »Done all of that. Epic fail on computer number 2 in trying to communicate with pira approved usb to rs232 dongle. Module does work as I can see *rds* appearing on car radio display. I did note that deviation in factory setting increased from 75 to 95. Humm.
Now onto computer number 3. Could the problem be a defective usb/rs232 dongle or defective Pira null cable or (gasp) a defective Pira module or finally a defective Magic RDS?
Computer number 3 may or may not point to the problem. In the meantime is the module returnable for refund or for upgrade?
Now onto computer number 3. Could the problem be a defective usb/rs232 dongle or defective Pira null cable or (gasp) a defective Pira module or finally a defective Magic RDS?
Computer number 3 may or may not point to the problem. In the meantime is the module returnable for refund or for upgrade?
Posted by: Jan
« on: July 19, 2018, 11:45:01 pm »This should be entirely seamless.
There are several COM ports in your PC. Only one of them is the USB adapter connected to the RDS encoder. Only that COM port will work. Check this in the Device manager. Make sure you've selected that COM port in the Magic RDS Preferences, not some of others (which could be a bluetooth, IrDA, modem etc.).
There are several COM ports in your PC. Only one of them is the USB adapter connected to the RDS encoder. Only that COM port will work. Check this in the Device manager. Make sure you've selected that COM port in the Magic RDS Preferences, not some of others (which could be a bluetooth, IrDA, modem etc.).
Posted by: w0kie
« on: July 19, 2018, 10:28:52 pm »Now have installed USB 2.0 to RS232 Teragrand FTDI adapter. Then installed latest Teragrand Win10 drivers. Rebooted PC, hooked up Pira null cable from USB adapter to Pira module. Magic RDS Options/Preferences works perfectly with connection type RS232. Win 10 says FTDI adapter is working perfectly. BUT Magic RDS wizard step 1 Test says "no response from the RDS encoder." Encoder LED2 briefly lights up at module power up and then LED1 flashes in a steady pattern. Please advise.
Posted by: w0kie
« on: July 17, 2018, 05:56:27 pm »Using alternative and proven 12 V power brick. Module white LED1 slowly flashing. Still no successful connection to module using Pira wizard via "low-cost Chinese adapter based on Prolific chip." Have now ordered an FTDI adapter. I suggest that Pira make a warning about the Prolific serial adapter chip in the quick installation guide.
Posted by: Jan
« on: July 15, 2018, 08:13:33 am »Two LEDs were supplied with the module. Connect them to marked positions on the board: LED1 and LED2.
The red part is a fuse, not a LED indicator.
The red part is a fuse, not a LED indicator.