Hi fellow automators,
I have come across this issue in FluentControl:
with this kind of workflow:
I don’t understand the reason why it doesn’t want to accept the offset values (I have tried just with numbers 0 and 1, works only when both offsets are 0).
Strange thing is that I use this offset pickup already in other script and there it works.
Any ideas what could be the cause of this behavior? At this point I am quite desperate, because this should work, but for some reason doesn’t.
Thank you for the help!
how many “varTotalLoops” are being initiated ??
could be that the loop is trying to offset to a row beyond the tip box Y row range
Maximally 2, you are right that in the screen above this would result in a problem. I have tried to put there varCurrentLoop -1 which should do the trick but it still gives errors whenever there is value 1 passed to either row or column field.
If you add another tipbox, MCA96_50[002], does the error persist?
Thank you for insights. I tried it on instrument live with both values set to 0 - which doesn’t raise any compile error - and have found a source of the issue.
The tip box was oriented 180 degrees and not 0. Fluent apparently also mirrors the tip pickup command, but not the increment change in the row/column offset. So, with both values set to 0, it picked tips from Q4.
So…at the end just a stupid error in initial deck setup.
But certainly a valuable lesson!
1 Like
