-
Notifications
You must be signed in to change notification settings - Fork 231
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
Activating serial connectors on the board #119
Comments
To give the choice, to use USB or serial is just one configuration parameter in Configuration.h To listen to both set of incoming ports is harder, since if you use both ports, 'who is right'? E.g. user A prints via USB, and user B tries to print via the serial port. You now have 2 incoming GCODES that will run intermingled. To handle that properly, a lot of effort is required. |
Well, how often would it really happen? I don't see any reason why people do such a madness and overload their printer with GCode from both sides. If people are doing crap they should get an unexpected (or whatever they were planning to do) result. Yes, it is currently possible to access the RX(1)/TX(1) pins of the active connection by soldering some test points, but that is - in my point of view - not modding-friendly at all. If this additional serial connection is really meant to be dead, why are we even wasting solder plus pins on our board and finally give these pins a name? |
Like noticed on my visit the serial pins are not used at the moment.
Would be great to have an option somewhere to make them work like the usual USB connection, so the pins are at least not dead.
The text was updated successfully, but these errors were encountered: