SCN5 Simulator Build - The Beginning

Bernard,

any luck with the alarm code. I have had a look through the SCN doco and can not find it...

Anyways back to the wiki I go....

Cheers,
AP

Here are the officical SCN5 Alarm Codes. I tried converting an error of 70 as you described into this list and came up empty handed. The decimal 70 converted to Hex as a DWORD, QWORD, or Byte does not result in anything on this list (nor does -70). Since I am not a cryptographer, and because SirNoName is likely converting these alarm values before diasplaying them in the X-Sim UI, I will have to ask him what the code 70 actually is.

Again, it is highly likely that the issue is a missed step, overspeed or overheat, etc.. basically indicating that the actuator is overworked due to the move everything design of the sim.

As simple as it sounds, one easy way to find out your pivot point is to remove the upper section from the pivot point, and set in on the floor with a small round pipe beneath it. Then sit in the seat as you would with your legs extended and begin experimenting with different locations of the pipe. You will quickly find your target pivot area this way. At a mimimum, this will give you an indication of how close your calculations are.

70H : Movement order in RUN status bit OFF condition
If RUN status bit (bit 2) of internal status flag (STAT) is 0 condition, system will reject movement order by direct commands of a, j, m, o, and reject non-limited revolution order of v command and PTP order by Q2 command. These commands will be rejected when buffering order by h command is executed by t command.

I speculate that an actual alarm code may have been thrown causing the RUN status bit to be off, causing the actuator to reject a buffered movement and therefore throw this warning. Unfortunately, this is a remote troubleshooting via forum effort, and X-Sim does not keep a log of all alarms and warnings thrown. What we are seeing is the last warning.

Based on the sim design, it is reasonable to believe that the actuators are being overworked, but I’m empty handed at the moment with regard to absolute proof.

@SirNoName - Is it possible in future versions to either log these errors, or only report the first alarm and not report subsequent warnings?

@Apsydsim - Does this warning only occur on one actuator or both. If it only occurs on one, please try swapping the troubled actuator to the oppiosite side of the sim using the wires from the non-troubled actuator and let us know what happens.