Re: Altering X and Y orientation
Posted: Sat Jul 09, 2016 8:18 pm
Hi Scootey7,
I disagree with sharkcutup about the danger and safety risk. I suspect some of us who have an extended bed have reversed the gantry installation on the table, and plugged the 'x' cable into the 'y' output (and the 'y' cable into the 'x' output) as for some us, this is what makes sense. And in fact, if that's how you use the machine day in and day out, it is the 'norm' for your use.
Speaking for myself, I find it much easier to think of with my X axis oriented along the 'long' side of the bed - which is also how I view the project in Aspire. I also know some folks who design the whole thing in that manner, and once done rotate it in Aspire, and generate the toolpaths as they have a different sense of the table axis orientation - and it works for them. I find that method has its own potential challenges - and again, for me, thinking of the 'long' side of the bed as X matches how my brain thinks of things (good, bad or indifferent).
I don't know that I'd fool with the gcode either. Given that if you want to configure your machine based on the gantry orientation, there really is no need to add this as an aspect of daily use - at least for me. Again, if that workflow works best for you - have at it.
What works best for you, in all aspects, including safety, is the solution I'd recommend you pursue.
I disagree with sharkcutup about the danger and safety risk. I suspect some of us who have an extended bed have reversed the gantry installation on the table, and plugged the 'x' cable into the 'y' output (and the 'y' cable into the 'x' output) as for some us, this is what makes sense. And in fact, if that's how you use the machine day in and day out, it is the 'norm' for your use.
Speaking for myself, I find it much easier to think of with my X axis oriented along the 'long' side of the bed - which is also how I view the project in Aspire. I also know some folks who design the whole thing in that manner, and once done rotate it in Aspire, and generate the toolpaths as they have a different sense of the table axis orientation - and it works for them. I find that method has its own potential challenges - and again, for me, thinking of the 'long' side of the bed as X matches how my brain thinks of things (good, bad or indifferent).
I don't know that I'd fool with the gcode either. Given that if you want to configure your machine based on the gantry orientation, there really is no need to add this as an aspect of daily use - at least for me. Again, if that workflow works best for you - have at it.
What works best for you, in all aspects, including safety, is the solution I'd recommend you pursue.
. 
