It is known that Repetier Server uses an XML file when exporting the content of the eprom.
I use MK4duo as firmware, and often the xml plugin for eeprom management is updated, and when I go to import a previously saved xml eeprom I find many wrong imported parameters, something that doesn't happen with the host because it doesn't use logical positions but simple gcode commands.
A simple example, msteps exported with the Host:
M350 X64
M350 Y64
M350 Z64
M350 T0 E32
M350 T1 E32
And here with the Server:
<epr pos="421" type="2" value="64">X driver microstep [ms]</epr>
<epr pos="422" type="2" value="64">Y driver microstep [ms]</epr>
<epr pos="423" type="2" value="64">Z driver microstep [ms]</epr>
<epr pos="424" type="2" value="32">E0 driver microstep [ms]</epr>
<epr pos="425" type="2" value="32">E1 driver microstep [ms]</epr>
If the MK4duo xml plugin has updates some positions (called "epr pos") change, and fails to import those values, writing them elsewhere, with its disastrous result.
I therefore ask you to implement an eeprom management like in the Host, more convenient and never wrong in any case.
I do not intend to replace the current standard, but to have also the possibility of import/export in the "gcode" format that creates the Host.
Marco