Interesting mts2000 programming error

Mike 701 · Post by **Mike 701** » Fri Nov 01, 2002 2:58 pm

I am having a tough time reading my mts2000. When there is no cable connected, or it's connected, and the radio is off, when I goto read the radio, I get a TIMEOUT ERROR, accordingly. When everything is connected fine, I get an INTERPACKET VIOLATION ERROR. What's the story here?

Mike

Post by **wavetar** » Sat Nov 02, 2002 6:39 am

Hmmm. One thing I forgot to mention in your earlier post regarding programming the MTS2000 was to do it in DOS ONLY, not in a DOS window. What are you using to program the radio (computer & operating system), and have you programmed other radios successfully in the past? Post back with a few details & I'll try & help.

Todd

RESCUE161 · Post by **RESCUE161** » Sat Nov 02, 2002 1:13 pm

I had MAJOR issues trying to program my MTS2000 with a 386/25 MHz with 4 MB of RAM. It kept giving me time out messages and other sorted messages...
when I changed to a 120 MHz with 16 MB of RAM, I've had NO problems...
could be me, but the slower computers didn't do it for the MTS2000...

ricciticcitembo · Post by **ricciticcitembo** » Sat Nov 02, 2002 2:21 pm

its probably the ram of 4m is not enough for that software.

But i did the same as 161, and have never tried it on my"regular"
old programming computer.

I have however successfully launched and programed a Spectra with a 386/16 2m ram as well as a P-133 with 96m and have
noticed little difference if any. (I know I know, shouldn't even use the pendulum)

If i get a chance, I'll try my mts2000 on the 386 with 2m, and then
I'll know for sure. (and post my findings)

RESCUE161 · Post by **RESCUE161** » Sat Nov 02, 2002 2:25 pm

the only reason I haven't experimented with my 25 MHz is 'cause I don't have the correct RAM to add to it..

oh well, it works for what I want it to do on the 120 MHz, plus it's the laptop that I have. The other Laptop that I have is 133 MHz...

mts2000des2 · Post by **mts2000des2** » Sat Nov 02, 2002 9:49 pm

If it is an older laptop, make sure all the power saving features (BIOS LEVEL) are disabled. I had an NEC 386/25 with 8MB of RAM that I used to use for RSS and had freaky problems...even with plain vanilla DOS bootup I still kept having issues. Went into the CMOS setup and found the power save set to "auto" which the help file explained "turns off peripherals such as serial and paralell ports when the BIOS detects are not being used" well that did it. Disabled it and never had a problem.

My main programming machine for RSS is a genuine IBM PS/2 Model 56. It is a 486-SLC/2 running at 50MHz. It was built for government/industrial use, has a WELL SHIELDED case with a security lock (even shows TAMPERED from the boot screen if someone boogers with it while off!) and has 16MB of RAM, a 420MB HDD (ESDI I think) and two serial ports. Runs new and old RSS like a champ. Never had any problems. Got it for free with monitor, keyboard and all for under 10.00 at a thrift store.

Post by **wavetar** » Sat Nov 02, 2002 10:00 pm

ricciticcitembo wrote:its probably the ram of 4m is not enough for that software.

But i did the same as 161, and have never tried it on my"regular"
old programming computer.

I have however successfully launched and programed a Spectra with a 386/16 2m ram as well as a P-133 with 96m and have
noticed little difference if any. (I know I know, shouldn't even use the pendulum)

If i get a chance, I'll try my mts2000 on the 386 with 2m, and then
I'll know for sure. (and post my findings)

The minimum memory requirement for running MTS/MCS RSS is 4Mb of RAM, and even that's cutting it too close. I can virtually guarantee that's the problem for a few others who have posted in this thread. I couldn't run it on our 386/25 with 4Mb of RAM until I configured it with the DOS memory mangaer (MEMMGR?) a certain way. The later RSS runs much better on my P-120 with 32Mb of RAM

Todd

RESCUE161 · Post by **RESCUE161** » Sun Nov 03, 2002 4:48 am

The only RSS I can't run at all on the 120 is Sabr/System Saber. It will not read the radio at all... It says comm is okay, but just will not read and gives me a comm error???