TP2 and it is working only with simple shapes really well, I did not notice infinity spikes of anything..
no more difficult shaping avaible.. it just froze at cloud of points as G2\G3 transfered to cloud of points .. time spiking increased from last testing
testing only in simulation level ... no real hardware avaible for now
You are welcome, still lots to be done, can you share your configuration, does it always freeze on the point cloud? I'd like to replicate. Time spiking meaning the servo thread? Can you share that as well?
notice > well tuned RT machine with less then 2us latency
I every time start with the LinuxCNC logo startup file ... create the scope of acc + velocity preview and analyze step by step movement ... jerk 10k m\s3 then I move to the 3d chips and 3d test ... if this works well i am shifting to the my code 1d movement, 2.5 d movement and finally 3d movement .. I start with 0 type then I move to other one for right comparation.. it is freezing TP2 with 3dchips.ngc from default local folder after last update ... no diagnoze possible from my side right now
all step by step analyzing the scopes
Configuration starting basically from axis_mm.ini with custom tool table which is missing from default
Spiking was mainly during start of the scope at servothread and then periodicaly, looks like at each end of segment - but no exact proofing
I am staying tune for more testing or cooperation ...
thanks E.
Last edit: 7 months 1 week ago by endian. Reason: latency notice add
I tried to follow your instructions, and it works ok for me.
I suspect it maybe something with the custom tool table which is missing from default, could you share that?
Hello,
I am sorry my bad ...I am too much focusing in something and then I failing in others ...
I have tested some toolpaths till now ... Infinite spikes are gone at tp 1 and 2 at paths where it defenetely were in the past ... I noticed that TP1 during its startup with testing code 1_1001.ngc spiking much with servo time (if we take 250us as our goal - for 1ms it is fine) ..
Default TP0 and TP2 do not this behaviour ...
dark blue from scope pictures in the attachments then TP1 is spiking at each segment change over 200us during cloud of points its repeating spiking too..
I notice that switching between TP1 and 2 is not possible sometimes it creates error and switch me back to TP2 from TP1
