I am using ONYX RIP-Queue (version 18.0) and its CUT-server with a Summa cutter (S2 class) and I have noticed a problem that makes it impossible for my cutter to read the barcode. When I print the barcode is on the paper, however the number next to it is not the same as the number that appears on my computer. There is only one number that is different. The number in the CUT-server shows a 0 and the number on the paper is a 6. I have no idea why that happens. I tried to rename the file and the cutter started cutting but as I expected it was making a mess.
-
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 ...
Barcode number and file name are not matching
- Thread starter Maniko
- Start date
balstestrat
Problem Solver
And what is the code on the other end? Is that matching?
If I remember correctly correctly that's how it's supposed to be. That way it knows in which way the work is aligned. It will still find it with the barcode if you have everything else working properly.
If I remember correctly correctly that's how it's supposed to be. That way it knows in which way the work is aligned. It will still find it with the barcode if you have everything else working properly.
The code on the other end replaces 6 with a 9 so it's not matching either.
balstestrat
Problem Solver
Okay but that's fine, it just tells the way it's put in. Only the end has to match. So if your barcode is not working you have some other issue going on.
White Haus
Not a Newbie
When we send files down through Onyx Thrive / Cut Server to our Summa F, the file number ends with either 0 (front/beginning of the job) or 5 (back/end of the job. I'm assuming this is based on which cutter it is being sent to?
When we send to our Summa S I can't remember how it treats the numbers but there is always a little arrow pointing to the front/beginning.
When we send to our Summa S I can't remember how it treats the numbers but there is always a little arrow pointing to the front/beginning.
Saturn
Your Ad Here!
I would email/call Onyx they're pretty responsive and aware of some Summa issues. My Summa S2 and Onyx (ver 20 and 21) both gave me similar issues and I was told by Onyx support to specifically roll back to 19 and use a driver patch/update they gave me the link for too.... Supposedly ver 21.1 fixed this.
Is this a new problem, or are you just setting up this process for the first time? How does the actual barcode itself look? When I had similar issues the barcode itself would appear to have issues, and printed obviously differently from a known good barcode.
You should have two barcodes, one at the top and one at the bottom, one with the 6 and one with the 9, as mentioned above it's to differentiate front from back.
Is this a new problem, or are you just setting up this process for the first time? How does the actual barcode itself look? When I had similar issues the barcode itself would appear to have issues, and printed obviously differently from a known good barcode.
You should have two barcodes, one at the top and one at the bottom, one with the 6 and one with the 9, as mentioned above it's to differentiate front from back.
