AMC-AASD15A servo controller

Hi @Thanos I'm building a gseat and I have a calibration problem with an actuator. I also have a 3dof platform with 3 actuators that work well, no calibration problem. I selected 3dof+tl+surge from the menu. The actuator that causes me problems is on output 4 of the AMC. The actuator works well except that when I cut the power supply (120v.) and reconnect the actuator it only turns 3 turns in one direction (without calibrating). On the other hand, if I connect it to output 5 of the AMC, it works correctly, it calibrates and go back in its place.

Have you updated the firmware to the latest version v2.26 fix0?
I just tried to replicate the issue, but all works as intended. Powering off and the powering back on the servo on DB25 port 4, fully retracts the actuator to calibrate and then moves to 50% parking position correctly (3dof+tl+surge setting). Did you try with another DB25 cable in case the one you are using is damaged?

Also make sure to restore defaults in case some other setting you did causes conflict on the park function. After loading the new firmware, hold down the 'EXIT' button on the Thanos controller. While continuing to hold down the 'EXIT' button, press and release the "RESET" button to restore the default parameters. Now release the 'EXIT' button. This is needed to remove any incorrectly stored values from the epprom from the previous firmware as sometimes these get updated too. (Click here for video).

For a detailed guide to update the firmware correctly, please refer here:
https://www.simracingstudio.com/forum/motion-profiles-actuator/thanos-firmware-update-guide

Hi, sorry for the delay , i was away for works.

Today I connected a fifth motor and the problem moved to output #5 and now #4 works fine.

What I suspect... It is as if a virtual calibration switch closes as soon as I turn on the power and so the motor moves immediately by 50%.

Later in the day I replaced my AMC board with my Flight sim board and everything works fine as expected. Then the problem comes from the AMC board themself.

I will try it again later by re-installing the firmware.

Maybe your actuators leadscrew slider have resistance and needs lubrication. I'd suggest to check if you can rotate the leadscrew by hand without resistance.

And check if the DB25 male-male cables are shielded type. EMI could cause false signals during the calibration if not. Although the AMC-AASD15A controller ignores torque signals when not in calibration mode, an EMI spike could send a wrong pulse and calibrate prematurely.

You can see what I mean here where the sensor used instead of torque has a LED indication:

I removed the engine, it is free.

I tried with an other DB25 cable but nothing.
Like i said everything works well with my other AMC board.

I downloaded again the latest firmware .

I'm pretty sure the problem is with the AMC board. I took the board alone and a single motor, I connect the DB25 cable alternately on each output 1-6 and at each output I see the "C" for calibration before the "P" of the park except at the output 5 that i see immeditely the "P" .

i restored it severals times , i selected "all axis parked" to be sure. I am run out of idea.

Hi,

Some photos of the AMC-AASD15A so I can see its version and manufactured date, would help.

The issue you described could be defect on the PCB, or just dirt deposit interacting with solder paste residue that maybe was not well cleaned during production.

If anything, you can always send us privately photos or provide more information that could help assist more, with possible repair or replacement if needed. Use our contact form here.

Thanks
Thanos

I applied but was unable to attach my photo and video...


https://www.youtube.com/shorts/KcegMm84-hQ

I can't see the video, its private, perhaps if you could set it as unlisted...

I'll be answering back to your email regarding replacement perhaps. I see you may have two of these controllers? Both show same issue or just this one?

Thanks
Thanos

Thanks for your help, it's appreciated

Hi Cubexxx. I am trying to use a 80st M02430 to do a seatbelt but I am strugling :/ I tried to send analog signal from an arduino Due, and also basic pwm signals from an Arduino Uno without sucess.
With the arduino Uno, the motor remains idle until we go above analogwrite(128). From there the motors starts to spin at the same speed even if the values are higher...
The wiring is as follow :
AASD - Arduino
COM(9) - GND
Vref(25) - A0
AGND(13) - GND

PN002 is 0 (torque mode)

any idea ?

PWM is not analog... when you use analogwrite, its actually sending PWM pulses 0 or 5v...

Even with the Due ? I tried analogWrite(DAC0,i); (with i from 0 to 4000).

The Due DAC is unbuffered analog voltage low impedance. To interface to a circuit like a servo drive you NEED Op-Amp buffer circuit!!

Would you have an amp to recommend @Thanos ? @cubexxx what are you using ?

I wouldn't know, depends on what impedance the servo drive has and the voltages. If it needs negative voltage for negative torque (reverse direction), it becomes complicated.

A few years back I had to build a -11v to +11v circuit for a servo driver, for analog speed control for the old AMC controller, which could be possibly be used for torque as well. These rail to rail op-amp that I used back then are not in stock anymore (victims of the chip shortage as it seems):

http://motionsim.blogspot.com/2018/02/using-linear-ac-servomotor-actuators.html

strange... there is no info in the documentation on what the signal should be...
I did test with a MCP4725 today but without any sucess...

I did not use any amp. The servo driver manual shows an input impedance of 10k for the analog voltage input (pin 25) and I read somewhere that the due can deliver 3mA at the dac output, so that's enough (voltage range of the due dac is 0.55V - 2.75V). Also you can use driver params Pn189/190 to map that dac output range to the desired torque range. Of course you can use an op-amp to extend the range, but I could achieve 0-max torque without an op-amp (example of using an op-amp is shown here )

Thanks !
Do the wiring seems ok to you ?
AASD - Arduino
COM(9) - GND
Vref(25) - A0
AGND(13) - GND

And the code ?
void setup() {
delay(2000);
Serial.begin(9600);
analogWriteResolution(12);
pinMode(DAC0, OUTPUT);
}
void loop() {
for (int i=0; i<4000;i++){
analogWrite(DAC0,i);
Serial.println(i);
delay(2);
}
for (int i=0; i<4000;i++){
analogWrite(DAC0,4000-i);
Serial.println(4000-i);
delay(2);
}
}

EDIT : i just tried to control the servo with a potentiometer, and it does work

I did more tests. It looks like it was missing a resistor... Now the function to read the serial from FlyPt doesn't seem to work... I am using the same code as for my actuators :

Code:

void SerialReaderC() {       // This function is the work of Sirnoname. FlyPt output : P<Axis1a???>, Data bits : 10 bits, Parity : None, stop bits : 1
  while (Serial.available())
  {
    if (buffercount == 0)
    {
      buffer = Serial.read();

      if (buffer != 'P') {
        buffercount = 0; // "P" is the marquer. If we read P, the next data is Motor1
      } else {
        buffercount = 1;
      }
    }
    else   //  if(buffercount>=1)
    {
      buffer = Serial.read();
      commandbuffer[buffercount-1] = buffer; // The first value next to "P" is saved in commandbuffer in the place "buffercount"
      buffercount++;
      if (buffercount >= 3) {
          m1Target = commandbuffer[0] * 256 + commandbuffer[1];
          buffercount = 0;
        break;
      }
    }
  }
}

Is there something specific to the Arduino Due ?

Back to topic, I was asked if you need to power off the servo drives before connecting to AMC-AASD15A controller, or which order you need to power up things... It doesn't matter. Automatic hotplug detection and activation prevents problems, as the motors will move only when all participating systems are ready: