Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DV 2.0A with Repetier 0.92 Generic Issues
#1
Hi Guys,
From what I have been reading in various forums, there appears to be people have the same generic problems trying to get their printer to work properly.
Some use Repetier Host, others use Simplify 3D and the issues are similar.
they are:
1. - Extruders are swapped and instead of emptying into their respective waste bins (ie. Left Ext into Left Bin, Right into right) they empty/ooze on the wrong side of the build plate.
2. - X, Y and Z offsets for home position are not right and need to be adjusted (especially Z as nozzles run into the glass plate)
3. - Printing with the wrong nozzle
4. - after pressing emergency stop during a print, the bed down function does not work

I am sure there are some others that I cannot think of right now, but it seems that most of us are having the same problems with their DV 2.0's
Has anyone out there actually addressed these problems and got their machine to work right?
Please share your solutions with the rest of us....please..
Reply
#2
I've been using Repetier for a while and have never seen issues 1, 2, or 3 and all of those would come down to your slicer configuration being wrong, not the firmware.

1. This is once again a slicer configuration issue. Depending on when you flashed Repetier, you could have different options for nozzle cleaning but as of right now you can use G-Code to select which hotend to clean. See pull - https://github.com/luc-github/Repetier-F...2/pull/131 & https://github.com/luc-github/Repetier-F...2/pull/134 & https://github.com/luc-github/Repetier-F...2/pull/138 . The path was adjusted for 2.0 machines to allow the nozzle to clear the wiper because there is not enough travel to do it normally, M100 was adjusted to allow specific nozzle selection so you don't waste time cleaning nozzles you don't use. If Left/Right confuses you, see this issue https://github.com/luc-github/Repetier-F...issues/137 where Luc explains the logic. S3D can easily be changed so that Left Extruder = Left Extruder on the printer just by changing the tool number.

2. I don't understand your issue? Z0 should not cause the bed to touch the hotends at all on a stock printer and the homing trigger for Z is Z0. If it does then you have messed with the leveling screws or moved the homing flag for Z. The only thing the hotends could hit at 0 are the hold down/probe tabs on the corners. Even with E3D hotends attached, there is more than enough room in the leveling system to compensate for the height difference so you can use the Z home location as 0.

3. The extruder being used to print with is determined by G-Code.

As for number 4 you should probably open an issue on Github for it.
Reply
#3
(05-03-2016, 11:45 AM)tjb1 Wrote: I've been using Repetier for a while and have never seen issues 1, 2, or 3 and all of those would come down to your slicer configuration being wrong, not the firmware.  

1. This is once again a slicer configuration issue.  Depending on when you flashed Repetier, you could have different options for nozzle cleaning but as of right now you can use G-Code to select which hotend to clean. See pull - https://github.com/luc-github/Repetier-F...2/pull/131 & https://github.com/luc-github/Repetier-F...2/pull/134 & https://github.com/luc-github/Repetier-F...2/pull/138 .  The path was adjusted for 2.0 machines to allow the nozzle to clear the wiper because there is not enough travel to do it normally, M100 was adjusted to allow specific nozzle selection so you don't waste time cleaning nozzles you don't use.  If Left/Right confuses you, see this issue https://github.com/luc-github/Repetier-F...issues/137 where Luc explains the logic.  S3D can easily be changed so that Left Extruder = Left Extruder on the printer just by changing the tool number.

2. I don't understand your issue?  Z0 should not cause the bed to touch the hotends at all on a stock printer and the homing trigger for Z is Z0.  If it does then you have messed with the leveling screws or moved the homing flag for Z. The only thing the hotends could hit at 0 are the hold down/probe tabs on the corners.  Even with E3D hotends attached, there is more than enough room in the leveling system to compensate for the height difference so you can use the Z home location as 0.  

3. The extruder being used to print with is determined by G-Code.  

As for number 4 you should probably open an issue on Github for it.

tjb1, thanks for your reply.

I am surprised you say you have never seen issues 1, 2 and 3 as the forums are full of people with the same issues? Maybe you are one of the lucky ones.
For me this is all new and I had no idea what I was delving into when I bought the printer. I dont understand G-Code I'm not into this stuff.
I have looked at all of your links and sort of understand whats going on but have no idea of what exactly I need to do. Its way over my head.
If you have already sorted this stuff out, would you kindly be able to Export your fff file in S3D and email to me to try out. Then maybe I can do some printing 
and have some time to learn this stuff. 
cheers..
Reply
#4
(05-05-2016, 10:51 PM)nickb00 Wrote:
(05-03-2016, 11:45 AM)tjb1 Wrote: I've been using Repetier for a while and have never seen issues 1, 2, or 3 and all of those would come down to your slicer configuration being wrong, not the firmware.  

1. This is once again a slicer configuration issue.  Depending on when you flashed Repetier, you could have different options for nozzle cleaning but as of right now you can use G-Code to select which hotend to clean. See pull - https://github.com/luc-github/Repetier-F...2/pull/131 & https://github.com/luc-github/Repetier-F...2/pull/134 & https://github.com/luc-github/Repetier-F...2/pull/138 .  The path was adjusted for 2.0 machines to allow the nozzle to clear the wiper because there is not enough travel to do it normally, M100 was adjusted to allow specific nozzle selection so you don't waste time cleaning nozzles you don't use.  If Left/Right confuses you, see this issue https://github.com/luc-github/Repetier-F...issues/137 where Luc explains the logic.  S3D can easily be changed so that Left Extruder = Left Extruder on the printer just by changing the tool number.

2. I don't understand your issue?  Z0 should not cause the bed to touch the hotends at all on a stock printer and the homing trigger for Z is Z0.  If it does then you have messed with the leveling screws or moved the homing flag for Z. The only thing the hotends could hit at 0 are the hold down/probe tabs on the corners.  Even with E3D hotends attached, there is more than enough room in the leveling system to compensate for the height difference so you can use the Z home location as 0.  

3. The extruder being used to print with is determined by G-Code.  

As for number 4 you should probably open an issue on Github for it.

tjb1, thanks for your reply.

I am surprised you say you have never seen issues 1, 2 and 3 as the forums are full of people with the same issues? Maybe you are one of the lucky ones.
For me this is all new and I had no idea what I was delving into when I bought the printer. I dont understand G-Code I'm not into this stuff.
I have looked at all of your links and sort of understand whats going on but have no idea of what exactly I need to do. Its way over my head.
If you have already sorted this stuff out, would you kindly be able to Export your fff file in S3D and email to me to try out. Then maybe I can do some printing 
and have some time to learn this stuff. 
cheers..

can you share the forums you mention ?
Reply
#5
(05-05-2016, 11:21 PM)luc Wrote:
(05-05-2016, 10:51 PM)nickb00 Wrote:
(05-03-2016, 11:45 AM)tjb1 Wrote: I've been using Repetier for a while and have never seen issues 1, 2, or 3 and all of those would come down to your slicer configuration being wrong, not the firmware.  

1. This is once again a slicer configuration issue.  Depending on when you flashed Repetier, you could have different options for nozzle cleaning but as of right now you can use G-Code to select which hotend to clean. See pull - https://github.com/luc-github/Repetier-F...2/pull/131 & https://github.com/luc-github/Repetier-F...2/pull/134 & https://github.com/luc-github/Repetier-F...2/pull/138 .  The path was adjusted for 2.0 machines to allow the nozzle to clear the wiper because there is not enough travel to do it normally, M100 was adjusted to allow specific nozzle selection so you don't waste time cleaning nozzles you don't use.  If Left/Right confuses you, see this issue https://github.com/luc-github/Repetier-F...issues/137 where Luc explains the logic.  S3D can easily be changed so that Left Extruder = Left Extruder on the printer just by changing the tool number.

2. I don't understand your issue?  Z0 should not cause the bed to touch the hotends at all on a stock printer and the homing trigger for Z is Z0.  If it does then you have messed with the leveling screws or moved the homing flag for Z. The only thing the hotends could hit at 0 are the hold down/probe tabs on the corners.  Even with E3D hotends attached, there is more than enough room in the leveling system to compensate for the height difference so you can use the Z home location as 0.  

3. The extruder being used to print with is determined by G-Code.  

As for number 4 you should probably open an issue on Github for it.

tjb1, thanks for your reply.

I am surprised you say you have never seen issues 1, 2 and 3 as the forums are full of people with the same issues? Maybe you are one of the lucky ones.
For me this is all new and I had no idea what I was delving into when I bought the printer. I dont understand G-Code I'm not into this stuff.
I have looked at all of your links and sort of understand whats going on but have no idea of what exactly I need to do. Its way over my head.
If you have already sorted this stuff out, would you kindly be able to Export your fff file in S3D and email to me to try out. Then maybe I can do some printing 
and have some time to learn this stuff. 
cheers..

can you share the forums you mention ?

http://forum.repetier.com/search?Search=da+vinci+2.0A
https://github.com/luc-github/Repetier-F.../issues/94
these are just some of the ones I have found. Scroll through them to find the issues.

There is one from Repetier themselves who give a crappy excuse for an answer to people with all these issues.
In the end someone says I will wait untill these issues are fixes before I put Repetier 0.92 FW on my printer.
Sorry just cant seem to find that forum...always the way..
Reply
#6
Repetier really has nothing to do with this firmware besides it being the base. Luc has had to modify it so heavily to get it working on a Da Vinci that I wouldn't expect them to be able to support it.

Once again...

1. All in the slicer and it really has no effect on printing besides being a minor annoyance. If you really want "Left Extruder" in S3D to equal the left extruder when looking at the front of the printer you need to change to printing with left extruder and then open the extruder page and change the toolhead. T0 is the first extruder so you need to change the left one to T0 - see https://forum.simplify3d.com/viewtopic.php?f=8&t=1980

2. Do you have this issue or is this just what you have read? Like I said, the home point for Z is at Z0...if the nozzle hits you need to lower the bed using the adjustment screws. The only reason an offset would be needed would be if you modified the carriage to the point where you can't compensate for the difference in height with the bed leveling screws.

3. You need to pick which extruder you want to use in the slicer. It's likely using the correct one, you just have it configured wrong. See #1.
Reply
#7
Thanks for pointing out my github, so far all questions there have answers if you read well Big Grin

I do not follow repetier forum, that is correct because fw is a fork of repetier and repetier does not support Davinci he mention it several times.

as Tjb1 already answered  your questions 1 2 3  

4. - after pressing emergency stop during a print, the bed down function does not work


Yes, It does not work because emergency stop is like a power off / power on, all flags, positions are reset, so bed does not know the current position anymore and so disable the bed down command until Z homing is done, this is safety purpose

I may add a message explaining command is disabled until Z homing is done on screen to avoid confusion

Thanks for pointing this out
Reply
#8
(05-06-2016, 12:25 PM)luc Wrote: Thanks for pointing out my github, so far all questions there have answers if you read well Big Grin

I do not follow repetier forum, that is correct because fw is a fork of repetier and repetier does not support Davinci he mention it several times.

as Tjb1 already answered  your questions 1 2 3  

4. - after pressing emergency stop during a print, the bed down function does not work


Yes, It does not work because emergency stop is like a power off / power on, all flags, positions are reset, so bed does not know the current position anymore and so disable the bed down command until Z homing is done, this is safety purpose

I may add a message explaining command is disabled until Z homing is done on screen to avoid confusion

Thanks for pointing this out

Hi Luc,
Yes there are answers for my questions but unfortunately for me I dont understand G-Code much and it looks like all the fixes are done via GCode.
So I would not know which one to pick and what to do with it. There are so many codes its very confusing.
Has anyone maybe put all the fixes together in one spot where a simple cut and paste can be done?
cheers
Reply
#9
(05-09-2016, 12:13 AM)nickb00 Wrote:
(05-06-2016, 12:25 PM)luc Wrote: Thanks for pointing out my github, so far all questions there have answers if you read well Big Grin

I do not follow repetier forum, that is correct because fw is a fork of repetier and repetier does not support Davinci he mention it several times.

as Tjb1 already answered  your questions 1 2 3  

4. - after pressing emergency stop during a print, the bed down function does not work


Yes, It does not work because emergency stop is like a power off / power on, all flags, positions are reset, so bed does not know the current position anymore and so disable the bed down command until Z homing is done, this is safety purpose

I may add a message explaining command is disabled until Z homing is done on screen to avoid confusion

Thanks for pointing this out

Hi Luc,
Yes there are answers for my questions but unfortunately for me I dont understand G-Code much and it looks like all the fixes are done via GCode.
So I would not know which one to pick and what to do with it. There are so many codes its very confusing.
Has anyone maybe put all the fixes together in one spot where a simple cut and paste can be done?
cheers

They are not fixes...there is nothing wrong with the firmware.  You need to take the time to learn.  Why did you flash a custom firmware if you don't want to learn about the g-code?
Reply
#10
(05-09-2016, 01:25 PM)tjb1 Wrote:
(05-09-2016, 12:13 AM)nickb00 Wrote:
(05-06-2016, 12:25 PM)luc Wrote: Thanks for pointing out my github, so far all questions there have answers if you read well Big Grin

I do not follow repetier forum, that is correct because fw is a fork of repetier and repetier does not support Davinci he mention it several times.

as Tjb1 already answered  your questions 1 2 3  

4. - after pressing emergency stop during a print, the bed down function does not work


Yes, It does not work because emergency stop is like a power off / power on, all flags, positions are reset, so bed does not know the current position anymore and so disable the bed down command until Z homing is done, this is safety purpose

I may add a message explaining command is disabled until Z homing is done on screen to avoid confusion

Thanks for pointing this out

Hi Luc,
Yes there are answers for my questions but unfortunately for me I dont understand G-Code much and it looks like all the fixes are done via GCode.
So I would not know which one to pick and what to do with it. There are so many codes its very confusing.
Has anyone maybe put all the fixes together in one spot where a simple cut and paste can be done?
cheers

They are not fixes...there is nothing wrong with the firmware.  You need to take the time to learn.  Why did you flash a custom firmware if you don't want to learn about the g-code?
I just thought it was all sorted out and it worked like it should, and thats why many others had done it. I didn't even know about GCode before I flashed it. 
Also I hate being forced buying a Company's Filament that is way over priced! Greed is a disgusting thing!
Reply
#11
(05-09-2016, 10:07 PM)nickb00 Wrote:
(05-09-2016, 01:25 PM)tjb1 Wrote:
(05-09-2016, 12:13 AM)nickb00 Wrote:
(05-06-2016, 12:25 PM)luc Wrote: Thanks for pointing out my github, so far all questions there have answers if you read well Big Grin

I do not follow repetier forum, that is correct because fw is a fork of repetier and repetier does not support Davinci he mention it several times.

as Tjb1 already answered  your questions 1 2 3  

4. - after pressing emergency stop during a print, the bed down function does not work


Yes, It does not work because emergency stop is like a power off / power on, all flags, positions are reset, so bed does not know the current position anymore and so disable the bed down command until Z homing is done, this is safety purpose

I may add a message explaining command is disabled until Z homing is done on screen to avoid confusion

Thanks for pointing this out

Hi Luc,
Yes there are answers for my questions but unfortunately for me I dont understand G-Code much and it looks like all the fixes are done via GCode.
So I would not know which one to pick and what to do with it. There are so many codes its very confusing.
Has anyone maybe put all the fixes together in one spot where a simple cut and paste can be done?
cheers

They are not fixes...there is nothing wrong with the firmware.  You need to take the time to learn.  Why did you flash a custom firmware if you don't want to learn about the g-code?
I just thought it was all sorted out and it worked like it should, and thats why many others had done it. I didn't even know about GCode before I flashed it. 
Also I hate being forced buying a Company's Filament that is way over priced! Greed is a disgusting thing!
many people shared their start/end GCODE search on forum
https://forum.voltivo.com/showthread.php...light=cura
https://forum.voltivo.com/showthread.php...hlight=s3d
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)