End of Product Life Information

Model Status No Stock date Alternative Upgrade Path
MC206X (P136) Obsolete. No Stock MC405 MC206x/MC405 comparison.
MC302-k (P190) Obsolete. No Stock N/A
MC302X (P192) Obsolete. No Stock MC403 MC302X/MC403 comparison
Euro205x (P151) Not recommended for new projects. Q2. 2020 Euro404 / 08 N.B. NOT Pin compatible.
Euro209 (P159) Not recommended for new projects. Q3. 2027 Euro408 Is Pin compatible.
PCI208 (P180) Spares only with limited warranty; ie. Repair only. <15 in stock. N/A
MC224 (P170) Obsolete. No Stock MC664 MC224/MC464 comparison.
MC464 (P860) Not recommended for new projects. Q4. 2019 MC664 Same case and add-on modules as the MC464. 99% program compatibility.
Euro205 (P150) Not in production. No Stock. Euro205x
MC206 (P135) Not in production. No Stock. MC405
MC216 (P140) Not in production. No Stock. MC664
MC204 (P130) Not in production. No Stock. MC664
MC202 (P165) Not in production. No Stock. MC403
MC2 (P110) Not in production. No Stock MC664


When upgrading a system to a new version of TrioBASIC and / or a newer controller, there are likely to be small changes required.  Whilst every effort is made to maintain backward compatibility of the TrioBASIC programming language, you may need to consider the following.

• The faster processor speed may have an impact on the way multi-tasking programs interact. 

• There may be some commands which now require extra parameters.

• The original program may have been written using “illegal” command options that are no longer allowed.

In the majority of cases, there will be an alternative command or alternative way of structuring the program which will allow the programs to run under the new system software.

Such changes are usually minor. In almost all cases the operation of the fundamental motion software is identical. 

Experience shows that in about 98% of upgrades, there are no changes required to the programs.