Centroid Community CNC Support Forum

Hello! If you don't mind running beta software, you can order the Ether1616 kit on this page now.
https://www.centroidcnc.com/centroid_diy/ether1616.html

cnckeith wrote: ↑Mon Nov 25, 2019 9:44 am Hello! If you don't mind running beta software, you can order the Ether1616 kit on this page now.
https://www.centroidcnc.com/centroid_diy/ether1616.html

Awesome, thanks. Not ready to order yet but looking forward to getting things like the more complex grey logic tool turrets working without needing to try and incorporate an external PLC and/or Arduino.

Ether1616 Setup Guide has been updated. 11-27-19
https://www.centroidcnc.com/centroid_di ... _guide.pdf
(refresh browser if you downloaded previously)

Ether1616 Setup Guide has been updated again, new info added.... 11-29-19
https://www.centroidcnc.com/centroid_di ... _guide.pdf
(refresh browser if you downloaded previously)

Mine is supposed to arrive early next week! Unfortunately, I'll be out of town for work all week.

I'm so happy that this was offered. I was going to installed a PLC and HMI for handling extra IO. No need now.

I'm just about ready to order the 1616, but I need to verify that the response time will be about 100 milliseconds. For instance, the documentation shows possible expanded sensing of home sensors and limit sensors. On a router that is jogging 500 inches per minute, the axis will move 8.3 inches per second, or 0.83 inches in 100 milliseconds. Cutting speed might be 125 inches per minute or 0.2 inches in 100 milliseconds. Homing speed would be much slower, possibly 10 inches per second or or 0.016 inches in 100 milliseconds. Should I assume that the response time is a constant? If it is a constant and if I home an axis at the same speed each time, then the home offset distance should also be a constant and the 1616 could be used accurately if connected to homing sensors. Limit sensors might be more problematic because the axis speed would not be constant, depending on whether the axis was at jog speed or at a much lower cut speed; however, by moving the sensor about one inch away from the absolute limit, a 500 inch per minute jog could be stopped before a crash.

The 100 milliseconds is not a "deal breaker", but I want to verify that any expectations for what I can use the board for are realistic.

like the ether1616 user guides says ...put HomeAll on the Acorn for the most accurate homing, HomeAll uses only one input for all home switches, (and put slaved home on Acorn if you are Auto Squaring as well), then all the overtravel limits can go on the ether1616. do a test and see how far your machine drifts after an estop from max rate, each machine will be different, some stop almost immediately while others continue to drift a while. Place the overtravel limit switch appropriately. and suggestion for you...our 5 axis machines have a polyurethane bumper at the end of the travel (in line with the ballscrew) to protect the machine itself from an rare accidental over travel.
(note: if you have software travel limits and homing working well the machine will not hit the limit switches unless an axis drive runs away (not Acorn, Acorn doesn't do that:-)).... I don't think my machine has hit a limit switch in years. )

Richards wrote: ↑Mon Dec 02, 2019 9:23 am Should I assume that the response time is a constant?

No. Typical time to respond to an input will be much lower.

appendix R (Ether1616 Input Output Response Time) has been added to the Ether1616 Setup Guide. refresh your browser to download the latest with todays date.

Thanks Keith. I just ordered the 1616. Looking forward to trying it out.