Bit Depth does not Match.

[shasta]

Keep getting Bit Depth does not match on different bits and different projects.

What exactly does not match?

Ive asked about this before but have been unable to solve the mystery but its really getting old.

[shasta]

For Clarity, its the standard carving bit that came with the machine and the standard cutting bit, does it on nearly every project, if i tell it to continue it will barely touch the board when cutting. Its a year old CX machine. Sometimes re-uploading the project helps.

[shasta]

I'll go with more info, the bit is the same bit that carved the last thing, havent changed it out, project asked for vector bit, which im using the same bit for vector and carving, it checked out fine for vector bit, then when it asked for the exact same bit for carving bit it gives the error.

[mtylerfl]

That's odd. Are you inserting the appropriate bit at every prompt? (You know, the redundant insertion of each bit that some folks skip during initial project setup at the machine).

Typically, you will be prompted to insert the Cutting Bit first...the machine homes and remembers the bit length. Then you are prompted for the Carving Bit. The machine homes, then the carving should begin. After the carving, you are prompted to load the Cutting Bit. The machine will home and if the bit length doesn't match the cutting bit length stored in memory, you will get the "bit depth doesn't match" error.

Some people ignore the bit swapping at the beginning of a project...they just leave one bit in the collet for all bit load prompts. of course this means they allow the bit depth error to occur and just press "enter" to continue. That usually works, but I do not recommend that procedure, because I think it's asking for trouble if an operator is not paying close attention during the project run.

So, if you are loading your bits as prompted for, then it has to be something else causing the error. Check your Z-truck travel and bearings. If the Z-depth differs between the stored memory depth and the real-time depth measurement, it is possible something is interfering with the z-truck travel and yielding different readings at different times. A dirty or frozen bearing, mis-adjusted z-truck bearings, rubbing of the z-truck against the mount, z-belt going bad or stretching, can all be things to investigate.

[shasta]

That's odd. Are you inserting the appropriate bit at every prompt? (You know, the redundant insertion of each bit that some folks skip during initial project setup at the machine).

Typically, you will be prompted to insert the Cutting Bit first...the machine homes and remembers the bit length. Then you are prompted for the Carving Bit. The machine homes, then the carving should begin. After the carving, you are prompted to load the Cutting Bit. The machine will home and if the bit length doesn't match the cutting bit length stored in memory, you will get the "bit depth doesn't match" error.

Some people ignore the bit swapping at the beginning of a project...they just leave one bit in the collet for all bit load prompts. of course this means they allow the bit depth error to occur and just press "enter" to continue. That usually works, but I do not recommend that procedure, because I think it's asking for trouble if an operator is not paying close attention during the project run.

So, if you are loading your bits as prompted for, then it has to be something else causing the error. Check your Z-truck travel and bearings. If the Z-depth differs between the stored memory depth and the real-time depth measurement, it is possible something is interfering with the z-truck travel and yielding different readings at different times. A dirty or frozen bearing, mis-adjusted z-truck bearings, rubbing of the z-truck against the mount, z-belt going bad or stretching, can all be things to investigate.

heres the insanity of it: First try it asked for vector bit, which is the bit i had in the machine, checked out fine, then it asked for carving bit, which is the same bit I have selected so I left it in and it gives error, never got to it asking for cutting bit. Turn machine off, pull card, put it back restart machine, start project again, this time it asks for vector bit, checks out good, then cutting bit checked out good, the carving bit, this time no errors and its carving fine right now. Its so perplexing. I think it just likes messing with me.

[aokweld101]

I thought that it's like getting on a boat..last one on, is the fist one off.. you do know that it starts with the last opperation that your project is asking for, if you are reinserting the vector bit and useing the hose that comes with carvewrite your depth can change by how much pressure you insert the bit with and will ask you to refind...

[lynnfrwd]

Are you watching it touch slap plate?

[shasta]

yes it touches and still gives the error, just tried another carve and the board kept rolling until the bit was off the end, not sure what thats about but its a first

[mtylerfl]

I'll go with more info, the bit is the same bit that carved the last thing, havent changed it out, project asked for vector bit, which im using the same bit for vector and carving, it checked out fine for vector bit, then when it asked for the exact same bit for carving bit it gives the error.

Power off the machine between projects to clear the memory, then start fresh. You also mentioned the board keeps rolling...this indicates either a stuck roller or your board is not thick enough (minimum of 1/2" thickness is required). Might clean the board sensor too...maybe it's having trouble "seeing" the board edge when moving in x for measurement.

[bergerud]

So, if you are loading your bits as prompted for, then it has to be something else causing the error. Check your Z-truck travel and bearings. If the Z-depth differs between the stored memory depth and the real-time depth measurement, it is possible something is interfering with the z-truck travel and yielding different readings at different times. A dirty or frozen bearing, mis-adjusted z-truck bearings, rubbing of the z-truck against the mount, z-belt going bad or stretching, can all be things to investigate.

If the above stuff all seems ok, it could also be a dusty z encoder.