TrioPCMotion will not connect

TrioPCMotion will not connect

For an MC403, MC405 or MC464 that refuses to allow a TrioPCMotion ActiveX connection, check that the REMOTE program is not disabled in the flash memory.

Look at the value in REMOTE_PROC. It is a system parameter that is stored in Flash in the MC403, MC405 and MC464. Here is what the TrioBASIC help says:
REMOTE_PROC Value:
-1 : Use the highest available process (default)
-2 : Turn off the Active X processing. No connection will be possible when set to this value.
0 to max process : Run on defined process

So if set to -2 then the ActiveX will never connect.
In most other MC4/5/6 Motion Coordinators, the REMOTE_PROC setting must be in MC_CONFIG and is not stored in Flash.

    • Related Articles

    • MC_CONFIG vs Flash parameters

      All Motion Coordinators store the IP_ADDRESS, IP_NETMASK and IP_GATEWAY in Flash memory.  So there is usually no need to add them to the MC_CONFIG. There are some differences with other system parameters. MC4N-ECAT, MC4N-RTX, MC6N-ECAT, Flex-6 Nano ...

    • AN-365 TrioPCMotion ActiveX Heartbeat

      To add a higher grade of reliability at our Trio PC Motion ActiveX control, a heartbeat function has been added to the component. This document explains how this heartbeat works

    • AN-419 TrioPCMotion TCP port

      Motion Coordinator firmware version 2.0300 has the ability to open a TCP server port on Ethernet. This document describes a program that can be run in Visual Basic to communicate with the Motion Coordinator. Requires TrioPC Motion ActiveX V2.20.5 or ...

    • AN-304 Adding TrioPC to Visual Basic

      A connection between a Windows PC and a Motion Coordinator can be made with an ActiveX component called TrioPC Motion. The ActiveX component must be added to the Visual Basic project. This document describes this step by step. The example is based on ...

    • CONNECT command

      Question: I use the CONNECT command and when I change the ratio the encoder slave doesn't move in the axis. I see the pulses of the master encoder move. This is the code: BASE(0) ' slave (following) axis SERVO = ON UNITS = 4000 DEFPOS(0) BASE(2) ' ...