atcomsystems.ca/forum Forums Other TDM Phone Systems Executone-Isoetec Telephones & Systems Backup and Communication

I want to backup the system (IDS 43/84 8.1) so I login, Press D Press S and the system says 'Ready to save'

In Procomm for windows I select 'Receive File' and it says I am to receive Xmodem.

When I put in the file name, there is a time out (as I would expect) then a bunch of 'Packet Type Error's, till procomm aborts and the backup file is empty.

The communication is set to 9600 N 8 1. I've tried Both Duplex Modes, various buffer sizes, software control.

Nothing seems to work.

Try at lower baud rate. 1200 or 4800 should work.

Good Luck!!

I tried changing my baud rate, but the system does not respond except at 9600 Baud. It is easy enough to change the Baud used in Procomm, is there a way to tell the system what Baud to use or to search for a connection speed?

The system baud (local connection right?) is set up on the B screen.Does programming at 9600 baud work OK?I've never changed the speed down for a problem like that.If you change the local baud rate I think you will have to try it a step at a time and reset procomm each time to the new baud rate.

I went to System Programming and the Port setup showed:
Port 01* Installd Y
Speed 9600 Protocol = NONE
Printer 0 Computer Port N Type 000
SMDR N Incom N Local N Long Dist N

I am connected directly to the board. When I try to change the 9600 (or the Protocol) all I get are beeps. I am at access level 8. I have pressed all the keys on the keyboard and number pad, both shift and un-shifted excluding A-Z and a-z.

Should the protocol be set to XMODEM?

I think to change the baud rate you press I to increment the baud rate and D to decrement it.I really don't think the protocol should make that much of a difference.

You are on a active port,so it will beep at you. If you change the baud rate it will kick you out. Then adjust your baud rate in Procomm.

I sually only get the timeout problem when backing-up remotly.

Good Luckl!!

Now I really messed the system up.

This is what I did.
1) tried backing up at 4800 Baud
2) tried at 2400 Baud
3) tried at 1200 Baud
4) turned off all other processes and tried
( all failed with 'Packet Type Error')
5) set the system back to 9600 Baud

So I thought (something I shouldn't be doing), "well maybe it is the Protocol, you said probably not, but I don't know anything so I probably know better"

I went to it and pressed I
It changed to 'X-ON'
So..I wanted to see the options and pressed I again (I should have pressed D to get back where I was)
Now I get no response from the system.

I have no idea what my setting should be to even see the screen or put in the password.

I figure maybe it went to a hardware protocol and the simple connection I have doesn't have enough wires to carry whatever signals.

I'm wearing my dunce hat today? <

If I get back in I'm going to try using a laptop instead of one of the servers, I think I saw our Tech guy do it that way occationally.

So, at this point the questions would be
1) Any way to get the connection restored
2) Any settings I can put into procomm to connect
3) Any alternate route into the system
4) Should I wait a period of time and see if it resets itself
5) Should I burn incense and utter an incantation

About 4 inches above your RS232 connection.. there is a jumper -'J26' move it to the left one pin-(so that you're on the two left pins)...then press the red reset button in to the right of that..hold it in for a few seconds..you might go ahead and power cycle the system after doing this...then move the jumper back..
..and yes, I think you should try this with your laptop..you might have some kind of network issue(s) that's interfering with the backup. I had timeout issues before and then it worked later on without any changes..I left the baud at 9600...even for the restore..which I was told you should do at 4800.

oops... This goes without saying..my instructions were for a reset/default..which is what it sounds like your going to need to do to get back into the system after your fiasco..I'll give you a email here in a sec. and I'll see if I can get into it remotely for you..before going the other option.