M66 Breaks DEBUG in ocode sub

Hi everyone,

I have been chasing a rather strange behaviour the past two nights.

Let's take a macro that has been stripped of everything useful.
If I launch this as a part of my M6 remap, I will get a DEBUG Message "A test message before we launch M66" and then nothing.
However, if I remove the M66 the second DEBUG will display. The same holds true in more complex macros. Once I use an M66 no further "debug" messages will be triggered. However, Messages using "print" will be sent to the terminal.

I guess I am missing something, but my google-fu failed me miserably.

Any ideas?

BR
Guido


I am on:
Debian 9, Buildbot Master, Gmoccapy 3

Hey Tommy,

E0 is indeed connected and will return a signal. The print statement (print, value M66 #5399) confirms this and yields the correct value.

It is worth pointing out that in a more complex macro which has multiple lines of movement after M66 all of these movements are executed. This is sort of why I am lost:).

Thank you. I'll have a look into this. It does, however, make me wonder a bit. Isn't M66 on an analog pin just doing an instantaneous read without waiting for a change?

In the specific case, the pin will not change, as it has been set prior to executing the macro and is used to get a correct pocket number as a hotfix for the current dilemma with pocket number handling.

If I use M66 E0 L0 it doesn't change the behavior either.

Hey Tommy,

I guess I did miss it. Till now I still don't get which specific aspect you re pointing me too.

Never the less, I have since made some progress. I added L0 to M66 E0. I might have missed that last night, though I thought I had tried that.

There is a another relation that I worked out. In the large macro there are numbers if conditionals which, when true, are supposed to stop the macro. I had used M2 commands at those places. I have since changed all those M2 to o<number, e.g. 110> return [999] commands. Since then, the entire macro seems to work just fine.