FastRad Lockout??? 2

[phonesrus]

I have a new Install with a MICS 6.1, I installed a F/R locally and programmed with it. Then I was working with a provider tech on site trying to set up access thru an IP terminal server to the F/R via the serial connection. We were trying to get the serial pinout correct to the F/R using a breakout box when after trying to connect several times, and being only partially successful the F/R stopped responding. I went back to the PC to F/R straight thru serial cable and now it will not connect at all. I get a F/R failure to connect message. I am using NRU 10.0 to connect.
?? could the F/R have failed?
?? does the F/R have a lockout provision from too many failed attempts, if so can it(will it)reset, or do I have to default it.
It is important that I get the IP to F/R setup working.

 

[curlycord]

Have you gone into F9** ?

 

[senk1s]

as far as i know there is no 'permanent' lockout - for trying the wrong password

the fastrad needs a digital station port to work
feature 9** (from a phone) should get you to admin
configure the sysID

com port - use a modem cable to the PC
Access using NRU locally

then termnial services

 

[phonesrus]

I think you misunderstood what I said, or maybe I need to expand.
I had already configured the FastRad with the SysID and had been connected with my PC and had been programming, on site, with it for 2 days.
We were in the process of using the same equipment on the same system to attempt to setup a serial connection thru an IP socket via a LAN telnet (terminal) adapter. We were using a serial breakout box to determine if we needed a straight thru or null modem connection thru the terminal adapter to the F/R. I was using NRU 10.0 all of the time.
We were having difficulty getting the DSR lead to go "hi" and when we attempted to connect we first got a response of wrong SysID (it hadn't changed), then we got an incorrect password response (it hadn't changed either), then all we got was fast rad failure to connect. I checked the F/R settings. I reconnected my PC directly to the F/R using the cable I had been using for 2 days and got a Fail to connect message continually after that.

That was my question about the lockout and/or failure. Why, even though we were messing with the pinout on the test connection, would the F/R no longer connect using the same PC, device, cable, password, and settings that I had been using for 2 days.

The main reason for this is that the installation is part of an offshore oil production platform that is under construction at a ship yard, and neither I, nor the company want to haul my butt 150 miles offshore to program a button on a phone, or whatever, when it is deployed and operational. I have several of these setups in place, but this is the first attempt with a F/R, so it is a work in progress, and I just don't understand why it quit working. When I go back to the shipyard (250 miles away), I am going to take another F/R with me. The IP terminal server is the only reliable way to connect, a pure modem dial up connection will not work across 45,000 miles of satellite connection, but serial via IP will!

 

[curlycord]

Some things to try....
Have you tried all the baud rates via F9**? I'm not too sure what rate it would use with a an IP TS.
Maybe delete the SysID in F9**
Reboot the RAD?

 

[phonesrus]

Havn't tried all the baud rates, the default IP rate is 9600, which I set on the F/R and was using for 2 days prior while programming the system, and need to use because of term server, if possible. 9600 is what I use on other sites for other equipment, unless it has direct IP.
Power cycled the rad 5 or 6 times over the course of testing the IP setup.
I deleted the NRU program and reinstalled on my laptop and re-input the sysid and password, thinking something might have gotten corrupted. I did not delete the sysid in the rad, we ran out of time because the provider tech and I both had to depart for different offshore locations for other work. He will be back on site on the 15th and will try the rad again, I installed the NRU on his pc also. We will reconviene at a later date because we have to install an additional trunk card and digital expansion module, and finish the installation and test.
What bugs the fudge out of me is why the rad will not respond to the direct serial connection from my pc anymore, something got hosed up, which is the reason for my post.
I understand that there is a NRU 10.1 out which I am trying to get a copy of now.

 

[MarvO1]

There is a RAD LOCKOUT from failed attempts, but it is for only 20 minutes then you are good to go again unless you have 3 more failed attempts, then you wait again.

MarvO said it

 

[tjcom]

if you open the RAD, you can reset the button.

 

[phonesrus]

FYI Guys:
The Release 11 NRU is available for download from the Nortel site, as both a zip file (72meg) and a Roxio Easy CD creator image file (82 meg). In addition there is an additional zip file which is apparently the "missing file" from 10.0 and earlier NRU's, at least it is marked as (missing file)