• Can I use multiple actuators for same objective?
    No, you can't.  You can assign ID for each actuator and synchronize them. However,  it is for positional synchronization, not for speed.  Due to the DC brushed motor's characteristic, each actuator's speed can be varied according to mechanical assembly status and DC motor's tolerance.  If you control multiple actuators for same objective, actuators will be under overload condition due to difference of speed.  Thus, as shown below picture, control single actuator for single objective. If necessary, you can use linear bushings or linear guide for better alignment.

  • Can I use mightyZAP with PLC?
    Here is simple diagram to show how mightyZAP can be connected with PLC
    Basic concept will be as below picture.

    1 : PLC controller
    2 : Communication card (RS-485/422/232C)
    3 : Power supply
    4 : Voltage regulator (drop to 12V)

    • Apply RS-485 compatible mightyZAP (L12-XXF-X series)

    • User needs to be program the motion in PLC ladder diagram based on our communication protocol.

    • As there are many different PLC brand, please understand that we are not able to provide more pinpointing information for each brand.

    • We plan to apply MODBUS compatibility for easier PLC connection in near future.

  • What is positonal accuracy?
    It is 50μ (0.05mm) to 90μm(0.09mm) according to stroke version. Shorter stroke version has better positional accuracy. For more information, please refer to the specification chart.
  • Do I need an additional position sensor?
    No need. because mightyZAP already has a built-in position sensor (potentiometer).
  • Do you provide some SDK or motion library?
    Yes, you can refer to various API and library for C++, C#, Java, Python, Raspberry Pi and Arduino from our website.
  • Can I get feedback data?
    Sure. mightyZAP communication is based on half-duplex communication and you can currently get feedback data for position, voltage, temperature and motor operating rate.
  • Then, what is the merit / demerit points between TTL and RS-485?
    Merit point of TTL is user can easily build TTL circuitry on their own embeded board at relatively low cost comparing to RS-485. Demerit point is communication range is shorter than RS-485. (TTL : within 4m)
    Merit point of RS-485 is that they are strong against external noise and have far longer communication range.(you can only manage power loss.). Demerit point of RS-485 is that it is a bit costly than TTL when you build your circuitry as RS-485 needs to have dedicated driver IC.
    Thus, TTL is recommended for short distance applications having embeded board like medical device and robot. For most of industrial facilites, RS-485 is recommended.
  • What about communication range of TTL and RS-485 communication?
    RS-485 has far longer communication range than TTL. For RS485, it reaches several hundreds meters and you can only manage weakened power. For TTL, communication range is about 4m. Data packet including feedback data is not broken within 4m range, so use TTL for short-distance communication.
  • How about TTL communication voltage?
    3.3V or 5V are fine.
  • We sent pulse signal under PWM mode, motion is abnormal. Why is it?
    Check out if you sent pulse signal constantly (not single signal) until it reaches designated position.