Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swappable channel A/C for HBP/Fan #30

Open
makerbot opened this issue Apr 12, 2010 · 3 comments
Open

Swappable channel A/C for HBP/Fan #30

makerbot opened this issue Apr 12, 2010 · 3 comments

Comments

@makerbot
Copy link
Collaborator

Add an eeprom configuration byte to assign HBP and fan mosfet channels.

@zaggo
Copy link
Contributor

zaggo commented Apr 12, 2010

Is this really necessary? Sounds to me like more complicating things than making it easier.

@makerbot
Copy link
Collaborator Author

I've had some requests for it, and it's invisible to users who don't need it, but you're right that it's a low priority issue. Marking it as such. It's simple enough that it will probably happen in v2.1, though.

@zaggo
Copy link
Contributor

zaggo commented Apr 12, 2010

true, the internal implementation is (kind of) transparent to the user.
However, I think it is clearer to the operator to read (in a hypothetical "user manual") something like "connect the HBP to the A+A- connectors" than "connect the HBP to A+A- or C+C- (but not B+B-!) and then configure the channel used to control the HBP in the EEPROM settings".
It's easy enough to re-connect the HBP cables to a (the!) well-defined connector.
It's a whole different thing with the axis swapping preferences of the stepper motors. We have preassembled connectors there, which only fit into the sockets in one direction (without using force), so it makes sense to let the users connect the connectors as provided and do the switch in software.
But in this case it's unclear to the user why only the A/C channels are swappable.
A logic solution would be a complete free routing of all channels (A/B/C) to their logic function in software. But again, this would make the code more complicated and thus harder to support.
As long as the A/B/C channels are connected with the current terminals (and not some pre-assembled, fixed connector), I think it make no sense to do a (partial!) channel re-routing in the firmware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant