Posts made by scottpickstock

@dc42 right ok, i will get a wifi repeater for starters, is the fact the wifi turns off on the duet down to loss off connection and is there something i can do wile connected directly to restart it.

You will have to pardon my ignorance but can you tell me why my phone/laptop etc work file in my house and garden but the duet wont?
genuine question. i ask because i believe my setup to be a good representation of an average user and having it sitting on my bench next my printer no more than 5m and one wall from my router.

So i have been busy with work but finally got around to looking at the wiki that @dc42 suggested. i ran the M122 command and got the below out.

=== Network ===
Slowest loop: 14.21ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.21
  WiFi MAC address 84:f3:eb:82:dc:78
  WiFi Vcc 3.45, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 15072
  WiFi IP address 192.168.0.27
  WiFi signal strength -76dBm, reconnections 0, sleep mode modem
  Socket states: 2 4 0 0 0 0 0 0
  === Expansion ===

i mentioned previously that the blue LED on the wifi modal went out as well, here is the readout from one of those instances.

=== Network ===
<-Slowest loop: 1.27ms; fastest: 0.01ms
<-Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
<-HTTP sessions: 0 of 8
<-- WiFi -
<-Network state is running
<-WiFi module is idle
<-Failed messages: pending 0, notready 0, noresp 0
<-WiFi firmware version 1.21
<-WiFi MAC address 84:f3:eb:82:dc:78
<-WiFi Vcc 3.45, reset reason Turned on by main processor
<-WiFi flash size 4194304, free heap 19408
<-Socket states: 0 0 0 0 0 0 0 0
<-=== Expansion ===

I know the signal is bad at -76 however but its in the next room no more than 5m away from the router with one wall. Im hoping this isn't the issue as it makes it rather pointless. moving the router closer in not really an option and Im not moving the printer into my living room.

Will go through the Wiki and see if that helps, thanks.

@timcurtis67

but i cant connect to it to send the command.

@hayseed_byte

yea, i kinda miss the simplicity of throwing an SD card at it. At the minuet i dont see any benefit of using wifi, if anything more hassle. i dont have the outright knowledge to figure all this out. just frustrated.

Hi Guys, i feel i have been plagued with connection issues since i got my board, it constantly times out and i have to click "connect" several times before it finally connects, some times i end up turning it off and on again.

anyways the last two days i have really been struggling to get it to connect, i have also noticed that the blue LED on the wifi...thing goes off so i do the old off and on.

question: does this sound like a software thing or a hardware fail?

WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.01beta2(RTOS) (2018-07-14b5)
WiFi Server Version: 1.21
Web Interface Version: 1.21.1

@scottpickstock

second update.

so it seem my previous issue of the y moving while jogging z could of been (most probably defiantly) my fault. While tidying up the code I noticed in home.z I had put m5...something something X0 Z1 Z2:3 U9 E4 P3.

Anyways I have cleaned it all up and so far everything is fine.

just an update,

so, I first changed the code to assign U back to driver 9 after homing and this sorted the z axis moving up on the u axis while jogging x or y. however, I had a new issue in that when I move z up 10mm it doesn't move …..the y axsis moves instead, when I then move the y axis +10mm I can only move it back 10mm and no further as it thinks its position is +10mm from 0 when its now actually +110.

on updating to 2.01 beta that issue is still present, I will go through the files again and do some tweaking to see if I can sort it.

any more advise in the meantime is welcome otherwise I will be back with an update.
EDIT: once again my config.g file has gone, 5th time in two days. Hmmmmm

@dc42

that's great, I will try the easy option first as a test then look at the slightly more complicated option of updating of the firmware.

much appreciated.

@dc42 said in Z (U) axis moves while moving only x or y?:

I believe this has already been fixed in firmware 2.01beta2.

The current FW is "Firmware version 2.0(RTOS) (2018-06-05b3)

Just realised you typed 2.01 beta, is this a known issue already? Searched and searched but couldn't find anyone with the same problem.

I will look into swapping the FW out.

Thanks.

Here is a short clip, im using matter control to move the x axis in 1mm increments and as you will see the u axis is moving up and down on its own accord.

that's with U configured to driver 9 in config,g, one other note is its not running within the limitations set in config.g as its moving hella fast.

https://youtu.be/gSHhefFFDCY

@deckingman

I have just done that very thing, I read an old thread where dc42 said to assign it to an unused driver, thing is it still does it, im thinking (that's dangerous as im no expert) that a simple G1 X10 shouldn't interfere with any other driver. I have just typed in G1 X10,20,30,40....all the way to 180 and it still did it. weird.

BTW dc42 said to do that to avoid any accidental U commands....or something to that effect.

weird how its still doing it when u is assigned to driver 9 (exluding the homez and homeall).

as for the SD card its worth trying, is it easy to do, am I able to just transfer everything over or is there a special procedure?

@deckingman said in Z (U) axis moves while moving only x or y?:

So, I don't think you can have Z mapped to 2 and 3 as well as U being mapped to 3. I don't use multiple Z screws but I do have dual CoreXY gantrys. So my mapping is

M584 X0:3 Y1:4 Z2 U10 V11 E5:6:7:8:9 P3;

Which means that X uses motors 0 and 3 and Y uses motors 1 and 4 and U and V are hidden. BUT, for homing, the drives are re-mapped as follows:

M584 X0 U3 Y1 V4 P5;
That line is at the start of the homing file, then at the end of the homing file, they are mapped back to X0:3 Y1:4 etc.

So I'd say you need to do something similar.

Edit - so leave out the U from config g and just have M584 X0 Y1 Z2:3 E4 P3
Then in your homing file, start with M584 X0 Y1 Z2 U3.

I will say though for the most part it was working, during homing they both home to the switches then on moving z in the control area they worked fine, just some how x and y occasionally control it.

@deckingman said in Z (U) axis moves while moving only x or y?:

So, I don't think you can have Z mapped to 2 and 3 as well as U being mapped to 3. I don't use multiple Z screws but I do have dual CoreXY gantrys. So my mapping is

M584 X0:3 Y1:4 Z2 U10 V11 E5:6:7:8:9 P3;

Which means that X uses motors 0 and 3 and Y uses motors 1 and 4 and U and V are hidden. BUT, for homing, the drives are re-mapped as follows:

M584 X0 U3 Y1 V4 P5;
That line is at the start of the homing file, then at the end of the homing file, they are mapped back to X0:3 Y1:4 etc.

So I'd say you need to do something similar.

Edit - so leave out the U from config g and just have M584 X0 Y1 Z2:3 E4 P3
Then in your homing file, start with M584 X0 Y1 Z2 U3.

On the face of that didn't seem to work, without defining U3 the stepper would not move.... I can not continue testing for a bit as for the 3rd time today my config.g file has gone.....keeps timing out and some how the config,g file goes.

@gizmotronx5000

As the other chap said, I have 2x end stop switches so the P3 parameter hides the u axis and the z2:3 couples them together. In the home.g and home.g there is a M584 Z2 U3 P4 which separates them, they then home separately before an m584 Z2:3 P3 which syncs them back up.

Homes fine, but somthing is amiss.

Hi, So I have just set up dual z axis on my Cartesian printer, the type with dual end stops and all seemed to be working well during simple testing. my issue is though that when I mover the Y or X in say 10mm increments at some random point the Z(U) will move up 10mm, but only the U axis.

https://youtu.be/gSHhefFFDCY

Y +10MM can equal Y+10 & Z(U) +10MM, I can then press the Y+10mm again and it will go Y+10mm and Z(U) -10mm back to end stop.

it happens on both the x & y randomly but when the z(u) axis goes up 10mm the next click of say x+10mm will bring the z(u) axis back down.

hope that explains it well.

any help much appreciated.

; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1

M584 X0 Y1 Z2:3 U3 E4 P3

M16 X16 Y16 Z16 U16 E16 I1 ; Configure microstepping without interpolation
M92 X80 Y80 Z400 U400 E800 ; Set steps per mm
M566 X900 Y900 Z12 U12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z180 U180 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z250 U250 E250 ; Set accelerations (mm/s^2)
M906 X850 Y900 Z850 U850 E850 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 U0 S1 ; Set axis minima
M208 X300 Y300 Z400 U400 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 U1 S0 ; Set active low endstops

; Z-Probe
;M558 P0 H5 F120 T6000 ; Disable Z probe but set dive height, probe speed and travel speed
;M557 X15:285 Y15:285 S20 ; Define mesh grid

Guys....My bad.

So with everyone saying it's easy to upload pics I thought I would give it ago but then decided to go one better and make a video. Anyways while tidying up the work bench I removed the cover from the duet I noticed the colour is different from the plug on the stepper motor , i had thought I checked this however tiredness must of dropped my IQ 30 points.

In a nut shell the wires were wrong, I had some how got caught up in making sure the pins each end were the same without knowing for fact that they need to be wired that way.

Stupid mistake, sorry to waste everones time but thanks all the same. Goes to show checking the obvious can be the way forward.

Yea I checked that and they both go red, blue, green and black. This leads me to believe I could only plug it in the wrong way and reverse motor direction. I would put a picture for what it's worth but it seems forums of 2018 still need links.

It's got me scratching my head to sure.

Hi guys

I feel this is a stupid question at it's basic level however I have been left perplexed by a simple cable. So I bought a simple stepper motor cable to add dual z to a Cartesian style printer but when I plugged the cable in to the zb slot I got an error saying short to ground on driver 2 (z driver). I checked the wiring which was fine the stepper was known to be good. I jumped to the conclusion that there was an issue with that driver one way or another. I went down the rout of assigning E0 as U and configured it for independent endstops. However once again I got an error on driver 3 using this cable. I used the extruder cable and all worked fine. I checked with a multi meter and there are no shorts between phases.

Question: what the hell can a cable do to cause this?

Anyone encountered this?

Thanks,

@obeliks said in Cant home z to endstop:

@scottpickstock Haha, please don't.

Don't worry, I couldn't home my z axis, I have no hope of homing in on you haha. cheers again.