Steppernug: Difference between revisions
No edit summary |
(→Status) |
||
| Line 8: | Line 8: | ||
#Height Control. This is the one non trivial task left as far as hardware is concerned. It has required access to a torch, which Chuck and I don't really have. '''Next Steps:''' Hardware to be researched; electrical connections required from Interface: 2 signal, 2 power, and 4 from a Steppernug stepper driver output. | #Height Control. This is the one non trivial task left as far as hardware is concerned. It has required access to a torch, which Chuck and I don't really have. '''Next Steps:''' Hardware to be researched; electrical connections required from Interface: 2 signal, 2 power, and 4 from a Steppernug stepper driver output. | ||
#In summary, I have most of the design work done, but before having the next board built I wanted to make sure the height control has been prototyped and tested. That has been holding up development of the hardware side. | #In summary, I have most of the design work done, but before having the next board built I wanted to make sure the height control has been prototyped and tested. That has been holding up development of the hardware side. | ||
==Firmware Status== | |||
Marcin, Darren, | |||
Firmware status: | |||
The homing is now functional on my mockup using one optosensor on each | |||
motor. I did a little development on limits a while back but they are | |||
not fully implemented. | |||
We made a choice a while back to implement an I2C interface bus on the | |||
board. This turns out to be a little more complex than I expected and | |||
has been a time sink, but I still support the design decision as it | |||
makes it easier to add more I/O features down the line. As noted | |||
above, we are successfully running home switch input operations | |||
through I2C; however we can't yet interleave output operations (e.g. | |||
"start torch") with input operations in real time. | |||
I am fully employed and unfortunately not finding much time to work on | |||
this project, maybe a few hours a week. A possible place to look for | |||
firmware coders who are already up to speed is the grbl site at | |||
https://github.com/grbl/grbl . I would definitely like to see this | |||
come to fruition. | |||
Cheers, | |||
Chuck | |||
=Links= | =Links= | ||
*OpenCapitalist documentation, schematic, and layout files - [http://opencapitalist.org/steppernug-simple-stepper-motor-controller/] | *OpenCapitalist documentation, schematic, and layout files - [http://opencapitalist.org/steppernug-simple-stepper-motor-controller/] | ||
Revision as of 02:26, 26 March 2013
StepperNug OSE V1.1 from Opencapitalist
Status
- Integration with the Arduino is essentially done. The latest version includes an interface board that plugs into the Arduino, like an Arduino shield would. Next Steps:
- The end stop sensing has been integrated in hardware and firmware. Including coming up with a special algorithm that Chuck was working on to align the two motors on the x axis. I wouldn't call this tested and complete, but the hardware for the next rev is designed and Chuck can advise on firmware, but I believe he has that essentially done. Next Steps:
- Trigger, I assume you are referring to turning the torch on and off. This is trivial, there are two expansion ports on the StepperNug Interface board to plug daughter cards into. One of which can be used for torch control, the other was intended for height control. Next Steps:
- Height Control. This is the one non trivial task left as far as hardware is concerned. It has required access to a torch, which Chuck and I don't really have. Next Steps: Hardware to be researched; electrical connections required from Interface: 2 signal, 2 power, and 4 from a Steppernug stepper driver output.
- In summary, I have most of the design work done, but before having the next board built I wanted to make sure the height control has been prototyped and tested. That has been holding up development of the hardware side.
Firmware Status
Marcin, Darren,
Firmware status:
The homing is now functional on my mockup using one optosensor on each motor. I did a little development on limits a while back but they are not fully implemented.
We made a choice a while back to implement an I2C interface bus on the board. This turns out to be a little more complex than I expected and has been a time sink, but I still support the design decision as it makes it easier to add more I/O features down the line. As noted above, we are successfully running home switch input operations through I2C; however we can't yet interleave output operations (e.g. "start torch") with input operations in real time.
I am fully employed and unfortunately not finding much time to work on this project, maybe a few hours a week. A possible place to look for firmware coders who are already up to speed is the grbl site at https://github.com/grbl/grbl . I would definitely like to see this come to fruition.
Cheers,
Chuck
Links
- OpenCapitalist documentation, schematic, and layout files - [1]