Nucleus Paging Tx / Dumb Terminal Connection
Moderator: Queue Moderator
Nucleus Paging Tx / Dumb Terminal Connection
Nucleaus Paging Transmitter has a way to interface to an dumb terminal
using the com port in the back. I poured through the manual and setup
everything as required, but I still can get the terminal or hyperlink
to communicate. I can toggle the modem selection in the front panel
and see the init string sent out from Nucleus to the dumb terminal (manual indicates, this to check connectivity)
But, no luck. I can't communicate via the dumb terminal. Has anyone else tried this and succedded.
Thnx.
Akash
using the com port in the back. I poured through the manual and setup
everything as required, but I still can get the terminal or hyperlink
to communicate. I can toggle the modem selection in the front panel
and see the init string sent out from Nucleus to the dumb terminal (manual indicates, this to check connectivity)
But, no luck. I can't communicate via the dumb terminal. Has anyone else tried this and succedded.
Thnx.
Akash
I had a "standard" controller in my 900 MHz Nuke, which has a DB9 connector on the front. That's the one I used. I set my Win95 HyperTerm to 19,200 baud, 8 data bits, no parity, 1 stop bit (8, N, 1). Much of the stuff that goes out of that port is plain text, but a few screens assume a VT100 emulation in HyperTerm, as they send out some escape sequences to clear the screen and position the cursor. I also had to make my own cable that cross-connected pin 1 to pin 4, and pin 2 to pin 3 at each end. There are more details in the Nucleus article on repeater-builder.com in the Motorola section.
Even though my SCM contained a modem, I never did anything with it, nor the connectors on the back of the chassis.
Bob M.
Even though my SCM contained a modem, I never did anything with it, nor the connectors on the back of the chassis.
Bob M.
Yes, mine is a Nucleus II, but the N-2 with the advanced controller doesn't have a front panel DB9 connector, if I recall. So that could be the difference too.
I found that the communications speed in HyperTerm wouldn't always change unless I exited and restarted the program. Quite annoying. This may be a problem in Win95 and Win98SE versions only, however. That might have been fixed in a newer version.
I don't have any documentation on the Nucleus I.
Bob M.
I found that the communications speed in HyperTerm wouldn't always change unless I exited and restarted the program. Quite annoying. This may be a problem in Win95 and Win98SE versions only, however. That might have been fixed in a newer version.
I don't have any documentation on the Nucleus I.
Bob M.
If I am correct, just cross connecting the two pairs is sufficient, no need to worry about CTS and RTS.
just wanted to line my ducks up before I go try it out.
thnx.
just wanted to line my ducks up before I go try it out.
thnx.
Last edited by akash1 on Wed Jul 05, 2006 3:43 pm, edited 1 time in total.
I don't see a signal ground on your pinouts.
Try full cables. Let me know I still want to hook up my Moscad system.
Shield N/C 1
Transmit Data 3 2
Receive Data 2 3
Request to Send 7 4
Clear to Send 8 5
Data Set Ready 6 6
System Ground 5 7
Carrier Detect 1 8
Data Terminal Ready 4 20
Ring Indicator 9 22
or a full null modem
Recieve Data 2 2 Transmit Data
Transmit Data 3 3 Recieve Data
Data Terminal Ready 4 6+8 DSR + Carrier Detect
System Ground 5 7 System Ground
DSR + CD 6+1 20 Data Terminal Ready
Request to Send 7 5 Clear to Send
Clear to Send 8 4 Request to Send
Try full cables. Let me know I still want to hook up my Moscad system.
Shield N/C 1
Transmit Data 3 2
Receive Data 2 3
Request to Send 7 4
Clear to Send 8 5
Data Set Ready 6 6
System Ground 5 7
Carrier Detect 1 8
Data Terminal Ready 4 20
Ring Indicator 9 22
or a full null modem
Recieve Data 2 2 Transmit Data
Transmit Data 3 3 Recieve Data
Data Terminal Ready 4 6+8 DSR + Carrier Detect
System Ground 5 7 System Ground
DSR + CD 6+1 20 Data Terminal Ready
Request to Send 7 5 Clear to Send
Clear to Send 8 4 Request to Send
Tried the option "null modem with full handshaking #2" as listed
in
http://www.virtual-null-modem.com/help/ ... matics.htm
still no luck, I am going to try out one at a time and see what is going to work. Also, if this matters. I check the papers on the nuc we have. It has
an internal smart modem option. I can't toggle "Smartmodem/No modem" as given in the OPT-2 config steps in the manual.
Does this matter ? I am running out of options, I will keep trying. I really want to get this working.
thnx
Akash
in
http://www.virtual-null-modem.com/help/ ... matics.htm
still no luck, I am going to try out one at a time and see what is going to work. Also, if this matters. I check the papers on the nuc we have. It has
an internal smart modem option. I can't toggle "Smartmodem/No modem" as given in the OPT-2 config steps in the manual.
Does this matter ? I am running out of options, I will keep trying. I really want to get this working.
thnx
Akash
On my Nucleus with the standard controller and NIU, remove the front panel, pull out the NIU (the right circuit board), and the modem was on two 30-pin plug-in boards at the top edge, just like old computer memory board. Spread the metal tabs on each side of the socket, tilt the board, and it comes right out.
The modem was split among two boards; one had a small battery mounted on it, the other has a small transformer. I think there was some lettering on them that led me to believe it was a smart modem, possibly made by Dallas Semiconductor.
After you remove it, I don't know if there will be any software settings you'll need to tell the station that there's no more modem inside.
Bob M.
The modem was split among two boards; one had a small battery mounted on it, the other has a small transformer. I think there was some lettering on them that led me to believe it was a smart modem, possibly made by Dallas Semiconductor.
After you remove it, I don't know if there will be any software settings you'll need to tell the station that there's no more modem inside.
Bob M.
Ok, got it working..
My controller had nothing similar to the one you had described. Here are the sequence of steps.
1. Pulled the controller out.
2. Modem board is a 2" x 2" board with a SIP header and 1/2" nylon stand offs.
* removed it
3. Used a standard 25pin to 9 pin null modem * NO LUCK*
4. Noticed a Jumper in th center of the area, where the modem was located. (3 pin SIP).
5. Moved the jumper to the alternate location
6. typed "connect 1200" & ASCII from the terminal ** CONNECTED **
Well, I was brave to do this. Hopefully I pulled the right board out and switched the jumper correctly. [no docs
]
Tried paging some pagers, the continute to work.
Thanks.
My controller had nothing similar to the one you had described. Here are the sequence of steps.
1. Pulled the controller out.
2. Modem board is a 2" x 2" board with a SIP header and 1/2" nylon stand offs.
* removed it
3. Used a standard 25pin to 9 pin null modem * NO LUCK*
4. Noticed a Jumper in th center of the area, where the modem was located. (3 pin SIP).
5. Moved the jumper to the alternate location
6. typed "connect 1200" & ASCII from the terminal ** CONNECTED **
Well, I was brave to do this. Hopefully I pulled the right board out and switched the jumper correctly. [no docs

Tried paging some pagers, the continute to work.
Thanks.