I’ve had my 4xxl for a few weeks. Still no projects. My fault, bc I am definitely not in the target audience for this machine.
I resolved my latest issue this morning and I’m now on to my next one. Each time I attempt to initial I must turn off the machine for atleast 15 minutes and manually move the gantry. I then turn on my laptop, plug in the USB, turn on the cnc, go to settings, load defaults (machine and z plus), and configuration to machine and initialize.
Is this standard? I’ve already emailed carbide support and I’m sure they’ll get back to me within the next couple of days.
The configuration should only have to be sent once. The machine knows what it is but you are mostly configuring Carbide Motion to let it know what machine you are using. Not likely but if you use multiple machines you have to send the configuration each time you use a different machine type. That only applies if you have 2 or more C3D machines. If you only have one machine you should not need to send the configuration but one. Sometimes when upgrading CM it is recommended to send the config but only when upgrading from one level to another and may not always be needed.
CM is configured to your type of machine and where the BitSetter is located. If this is your initial initialization connect to machine and go to settings and turn off (uncheck) the BitSetter. You will configure its position after you get initialized. The most common problem with initialization on a new machine is the proximity switches need to be adjusted. Sometimes they are too far away to trigger properly when the machine goes to the home position. Another issue could be a homing switch or the BitZero magnet is on all the time or the magnet is grounded. The same thing connect to machine and go to settings and see if there are any active inputs like a homing switch on all the time when the machine is not in the home position or if your BitZero magnet is touching ground.
The machine is doing a truly phenomenal job remembering the machine’s settings. Also, I should clarify that I have had the machine put together for a few weeks, so this would not be the first time it’s being initialized. It’s actually initialized quite a few times. The issue is that when the machine reverts “home” and an attempt to initialize is done for a second or third time in one setting, for instance within the same hour, all of the steps mentioned in my original post must be done in order to initialize properly.
There are no steady active inputs from the swtiches; however, they do respond correctly when tested. I have a bitsetter, but that’s not installed. Unless the bitzero you’re referring to is something completely separate and not coming up with any of my online searches.