1. Gibts nicht beim delta, also aus/0 2.Ich nehme immer 80000. Mit quadstepping bei delta gehts bis 320000 dann. Cartesisch kann noch mehr. 3-4 nicht ändern, versteht wohl eh keiner so genau. 5-6 Advance mit bowden ist witzlos. Da kommt der extruder nicht mit. Ansonsten sollte es mittlerweile beim due klappen. 7. Ja startgeschwindigkeit aus dem stand. 8. Gibt nur pullups. Nötig für mechanische scby repetier - Software
Zum verständis. Diese Motorroutinen sind für einfache routinearbeiten wie abröumen oder extruderwechsel. Sie funktionieren nur wenn der normaller pfadplanner leer ist, aber das wird automatisch gemacht durch warten. Hier können auch neue Treiberhinzugefügt werden, aber ich gehe mal davon aus das hier der einzige verhandene Treiber verwendet wurde. In driver.h ist der gesamte code für die positionby repetier - Software
No, there are no simulated pins. If you are only talking about handling extruder position check extruder.cpp where we have the function responsible for extruder selection (selectExtruder I think it is named). Or write a new g-code that does it and lets it run before/after gcode selection, so you can write is as event in a separate file not messing up with existing code. Temperature control isby repetier - Repetier
The host comes with 32 and 64 bit curaengine executables in plugins/CuraEngine. Make sur eit renamed the right one on configureFirst run (you did run it right?) and also make sure it has the executeable bit set.by repetier - Repetier
On firmware side you need 3 extruders I think. It is just that 3 extruder share one heater that make sit problematic. Not really a problem if you know what you are doing.by repetier - Repetier
I have to think about that. It makes again more trouble since some printers can not connect without DTR/RTS high while others will reset and even others can not be reset at all. So we have then a setting that can prevent connection or does not do what it says provoking new support questions.by repetier - Repetier
One more thing. You might want to enable mixing extruder in printer settings->extruder. This will make the host think you have one nozzle for more colors. Works like it should only that it offers 16 extruders I think. So just use the first 3.by repetier - Repetier
Since 3 extruders share a single nozzle I guess your firmware controls the temperature only with extruder 1 since you have only one heat element and that can belong only to 1 extruder. The host does not know this and thinks you have 3 extruder with 3 heaters. A mapping might help here, bit is currently not implemented.by repetier - Repetier
This is related to a bug fixed in 1.5.6. Before the host did not send selected extruder id as selected in object placement correctly. Therefore slic3r used it's defaults. Now these extruder settings get send correctly and slic3r uses the selected extruder for the object. This overrides default settings.by repetier - Repetier
It always was a point of confusion and often the source why users did not succeed. The new solution is mix like we use it in our server or othe rhost software does it. It tries a reset but does not depend on it to succeed, so it should now work on all boards.by repetier - Repetier
Sure it is available. You just need to checkout the github work092 branch instead of master branch.by repetier - Repetier
The firmware can mirror all stepper signals to a second driver. In the config tool just select the mirror option for the driver and a second set of motor pins will appear. If you have added extra pins they are not defined in pins.h so you have to define them or simple select E2 extruder and later in config.h replace these pin names with the pin numbers you assigned.by repetier - Repetier
I see no disadvantages for this new version. It is rather faster then slower so I made it the new 1.5.6.by repetier - Repetier
Host starts with drt/rts low and had a 1s delay before turning them high. In a second firmware can achieve already some stuff. So reduced it to 10ms in this version: For me it still works creating a reset. I also tested sd influence. With sd card I have 1.5s delay and without I get the same 3s delay you get, so that delay is sd related or at least 1.5s. In the same period also firmware gets inby repetier - Repetier
No, "Start" comes after every reset. Just hit reset key on the board and you will see it happen again. You can also do a software reset or trigger watchdog to get the same. There is nothing the firmware can do against this (beside self inflliced resets).by repetier - Repetier
Yes, "Printer reset detected - initalizing" comes in response to "start" from firmware. This is only on restart of printer that it sends start so it must be reset (which is what host initally tried). SO that is correct only the message is new in 1.5by repetier - Repetier
I guess we need to dig deeper. It is in deed a reset before any send command was handled. The reset sequence takes < 2 seconds on connection start. That is where the first start comes from. So what makes it take 8 seconds and reset then. Looking in more dtail I see when it works you get aufter 3.5 seconds a sd init fail. When it resets again you do not get that message. So maybe sd initalizatby repetier - Repetier
Very strange. Here is how it looks for me with Marlin 1.0.2 on RAMPS+LCD 19:37:01.488 : Printer reset detected - initalizing 19:37:01.488 : start 19:37:01.488 : echo: External Reset 19:37:01.488 : Marlin1.0.2 19:37:01.504 : echo: Last Updated: Sep 10 2015 15:22:53 | Author: (none, default config) 19:37:01.504 : Compiled: Sep 10 2015 19:37:01.504 : echo: Free Memory: 3762 PlannerBufferBytes: 12by repetier - Repetier
Are you talking about the new 1.5.6 release? In the old there was the initalization started twice while host was resetting firmware. So depending on timing and luck you could get a resend error or not. After the fix I couldn't reproduce it any more.by repetier - Repetier
It should switch to float on AVR boards and to 64 bit int on arduino due based boards.by repetier - Repetier
You better once change EEPROM_MODE if you do not want top read your eeprom values. Do didn't read config. Too time intensive with all the questions I get. Once G30 works the rest will start working as well since it is just repeated usage of G30.by repetier - Repetier
Check your eeprom values. This normally happens when some values are set to nonsense values due to wrong eeprom initalization Happens if you had a different config on first upload.by repetier - Repetier
Please try the new 1.5.6 version. I think I have found a way that also Arduino Megas do not get resends. At least I didn't get one and I could remove the "Reset on connect" setting:-)by repetier - Repetier
Ok, I downloaded 1.6.5 and got the same problem. Investigation showed that the boards.txt had an error in VID and PID definition, which was ignored in older Arduino IDEs. I have updated firmware along with some minor changes in watchdog handling without that problem. Please replace boards.txt with new version.by repetier - Repetier
2 Resends is one to much for ping pong. So maybe there is a counting wrong and we are still overfilling. I have to check that when I get some time. I guess it needs quite some internal debugging, also yes it would be interesting if 1.0.6 didn't have it. Haven't testen 1.5.5 with ftdi since all active printers do have the other solution.by repetier - Repetier
Yes this is strange. The only printers not having the problem are the one having a FTDI driver instead of atmega 16U2. These also use a different windows driver. I never found out why this happens at startup and always thought it is a combination of .NET serial class and driver that makes some errors. With pingpong you do only send one command at a time so there is no piled up command list thatby repetier - Repetier
I always got this problem on connect with most printers. For me this is nothing new. Only thing is I can not say why firmware has no problem with first 3 lines and has a communication error on 4th line. You could try reducing buffer size to 120byte and see if it gets better. You will get such errors if buffers available are exceeded. Since I only get this problem on connection and not during prinby repetier - Repetier
I think that is the message you would get if you hit the reset button on the rumba board. Just try hitting hit after connection and you should get the same message. Next would be finding why the reset signal gets triggered. Look out for possible shorts and other cables that could induct wrong signals. It just needs a little spike to trigger reset.by repetier - Repetier
Other users with that problem choosed to downgrade the kernel to previous version. That was on a ubuntu version where 1.3.13-46 came as an update, so this was possible.by repetier - Repetier
The only thing it uses is where the crash happens and that is mono. But if I forget the error at the end, which you can ignore, it is always the thread handling that crashes and that reminds me that there is a bug in linux kernel that causes mono to do exactly this. Here comment from our forum: There is a incompatibility/bug introduced in kernels from 3.13.0-46 that causes multithreaded mono apby repetier - Repetier