• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

Serial port pins?

N

NSRadio

This may be a very bad idea - but I'd appreciate feedback from anyone who's tried anything similar....

Our STL only has 1 data channel, but I need to get 2 data sources to our tower site: 1 for remote control functions, the other for RDS.

The remote control only needs 2 pins of a 9-pin RS-232 connector, and the RDS unit needs 3. If I made a cable connecting the appropriate pins to each device and sent it through the RS232 data channel on our STL, is there any reason I couldn't get both sources to come through?

As I understand it, each pin is its own seperate channel, so it shouldn't matter what gets sent through it as long as it is routed to the right place on the other side.

Any feedback is appreciated!
 
>If the STL operates as you say - the logic you put on the studio pins comes out on the same pins at the transmitter regardless of the baud rate, parity, etc. - then it may work assuming the data rate of the STL can handle the data rate of your RDS signal. I don't think you will blow anything up by trying it although a call to the STL manufacturer to see if it will work may save you the trouble. If you are just sending a fixed RDS message (like call letters) you can put the encoder at the transmitter.
 
> >If the STL operates as you say - the logic you put on the
> studio pins comes out on the same pins at the transmitter
> regardless of the baud rate, parity, etc. - then it may work
> assuming the data rate of the STL can handle the data rate
> of your RDS signal. I don't think you will blow anything up
> by trying it although a call to the STL manufacturer to see
> if it will work may save you the trouble. If you are just
> sending a fixed RDS message (like call letters) you can put
> the encoder at the transmitter.
>
What kind of STL are we talking about?

Digital or analog?

There are analog STL's with 9 pin D connectors but they ain't serial ports.

And a digital STL's that is supposed to have only one data channel probably does have only one data channel, even if it has a 9 pin wired with standard serial port connections.
 
Thanks once again for the help ncradioeng!

The STL is a Moseley DSP 6000 - digital. It does have only 1 data channel, but I am hoping to use that one channel to convey info from 2 devices by using available pins....

I will post how it works out for anyone else who may have use for this method.

Thanks again!


> What kind of STL are we talking about?
>
> Digital or analog?
>
> There are analog STL's with 9 pin D connectors but they
> ain't serial ports.
>
> And a digital STL's that is supposed to have only one data
> channel probably does have only one data channel, even if it
> has a 9 pin wired with standard serial port connections.
>


> > >If the STL operates as you say - the logic you put on the
>
> > studio pins comes out on the same pins at the transmitter
> > regardless of the baud rate, parity, etc. - then it may
> work
> > assuming the data rate of the STL can handle the data rate
>
> > of your RDS signal. I don't think you will blow anything
> up
> > by trying it although a call to the STL manufacturer to
> see
> > if it will work may save you the trouble. If you are just
>
> > sending a fixed RDS message (like call letters) you can
> put
> > the encoder at the transmitter.
> >
 
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom