My remapping function of power isn't satisfying yet. I must say that i didn't take the easiest photo. I made a quick user interface (Python).

Lessons Learned :
To avoid white lines caused by a mismatch between the requested travel distances and the minimum step resolution allowed on an axis, I implemented a step-based logic where the commanded distance is computed by multiplying the number of Y-axis steps by the axis counts-per-unit value.
The same resolution was initially used for the X-axis motion; however, the system was unable to keep up with the resulting instruction rate, causing the feed rate to drop to 2400 instead of the requested 3000. As a result, the resolution had to be reduced.

Here's the first release of my Gcode converter, AliG : https://github.com/MoMo830/AliG/releases/tag/AliG

Feek free to comment.

A small example, once settings are correct.

Excellent progress.

nb. GitHub returns 404 error for your Alig.

Tweakie.

Sorry, the good one : https://github.com/MoMo830/AliG

I made some updates to ALIG :
- Added Analog output choice (not suitable yet with pokeys, as it requires analog output 0)
- Added S support
- Choice of the origin point
- Improved graphics

Link of the project : https://github.com/MoMo830/AliG

Do I need to make a new topic as S commands are now supported ?

Do we know if Mach4 now supports the S### command being used within a running GCode without breaking the CV chain ?
Last I tried it failed miserably.

Tweakie.

No it doesn't, thats why I built this software. It allows to use M67. I just added S for non mach users.
I can now engrave within Mach4.

I still use S for cutting only.

OK thanks, I now understand your reasoning for adding the S### support.

Tweakie.