• I want to thank all the members that have upgraded your accounts. I truly appreciate your support of the site monetarily. Supporting the site keeps this site up and running as a lot of work daily goes on behind the scenes. Click to Support Signs101 ...

S3 TC-160 Issue with reading registration marks

jharler

New Member
So I recently took delivery of a new S3 TC with the Pro Pack upgrade to work alongside my F1612. I've gotten it setup and working but I'm having an issue that's making automation impossible. In GoSign, I use the provided action set for the twin workflow and it reads the barcode, successfully loads the file and successfully reads the first registration mark. However, after reading that first mark, it doesn't move the camera or the media and immediately says "This mark has already been detected." I'm using Onyx Thrive and these same registration marks are read fine by the flatbed (using GoProduce). If I manually move the camera and media to the second registration mark, it works fine from that point on. I've gone through all the options in the action set and tried various combinations of settings but I get the same message every time. I searched google, but the message it's giving me doesn't seem to be found anywhere else. I'm hoping someone has seen this before and knows what's going on.

1755008326826.png
 

balstestrat

Problem Solver
Hmm just as a workaround there might be a setting to skip marks automatically in the output macro.

Make sure you have the newest firmware installed on the cutter and Gosign as well.
 

jharler

New Member
There is an option to skip marks if they're not detected, and that option is enabled. On or off, it doesn't make a difference, I still get this message.
 

jerry369

New Member
If you are using GoSign 3.3 disabile the "Preload" flag in the Send command of the Barcode Action. It is a know defect of barcode with random marks when such an option (Preload) is selected
 

jharler

New Member
That was it. It's now working its way through a roll. Thank you! You saved me the frustration of dealing with Summa support again.
 
Top