Handle undocumented values in StatInfoText veneer.

[MRIIOT]

fanuc-driver/fanuc/veneers/StatInfoText.cs

Lines 102 to 117 in abe26bc

	var current_value = new
	{
	mode = new
	{
	automatic = _autText[input.response.cnc_statinfo.statinfo.aut]
	},
	status = new
	{
	run = _runText[input.response.cnc_statinfo.statinfo.run],
	edit = _editText[input.response.cnc_statinfo.statinfo.edit],
	motion = _motionText[input.response.cnc_statinfo.statinfo.motion],
	mstb = _mstbText[input.response.cnc_statinfo.statinfo.mstb],
	emergency = _emergencyText[input.response.cnc_statinfo.statinfo.emergency],
	alarm = _alarmText[input.response.cnc_statinfo.statinfo.alarm]
	}
	};

So basically StatInfoText just takes the integer value from Focas call and gets the string representation based on index. In this case automatic:5 would have become automatic:TeachIN. The original exception points to an index in one of the arrays that does not exist. We just don't know which one or what the value was.

2021/07/27 12:21:59.191|ERROR|[m9_doosan_puma] Collector sweep failed at segment PATH. System.IndexOutOfRangeException: Index was outside the bounds of the array.
at l99.driver.fanuc.veneers.StatInfoText.AnyAsync(Object input, Object[] additionalInputs) in /home/ts/git/c10n/fanuc-driver/fanuc/veneers/StatInfoText.cs:line 102

1. Change it back to await Apply(typeof(fanuc.veneers.StatInfoText), "stat_info");,
2. turn up the logging in nlog.config <logger name="*" minlevel="Trace" writeTo="fileTarget,consoleTarget" />,
3. and post driver.log after the exception.

This will give us the info needed to troubleshoot, because we'll get the raw output from Focas before it hits the StatInfoText veneer.

fanuc-driver/fanuc/platform/StatInfo.cs

Line 33 in abe26bc

_logger.Trace($"[{_machine.Id}] Platform invocation result:\n{JObject.FromObject(nr).ToString()}");

[MRIIOT]

Look at documented differences in cnc_statinfo2 and cnc_statinfo.