Repetier
About
- Username
- Repetier
- Joined
- Visits
- 2,088
- Last Active
- Roles
- Administrator
Comments
-
Then in Repetier-Host run M115 to see which firmware it really is and not the baud rate.
-
Somethink like that. To have no interruptions we have to optimize sending data. A reset is detected by seeing a "start" in firmware response. Until then old job is just sending and it could be that between reset and start some commands get through. …
-
To explain I would need to see full log around the error not just error message. In principle both use same communication system, just 2.0.5 has some more cases to test as it knows newer firmware better. But I do not really expect that this causes p…
-
First don't use string. We do not use any dynamic memory allocation in firmware. Better use char array and sprintf instead. PSTR ensures the string is stored in flash data section on compilation. You can not use that with dynamic variables! Please …
-
You need at least Apache 2.4 to be able to proxy websockets. My bet is on a wrong setup for the websocket proxy. Apache has a special module for this, but please do not ask how to setup. We have an example for nginx where oyu might take a look at on…
-
See also http://reprap.org/wiki/Melzi search for FTDI problems. If you have a fake FTDI depending on installed driver it changes data or does other nasty things. Not sure but could also be a reason.
-
If homing already fails it is a firmware config or hardware error. Stepper drivers have a pin for direction. If that does not work - either connection broken or chip it will only go in one direction. One simple test is to use socket for second extr…
-
Ok, /dev/serial/... is already the right right port. Leaves firmware and baud rate. Setting repetier-firmware on marlin will make big problems. Vice versa it works better but also not perfect, so make sure firmware is set correctly.
-
No, error did not depend on firmware. At least directly. Maybe having faster communication with smaller packets made the timing worse in your case, but that is speculation. So for tomorrow my only plan is to fix server issues and make a new release …
-
@mpl You are my hero. At first I feared the solution lies in the missing 25 threads but the most critical was included and from there I could in deed find the deadlock. The problem arises at the end of print when an event gets send and a webbrowser…
-
Are you using the bootloader to upload? There are 2 ISP connectors so when using ISP and you take the one for usb->serial it could be a different chip. But I never heard a chip has changed the id. So if using bootloader just try again or try with…
-
Fill in the configuration files in marlin, compile and upload firmware. But it sounds like you do not have the original configuration.h file. There are quite some parameters and it would be helpfull to have the old one as you only want to change th…
-
It was worth the guess. So you do z max homing I guess and can move down to z=0 normally. What happens if you omit G1 Z-10 F9000 ;Z - 10mm host will go back to stored position anyway on continue.
-
If your z probe is also z min endstop you need to disable ALWAYS_CHECK_ENDSTOPS otherwise it will not go down once it triggers and being inductive it triggers for z> 0.
-
You must configure homing to always work even if you are already down. If you use a sensor that triggers only for z > 0 you can tell firmware to go up a bit before homing (at least in dev version) which solves such problems.
-
You need to increase the steps per mm for x and y by 3.6% then. This is done in firmware and depedning on configuration you can also change it in eeprom. In Marlin it is only permanent if eeprom was enabled in config.
-
Does the read temperature rise while being blocked? Some heat commands block communication until target temperature is reached, so watch temperature graph if that happens. Wrong configuration of heating parameter especially max PWM being too low can…
-
diagonal length / horizontal radius ratio mismatch is the main reason for a big bump/dome with center as apex. So change one of them to fix it. Normally you can measure diagonal length quite exactly so I would change horizontal radius. You can also …
-
No. M600 blocks communication until it is finished. If you want tocontrol from host/server use a pause instead and do filament change action on host/server side.
-
When you are not printing, you could also try the sequency just to feel comfortable in case it happens in earnest. On second run the install can of course be omitted.
-
You can not copy settings, sorry. Depending on the slicer you use names may vary a bit but it the most important variables should be quite clear. Speeds are most important and the width on different parts is also important, the rest is more or less …
-
You enter the settings save and hit connect. That creates a configuration file for NetWork Manager to connect and disables AP. From there on NetworkManager should take care of it. I have tested my pi 3 with it on 3 routers with different settings. W…
-
Ok just an idea - try G33 R0 to delete the distortion map. Maybe first check values with G33 L0 at least if you are using dev version. Default config for distorion map is to start at 1mm and if you have big corrections stored at that point it wi…
-
Yes, if you have a copy of config just copy that file back and restart and everything is fine again. Read this thread https://forum.repetier.com/discussion/4053/new-image-for-sd-has-a-bug#latest for mor einfos and how to help us finding the source…
-
That is a problem we did not find as it happens only to some users under some timing conditions. What exactly is not clear. Please refer to this thread https://forum.repetier.com/discussion/4053/new-image-for-sd-has-a-bug#latest for for to prepare…
-
Yes I mean that line but not on connection. When you initially connect the host resets the printer so that one is fine.
-
0.85.2 is not slow, but it has some new features requiring to parse all g-code files. So after upgrading it rescans all g-code files (which 0.80.3 did then finish). If you would not have switched back everything would be normal again. It is just ha…
-
#define Z_PROBE_Z_OFFSET 0 is what should be 0 RAyWB mixed these. But in any case you should also check it in eeprom (bed coating it is named there). If you have a inductive endstop this can in deed make it stop 1mm before bottom. Otherwise increas…
-
Open log window (expert mode in host required) and see what firmware writes. Most likely it sais something about decoupled printer stopping everything. Also it might reset when that happens - you should then see a "start" in log appear.
-
You open the sources, edit required setting and compile and upload it again using the Arduino IDE.