> What LinuCNC is doing in its core was done on relatively simple systems > without GUI long time ago. I believe that it's time for architectural > change. Split GUI from RT section, and move away from the dependence on > terrible PC architecture to industrial SBCs make sense to me. Imagine, > we still have DOS functions in BIOS! And that is "emulated" in virtual > machines in the data centers these days! >
I'm not even close of being a developer or a programmer because I really lack the programming expertise (which I hope slowly I can gain) so I can only speak as an integrator but I think what you're saying about moving to SBCs is already happening. Off course it's not happening at a fast rate but I think we'll eventually get there. The problem I started to see here, and mostly since I suscribed to the developers list, is that IMO there is only a few people doing all the hard work (Andy being the first that comes to my mind because is the one I talk to the most). It's not a complain but rather a compliment because the developers on this project are doing pretty amazing stuff. I think the solution here is for us integrators and frequent users of LinuxCNC to get more involved into the development, in any way we can. This is a critic to myself mostly, because sometimes I feel guilty about not having the time or knowledge and expertise to contribute to that matter. For example, today is one of those days that I can really sit and read thru the list and ask something or may be respond something to someone, just because I'm too busy with job's stuff. But to sum up, I'm more that agree with what you're saying. But I think that whatever happens with LinuxCNC 3.0 in the near future, we need to think about portability so low cost SBCs and/or PCs are still supported because I think that's one of the main concerns of this project (correct me if I'm wrong). El lun., 7 sept. 2020 a las 21:42, Bari (<bari00...@gmail.com>) escribió: > More details: > > MMC - Modern Machine Control > > Everything is STM32. > > Real time Ethernet with bridges to factory floor protocols. > > Distributed intelligence > > Easy to debug > > "All things to everyone", ATE GUI's. > > Support for any buses the OS supports, bus agnostic, ungendered, > polytheistic, all-buses-to-everyone, no bus left behind, etc etc > > Arrives early vs just in time design > > No old hardware! You have been warned! > > All code over 6 months of age is automatically tossed. > > No developers are allowed to complain, only manage. > > CAM and CAD included for one stop shopping. > > No Clippy, but popups for what I think you want to do macros. > > Automagic updates while you sleep, on or off the machine. > > Wizards, witches, etc whatever it takes to make you happy. > > Post G-code ready. > > > > Main components (MC): > > Operator panel based on industry-compatible PC technology for the > man-machine interface > > CNC control unit > > Programmable controller > > Drive modules for machine tool axes and spindles > > Motors (AC motors and linear drives) > > Supply and energy recovery unit (S/E unit) > > > Digital Drive Control (DDC): > > High resolution digital speed and path monitoring > > Higher order control algorithms, in particular compensation of the lag > induced contour error through speed and torque feed forward control > (important in the case of high tool path feedrates and the resulting error) > > Wide range of analysis options, e.g. measurement of frequency response > > Automatic circular test with automatic optimisation of the reversing > error that occurs at axis reversal points (quadrant error) using neural > networks > > Connection of direct drives, e.g. linear motors > > Machine safety functions implemented across two channels using CNC and > drive processors > > > Look ahead feedrate control over more than 100 blocks > > Transformations, e.g. for clamping corrections or 5-axis transformation > > Elimination of contour error in the axes to provide greater path accuracy > > Torque damping along the feed path and in an axial direction to reduce > machine wear > > Tool correction (length, radius, various types of cutter) > > Automatic path smoothing functions for smooth surfaces > > Compensation for mechanically induced errors > > Safe operation of the machine in the work area > > Compensation for temperature induced errors caused by high spindle > speeds and axis feedrates through heating of the spindle and feed axes > > Compensation for friction errors at axis reversal points (quadrant errors) > > Compensation for leadscrew errors and errors in measuring system > > Compensation for angular and sag errors in machine tool through > interpolative compensation (volumetric compensation or cross error > compensation) > > Compensation for play in axes that are not measured directly > > > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
