Are you talking clock drift, always resetting to (eg) 00:00, a timezone offset, or something else? If it's drift, that's normal... clocks drift, some are shockingly bad. A lot of times you don't see it because OS's are configured to sync to the Internet regularly. You can check the time in the BIOS to verify that. If you don't have an internet connection on the machine, you're probably stuck with the drift/manually adjusting it occasionally.

Always resetting to 00:00 is probably a dead battery, timezone offset is likely misconfiguration or (if you're dual-booting) Windows and Linux fighting over whether BIOS time is localtime or UTC.

No calculator... pretty sure it has Python installed, which IMO is the best calculator around.

Thanks, that is very helpful.

Jogging being designed to be re-targeted while already moving is the key point I was hoping to confirm.

The note that each axis has its own planner and is not coordinated with the others is also important. That means FabScan should probably generate the desired Cartesian velocity vector itself, while LinuxCNC remains responsible for the real-time per-axis acceleration/velocity limits.

Your QtPlasmaC “scan mode” suggestion also makes a lot of sense. For early testing I can keep FabScan limited to idle/manual operation, but a dedicated mode that prevents conflicting user jogging would be a cleaner long-term solution.

This gives me a much better direction for the simulation and LinuxCNC SIM testing before I try any continuous motion on the real machine.

Thanks again!
Jeff

I'm on 2.7.15 How in the world do you make the desktop clock read bios clock and keep correct time? i'm a linux newb
Did this version really ship with NO calculator???

Linuxcnc has no ability to 'drip' feed gcode commands.
You can stack MDI commands but that doesn't always work the same as a program.

I realize neither of these is what you want to do anyways.

So the other two ways to control movement is jogging and external offsets.
Jogging seems to most appropriate for what you are doing.
jogging is made to be re-targeted mid movement.
Each axis has it's own planner and they are not coordinated with each other.

If you want to coordinate with QtPlasmac, best to have them integrate a 'scan' mode to lock out the user from trying to jog but otherwise I think if idle, Qtplasmac won't mind.

Thanks a ton, Greg. How soon will this hit Buildbot2, you figure?

 Is it unrealistic to try and run this on 7.2.15 ?

Earlier this year i got hit by the idea, to build an airplane windspinner. The model is based on Nieuport N28. The body is made of oak, some other parts are made of screen-printed plywood panel

Just checking you know, home switches need to stay triggered to end of travel.
Also be sure to add a home-offset to move off the home switch trigger
 

I would try typing: lcec-configgen
and see how much of your configuration is done for you

If I had a Trademark on fusion360 and found someone with a product in the same trademark class called CNC fusion, I would be sending a Cease and Desist letter real quick. I recommend you change the name of your product. There are lawyers out there whose business model looks for opportunities to bill their client for trademark protection.. That would be an instant winner.

Johnsinski wrote:

rodw, oh I saw you on youtube! The new motion.interp.heading pin looks to give you the tangent angle of the current point on a path? That seems helpful.

oh well, tried to attach gifs of the two motion strategies, but didn't work.

Yes the heading gives you an arc tangent to a G2/G3 move which is the direction the wheels should be pointing to drive it. When you revert to a G0 or G1 move, the heading is simply the direction of travel which should also be where both wheels are pointing

Now in the case of  the inside wheel needing to travel  a shorter arc radius than the outer wheels, you should be able to calculate that from the outer arc.

Hi Sascha,

i wanted to thank you, you made my day with your hint, that's what it needed to get the smooth Handwheelfeeling i wanted!

Greets, Tom

Hi All. 

I am using SCARAKINS for my scara robot with (2 angular axis + 1 linear axis). The joint mode is working fine but when in cartesian mode the X axis does not move. Please help!  
Attached is the config. I am using MESA 7c81 with a regular BOB.