Is there a way to stop gcode from ignoring speed limits set in repetier-firmware?

I have two old Davinci 1.0 printers modded with E3D V6 hotends etc running repetier. (I'll call this the DUE)

first and oldest one to me is complete with its original board and a version of repetier-firmware for davinci(older 92 based) modded to fit the hotend/thermistors etc

it works flawlessly.

the other is a skeleton of a Davinci 1.0 that has a ramps 1.4 board(and 1.0.3 repetier-firmware) and the same hotend/thermistors as the first printer(I'll call this AVR)

the problem I'm getting is the startup gcode slicers send seems to ignore the speed limits set in configuration.h and eeprom

My Z axis on both has a limit of 100 its a screw type.

when the following start up code from cura is sent to the DUE printer it works flawlessly and keeps to its own speed limits.

G28 ; home all axes

G1 Z15 F5000 ; lift nozzle

G92 E0

G1 F200 E3


when I send the same code to the AVR printer it tries to go the F5000 that is set in the startup code. on a screw style Z axis and fails at it, I can hear the high frequency the stepper is trying to do but it doesn't move the bed(I have adjusted the current for the motors correctly, it has no issues moving at this proper speeds)

 even the EEPROM and configuration.h is set correctly at 100 travel/100max 50 normal

if I change it to G1 Z15 F300 ; lift nozzle

it will move to the correct height.


Anyone know if I missed a tick-box or something to stop the printer trying to go a million miles an hour ignoring its set limits?

Comments

  • Whoops nevermind I'm a dork, max travel speed, homing speed etc weren't set correctly for z axis even tho I thought I had
Sign In or Register to comment.