Hopefully someone can help as I'm pulling hair out with this particular one. I have a standard BigBox Kickstarter 1.0 Dual with no mods. Firmware being used is the latest from Alex https://github.com/Alex9779/Marlin/tree/BigBox/Dual/RC Compiled using Arduino 1.6.9 with no issues and uploaded through Octoprint 1.2.12 using the Firmware updater. Set home and carried out the 9 point bed levelling, all looking good. Chose the traffic cones as a dual slice in S3D 3.1.0 using again Alex's .FFF for dual big box. Uploaded to BigBox and hit print, all starts fine, heads and bed warming up but for some reason during the 2nd extruder warming up the carriage decides to move. I've proved this to myself by typing in the G-Code line by line. I don't think there is anything wrong with the gcode as it runs with an old .HEX I have so I suspect the latest firmware. Any pointers greatly appreciated as I can't think what to try. Up to this point the BB has been working fine with no issues making it appear to be the firmware but I can't be the only one.
I'm beginning to think it's a typo or issue with marlin_main.cpp as it was modified just prior to when I updated my files.
If I open your code in Repetier Host, I see two objects and the faulty movement too. Try to slice the attached cone. Change the extension to *.amf before (could not upload with the correct extension).
I'm afraid S3D can't load .amf files. The problem I have occurs before the head leaves the dock, it occurs during the purge process. The head doesn't even get to leave the dock.
You are correct, I don't think the problem is the G-Code. I can run this code without any issue on an old version of the firmware. I think it is an issue in the source code.
Don't have that, opened in S3D and I read the code line by line... there is no unusual movement in there until the print starts... Maybe I don't see it... Can you post a screen shot?
I'm just updating my Repetier host, unfortunately it's not setup for the BigBox (Setup for SpiderBot).
hmmmm I checked the commits but is see nothing obvious... So I didn't print a dual yet with RC6 I think... And the firmwares I am using and you use for the V1.0 dual only differ in some small config changes...
I'm convinced it's not the G-Code. My mistake was being lazy and downloading the .hex back in April (that works fine) and so I can't see the changes when I compare the files in Notepad++
Hmmm that is a commit I pulled extra to RC6 because it was it was not in there yet but making problems especially on dual prints because the purge had strange issues...
Ok the problem is the firmware it seems... You move the head into the dock and when you switch to T1 the head moves. I think that is because T1 is not at that position but I never had that before RC6, I am going to do what I wrote, reversing that one commit but I don't think that is the problem...
Thank you so much, I'm not going mad. I think trying to clone the Git and using what should be a simple program will do that for me!
