Problems with Marlin

1. The very FIRST line that the printer spits out is the date the firmware was compiled - you will have to scroll backup in repetier-hosts log window to see it. As to which 'version' it is - both versions you referenced have the same internal versions, so the only way to tell is based on you recalling which version you last compiled and when. It looks like this, with obviously whatever date you compiled your firmware in place of the one listed here. I've bolded the key lines...

I *could* increment the version number in our versions - however - that will mean that we are 'ahead' of the mainline Marlin, as all its versions are perpetually 1.0.0 at the moment (technically, they are all still 1.0 RC's...) .. I am not keen to version a fork higher than the mainline base from which it derives... that will just lead to all sorts of poo...

2. Marlin can't control the MOSFET's current direction or polarity - if it could, it would be awesome As to if the pins are different; The printrboard section of pins.h of my marlin is identical to Solidoodles much older version - EXCEPT for the SDSS pin, which has a long sordid tale unto itself (teach people to share Y-Stops with SS pins ... ); So in short - whatever is going on with your PWM fan is unrelated to the firmware;

My Marlin:

#if MOTHERBOARD == 8 || MOTHERBOARD == 81
#define KNOWN_BOARD 1
#define AT90USB 1286  // Disable MarlinSerial etc.

#ifndef __AVR_AT90USB1286__
#error Oops!  Make sure you have 'Teensy++ 2.0' selected from the 'Tools -> Boards' menu.
#endif

#define LARGE_FLASH        true

#define X_STEP_PIN          0
#define X_DIR_PIN           1
#define X_ENABLE_PIN       39

#define Y_STEP_PIN          2
#define Y_DIR_PIN           3
#define Y_ENABLE_PIN       38

#define Z_STEP_PIN          4
#define Z_DIR_PIN           5
#define Z_ENABLE_PIN       23

#define E0_STEP_PIN         6
#define E0_DIR_PIN          7
#define E0_ENABLE_PIN      19

#define HEATER_0_PIN       21  // Extruder
#define HEATER_1_PIN       -1
#define HEATER_2_PIN       -1
#define HEATER_BED_PIN     20  // Bed
#define FAN_PIN            16  // Fan
// You may need to change FAN_PIN to 16 because Marlin isn't using fastio.h
// for the fan and Teensyduino uses a different pin mapping.

#if MOTHERBOARD == 8  // Teensylu
  #define X_STOP_PIN         13
  #define Y_STOP_PIN         14
  #define Z_STOP_PIN         15
  #define TEMP_0_PIN          7  // Extruder / Analog pin numbering
  #define TEMP_BED_PIN        6  // Bed / Analog pin numbering
#else  // Printrboard
  #define X_STOP_PIN         35
  #define Y_STOP_PIN          8
  #define Z_STOP_PIN         36
  #define TEMP_0_PIN          1  // Extruder / Analog pin numbering
  #define TEMP_BED_PIN        0  // Bed / Analog pin numbering
#endif

#define TEMP_1_PIN         -1
#define TEMP_2_PIN         -1

#define SDPOWER            -1
#define SDSS               14
#define LED_PIN            -1
#define PS_ON_PIN          -1
#define KILL_PIN           -1
#define ALARM_PIN          -1

#ifndef SDSUPPORT
// these pins are defined in the SD library if building with SD support
  #define SCK_PIN           9
  #define MISO_PIN         11
  #define MOSI_PIN         10
#endif

#endif  // MOTHERBOARD == 8 (Teensylu) or 81 (Printrboard)

Solidoodles Marlin:

#if MOTHERBOARD == 8 || MOTHERBOARD == 81
#define KNOWN_BOARD 1
#define AT90USB 1286  // Disable MarlinSerial etc.

#ifndef __AVR_AT90USB1286__
#error Oops!  Make sure you have 'Teensy++ 2.0' selected from the 'Tools -> Boards' menu.
#endif

#define X_STEP_PIN          0
#define X_DIR_PIN           1
#define X_ENABLE_PIN       39

#define Y_STEP_PIN          2
#define Y_DIR_PIN           3
#define Y_ENABLE_PIN       38

#define Z_STEP_PIN          4
#define Z_DIR_PIN           5
#define Z_ENABLE_PIN       23

#define E0_STEP_PIN         6
#define E0_DIR_PIN          7
#define E0_ENABLE_PIN      19

#define HEATER_0_PIN       21  // Extruder
#define HEATER_1_PIN       -1
#define HEATER_2_PIN       -1
#define HEATER_BED_PIN     20  // Bed
#define FAN_PIN            16  // Fan
// You may need to change FAN_PIN to 16 because Marlin isn't using fastio.h
// for the fan and Teensyduino uses a different pin mapping.

#if MOTHERBOARD == 8  // Teensylu
  #define X_STOP_PIN         13
  #define Y_STOP_PIN         14
  #define Z_STOP_PIN         15
  #define TEMP_0_PIN          7  // Extruder / Analog pin numbering
  #define TEMP_BED_PIN        6  // Bed / Analog pin numbering
#else  // Printrboard
  #define X_STOP_PIN         35
  #define Y_STOP_PIN          8
  #define Z_STOP_PIN         36
  #define TEMP_0_PIN          1  // Extruder / Analog pin numbering
  #define TEMP_BED_PIN        0  // Bed / Analog pin numbering
#endif

#define TEMP_1_PIN         -1
#define TEMP_2_PIN         -1

#define SDPOWER            -1
#define SDSS                8
#define LED_PIN            -1
#define PS_ON_PIN          -1
#define KILL_PIN           -1
#define ALARM_PIN          -1

#ifndef SDSUPPORT
// these pins are defined in the SD library if building with SD support
  #define SCK_PIN           9
  #define MISO_PIN         11
  #define MOSI_PIN         10
#endif

#endif  // MOTHERBOARD == 8 (Teensylu) or 81 (Printrboard)

Re the P.S : Did you enable the hystersis options in the Configuration.h file ? you need to enable the Z_Wobble et al in Configuration.h for it to do anything.. and Re the Heated Bed - Did you enable as per the Configuration.h file PIDTEMPBED; the defaults in the file for the PID are based on older beds - make sure to run the referenced M303 E-1 C8 S95 command (or susbstitute S95 as desired..) . Update the values in the file, recompile, reupload.

However - If you didn't enable the PIDTEMPBED - then the Firmware has nothing to do with your Bed heatup - because it simply turns on the MOSFET then and thats that... so if its now not performing as the same, something physical has changed - be it your Powersupply, the MOSFET going, bad physical connection, or the bed itself.  Given the MOSFET for your PWM Fan is now misbehaving - I'd be checking for a short or something somewhere as well...

Click on the scroll bar next to the message window, or click in it and use the mouse wheel if you have one...
Or alternative, under Repetier-Hosts Preferences, make sure Logging is enabled, and just open the Log file in a text editor.

you're not using lawsy or mines firmware - since you have the mendel-parts.com URL there..... you get that from Pirvan (just curious - only other place I've seen someone using the Mendel streamed firmware... )? Anyway, Because the "mendel-parts" based 'mashup' isn't the one we developed here in the community... I'd personally suggest grabbing the firmware which is the latest one from the community;

Grab the source code by downloading the zip from https://github.com/ozadr1an/Solidoodle- … in_v1_beta , Unzip it, move the "Marlin" folder to the Arduino-Sketches directory (check preferences inside Arduino IDE), then open that Marlin folder and the Marlin.ino/Marlin.pde (either, doesn't matter) and use that to compile the firmware.

make sure you're doing the boot jumper at the right time (before you power the board), and let us know what errors if any the hid-bootloader program (from inside the hid-bootloader.zip folder) reports.

This is one of the 'joys' (theres many... ) of the Printrboard.. and why I despise them lol

Its Motherboard Rev E. Guys from this forum said that it means that I have standart Printboard.
Yes, it is fresh board as it was shipped, I didnt change anything - only tried to make firmware upgrade with your and Lawsly firmware as I mentioned in first topic.

What does it mean? Why again? I don't know what means GPL and whhy is it violating..?

The board needs to startup with the jumper across the boot pins - pressing 'reset' causes it to also restart. Yes the board will only accept new firmware if it starts up with the jumper in place to put it into DFU mode so it can receive the new firmware.

Putting it on before powering it up vs plugging it in, putting the jumper on, then pressing reset; essentially does the same things...

in theory - yup.

But I've never had/used the Solidoodle built Printrboards (they wont send me a free one, and I wont pay $100 for it so I can help them...) - so I'm just working from guess work

THe update may have taken properly....What you are seeing in the log file might actually be just a mistake....

There is a small problem with the code in the Language.h file that it does not properly show the Solidoodle Machine name etc...

For the Elif statement to work correctly you have to add "MOTHERBOARD == 6" to the beginning - see below corrected.

Otherwise, it will always default to MENDEL for any of the solidoodle board options. 

#ifndef LANGUAGE_CHOICE
#define LANGUAGE_CHOICE 1 // Pick your language from the list above
#endif

#define PROTOCOL_VERSION "1.0"

#if MOTHERBOARD == 7 || MOTHERBOARD == 71
#define MACHINE_NAME "Ultimaker"
#define FIRMWARE_URL "http://firmware.ultimaker.com"
#elif MOTHERBOARD == 80
#define MACHINE_NAME "Rumba"
#define FIRMWARE_URL "https://github.com/ErikZalm/Marlin/"
#elif MOTHERBOARD == 6 || MOTHERBOARD == 62 || MOTHERBOARD == 33 || MOTHERBOARD == 34 || MOTHERBOARD == 81 //{SD Patch}
#define MACHINE_NAME "Solidoodle" //{SD Patch}
#define FIRMWARE_URL "http://github.com/mlaws/solidoodle2-marlin/" //{SD Patch}
#elif MOTHERBOARD == 77
#define MACHINE_NAME "3Drag"
#define FIRMWARE_URL "http://3dprint.elettronicain.it/"
#else
#ifdef CUSTOM_MENDEL_NAME
#define MACHINE_NAME CUSTOM_MENDEL_NAME
#else
#define MACHINE_NAME "Mendel"
#endif

#define FIRMWARE_URL "http://www.mendel-parts.com"
#endif

I was having the same problem with the fan on my sd3 with the rev e printrboard.  The pins for the fan were actually 22 on the updated firmware, i had to revert back to 16.  My fan works fine now.

Rjp350z is right about the log not showing an update.  Every different version i used all show the same marlin v1 mendel-parts.com in the log.  So the gpl probably isn't being violated.  I know mine was changed because I'm using an e3d now and i can ramp up the heat well past 230.

I am sure his bed problems are firmware related as well.  Ive run my bed at 115 for awhile now and would reach that after 10-20 mins.  After i flashed it wont get over 96 now.  I manually changed the max bed temp from 110 to 120.  I haven't done pid tuning for the bed, but if its on constant that won't help.

The only thing i can think is the e3d is using more of the power supply.  The hot end reaches 230 in under two minutes now, but its only on 30-40% duty cycle instead of 50% so i don't think current draw is limited from the hotend change.

I did see in the firmware a setting for bed max power, which was set at 256, noted that that was full power. Maybe try 255?

Edit:
Could a wrong thermistor in firmware cause such slow heating?   I'm going to check it when i get back home.