Exact same JSON file compiled in DEV version won't execute Gcode

After a lot of struggle I found out that the exact same configuration.h/JSON file won't let me execute Gcode when compiled in DEV mode.

This configuration file works fine in .92 and with both new and older versions of Arduino.

Please let me know what settings I need to change in order to get Gcode to execute in the DEV version.

I've pasted the configuration below that allows me to execute Gcode when compiled in .92 but not the DEV version...

/* This file is part of Repetier-Firmware.

Repetier-Firmware is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Repetier-Firmware is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

This configuration file was created with the configuration tool. For that reason, it does not contain the same informations as the original Configuration.h file. It misses the comments and unused parts. Open this file file in the config tool to see and change the data. You can also upload it to newer/older versions. The system will silently add new options, so compilation continues to work.

//#define EXTERNALSERIAL use Arduino serial library instead of build in. Requires more ram, has only 63 byte input buffer.// Uncomment the following line if you are using Arduino compatible firmware made for Arduino version earlier then 1.0// If it is incompatible you will get compiler errors about write functions not being compatible!//#define COMPAT_PRE1#define BLUETOOTH_SERIAL -1#define BLUETOOTH_BAUD 115200#define MIXING_EXTRUDER 0

/*If the firmware is in laser mode, it can control a laser output to cut or engrave materials.Please use this feature only if you know about safety and required protection. Lasers aredangerous and can hurt or make you blind!!!

The default laser driver only supports laser on and off. Here you control the intensity withyour feedrate. For exchangeable diode lasers this is normally enough. If you need more controlyou can set the intensity in a range 0-255 with a custom extension to the driver. See driver.hand comments on how to extend the functions non invasive with our event system.

If you have a laser - powder system you will like your E override. If moves contain aincreasing extruder position it will laser that move. With this trick you canuse existing fdm slicers to laser the output. Laser width is extrusion width.

Other tools may use M3 and M5 to enable/disable laser. Here G1/G2/G3 moves have laser enabledand G0 moves have it disables.

In any case, laser only enables while moving. At the end of a move it getsautomatically disabled.*/

/*If the firmware is in CNC mode, it can control a mill with M3/M4/M5. It workssimilar to laser mode, but mill keeps enabled during G0 moves and it allowssetting rpm (only with event extension that supports this) and milling direction.It also can add a delay to wait for spindle to run on full speed.*/

LCD does not send gcodes but executes the commands directly e.g. homing, move, temp. But that is working perfectly for all printers I use dev on. So How do you send G1 Z70 form LCD. You seem to to not use the firmware LCD could that be? Do you have something like PanelDue, MKS or similar?