Duet3 config Frustration
-
That is 100% correct
But no-where does it actually state (that I could find) that to get the main board and tool-board to communicate with each other, that you should use that address in the C parameter of each required G-Code Command.
That is exactly what I mean about guides that "assume" that the user has prior experience with a certain types of technology, if the user has never used or encountered the tech & what is required to get it up and running how can they know if its not specifically mentioned.
Now this is not having a go, and as an Engineer I understand the trap we can fall into, when someone asks about something (something we perceive as so simple we never give it a second thought) something that we have used and understood for years so much so that when some one asks about it we are like "eh why dont you know that, that's easy"
Yes its easy for some of us because we have been used to it (and been used to using a certain technologies for a long time) but for those who might not have ever used it before we need to change out our approach, and look at it from their perspective.
-
@CaLviNx said in Duet3 config Frustration:
That is exactly what I mean about guides that "assume" that the user has prior experience with a certain types of technology, if the user has never used or encountered what is required how can they know if its not specifically mentioned.
No argument there. I'm in the same boat. The tool board canbus expansion paradigm probably makes more sense to those in the target market who may already be familiar with canbus, but for the neophyte it's not intuitive. I don't have access to the hardware myself so I haven't used it to know what the major sticking points between documentation and reality are yet. Best I can do is take complaints and suggestions for improvement and update as we go.
-
A single sentence in the documentation explaining the requirement could save people (me included) hours of frustration.
And with the can-bus tech becoming more common possibly someone could write a small section in the documentation with a brief description of the tech and how it is used/works, requirements etc.
I know and understand that when I write technical curriculum material it is a fine line of trying to get the technical point across in such a way that is not going to make the students eyes roll to the back of his/her head and they pass out, But we always make a point of giving a brief on how the technology (or specific component) works to try to provide a solid foundation on the subject.
-
@CaLviNx said in Duet3 config Frustration:
And with the can-bus tech becoming more common possibly someone could write a small section in the documentation with a brief description of the tech and how it is used/works, requirements etc.
Well there is this: https://duet3d.dozuki.com/Wiki/CAN_connection
I'll see about linking to that page from the other duet 3 hardware pages.
-
@BlueDust said in Duet3 config Frustration:
All I know for sure is that this tool isn't working.
M563 P1 S"RightExtruder" D0 H0 F0:3
But the fans work fine on the Left Extruder.
M563 P0 S"Left Extruder" D1 H1 F1:2I have made a handful of changes to Fx:x on both the left and right extruders and haven't seen any changes or swaps of the fans. Always works/can't break it making those changes. I don't know what they do.
Saying that, I fixed the right fan. It was unplugged. I thought I wrapped electrical wire around all the fan wire connections to make sure they didn't come apart while moving (connections are inside of the cable sleeve, and not seen without unwrapping the sleeve)... Will fix that.
-
@BlueDust Thanks, it's fixed now:
-
I have noticed another weird temp thing a few times, but I am not 100% sure how to reproduce it...
It seems that if I manually set (have yet to print anything), the temp on two extruders, I can only get the temp to heat up on one of them. Even though there is a temp listed, it does increase. I have to click on it a 2nd time and click enter.
I just did this...
I set the temp on two different tools (active and standby) . On the tool that was off, and moved it to standby, and then moved to Active, it wouldn't increase while in either standby or active. I had to click the temp and hit enter (didn't re-input the temp a 2nd time).Is this a bug or expected? If this is a possible bug, I will have to pay more attention what I am doing when manually playing with the temps incase I see this again.
-
@dhusolo said in Duet3 config Frustration:
Checkout my github. I have configs i've made and shared for the BLV printers. I don't know how IDEX are setup but use Cube RRF 3.1.1 but be sure to change it to what you need it for. There's wiring diagrams in the repository.
Looking at your Duet3 wiring png... It shows you have a BLTouch v2.0 in the picture. As I had to buy a new BLTouch, I received a v 3.1. is the wiring the same for both versions?
Thanks! -
@BlueDust said in Duet3 config Frustration:
As I had to buy a new BLTouch, I received a v 3.1. is the wiring the same for both versions?
yes. it should work.
one user had to enable 3.3v logic. -
@Veti
Does that mean they used the 3.3v instead of the 5v? -
@BlueDust I wouldn't read too much into it. That particular case could have been any number of things.
However, if you find you're having troubles here is the relevant doc from antclabs on how to switch between.
-
@Phaedrux
AntLabs says the BLTouch 3.1 is 5v, and don't want to confuse myself any more on this if I don't have to. I was just curious as I remember older BLTouches needed resistors or something to make them work on the Duet boards. The documentation on Antlabs website in relation to Duet seems old and trying to keep this simple as it was on the Duet2Eth as I use a BLTouch 2.2. They seem to change things up often and I don't mind making a mistake and fixing it, but don't want to break anything and have to buy a new one for something dumb I did (like not reading the instructions).3Pin: Brown (GND), Red (+5V)
Orange (control signal)
2Pin: Black (GND) White (Zmin)As always. Thanks for the help!
-
Duet3 is 5v tolerant so you shouldn't need to change anything on either the duet or BLTouch. It's been that way for a long time now. Should be plug and play.
-
@Phaedrux
Is the GPIO Port # referring to the io#.in? Where the number would match where the BLTouch is plugged in?M280 P0 S80 ; set 80deg servo position on GPIO port 0
Thanks
Fun, that 3 letter word with "u" in the middle.
-
@Phaedrux
I read something on one of the Z Probe M commands and it made me think it was a heater.
Self test works now... -
@BlueDust said in Duet3 config Frustration:
@Phaedrux
Is the GPIO Port # referring to the io#.in? Where the number would match where the BLTouch is plugged in?M280 P0 S80 ; set 80deg servo position on GPIO port 0
Thanks
M280 P0 refers to the M950 S0
The pin name refers to the servo control pin and the probe signal input pins.
Did you get it figured out?
-
@Phaedrux
Yes, I think I figured it out as I can now home the printer, and BLTouch is working. But found another issue, this time with my PanelDue. I am trying to find the max/min places for each tool using the PanelDue and it's not working.My PanelDue is only updating temp/axis location after reset (of the PanelDue), but appears to stop after I start moving the motors (homing right now). I am guessing it is interference... Controlling the printer always works. Updating current info on the screen is the only thing that stops working.
PanelDue is on 3.2, and Duet3 is on 3.1.Thanks!
-
@BlueDust said in Duet3 config Frustration:
PanelDue is on 3.2, and Duet3 is on 3.1.
Stick with 1.24 on the Panel for now. Will work better when the Duet is also on 3.2.
-
OK thanks!
Any idea when RepRap 3.2 will be released? I am only looking for a guess.
Sometime this month? -
I just wanted to see this new printer print. And guess what, it's printing. But the part fan isn't turning on automatically. I have to turn it on manually. This must be that F setting on the tool I was playing with before but have no idea how to set it... As I can manually turn the fan on, and it turns on, on the correct tool from DWC... I am not sure what to do to fix this at the moment.
