I would just point out that MTH engines have changed over the years and it's good to know which item you are dealing with. Any with command inside, need a charged battery (if equipped) to function correctly.
Start by connecting the system to a small test track might help you get going easier. Make sure you have proper power to the TIU and the red light comes on. Make sure the remote talks to the TIU. Don't change TIU or remote addresses until you understand how and why.
The system will display messages, and they are generic. Each will help point to a problem and help figure out any issue. It takes some detective work when there's an issue. After much use, the messages will make better sense in what's going on.
The members here can help in each step so post anything happening as you go. They may ask for all the specifics to help them understand the issues.
I got help here right away back when I started. I then dove in to learn more about why I was having issues. Learning about the signal propagation was a big one. An easy fix is to not let the signal double back on itself for example. A loop of track needs to be broken in one spot to prevent this. It just requires a break in the hot center rail.
Keeping the polarity correct is a good basic rule. TMCC/ Legacy connects to the outside rail. DCS connects to both and must be correct to get the 2 way communication it needs.
Putting too much load on a single channel of the TIU can cause issues. So can having TMCC/Legacy equipment on powered DCS rails.
I could go on for the length of Barry's book here. I'm just trying to point out some reasons why your previous attempt at DCS may have failed.