Firmware 2.02RC6 released

[Phaedrux]

Completed a 16 hour print without issues.

[insertnamehere]

Can I just ask if anyone has used pause and resume successfully with RC6?

I'm not sure that a problem exists in RC6, however, I upgraded yesterday and was printing calibration cubes to make some changes to fix an infill problem. On 2 different prints I hit paused to check the infill pattern and when I resumed the hotend returned to a point above its last location and continued printing. Like it skipped a layer completely.

Has anyone seen anything like that with RC6?

I'll go back to RC5 and try it again.

[Phaedrux]

@insertnamehere rc5 had an issue with pause and resume where some moves were not completed successfully. Check the rc5 thread for details. I have tested pause and resume on rc6 and it seems to behave normally again.

What do you have in your pause.g and resume.g macros?

[insertnamehere]

@phaedrux Thanks, that's good to know it is not the firmware.
I'll check my Z axis for binding, most likely a mechanical problem.

[frafa]

Hi David

in progress with my Scara
Homing ok

Test print prtial ok
print ok but in relative position compared to homing

After print i test this macro file content to debug:

G28
G90		;Absolute Positioning
G1 X150 Y150 F2500····

Return error on G1: M98 P"0:/macros/test" Error: G1/G2/G3: intermediate position outside machine limits

Second test:

G28
G90		;Absolute Positioning
G1 X150 Y150 F2500
G1 X0 Y0 F2500

Error: G1/G2/G3: intermediate position outside machine limits 16:24:50 M98 P"0:/macros/test" Error: G1/G2/G3: intermediate position outside machine limits

the arm does the homing, then it makes a mistake, it moves in relative coordinates and not absolute in x150 / y150 (partial ok, not absolu)
but afterwards it is supposed to go to x0 / y0, and it goes to x0 / y300 ???

I think the concern is there is an inverted axis?

I think that since the beginning of my tests on 2.02RCx the problem with the absolute movements is here!

[Ckostikas]

Hi,

After the latest update to RC6 and web interface 1.22.5 I am getting this error every time I leave the page open for more than 10-15 mins.

Fully updated MacOS

Also sometimes I click on a gcode to start printing, I click on the confirmation message but it does nothing, like I never selected it. I have to do an emergency stop and click on the gcode once again to get it going.

Thanks!

[Phaedrux]

@ckostikas that's a feature of OSX to alert you to apps that are using resources. I'm not sure but I think you can tell it to ignore certain apps.

Have you tried chrome?

[Ckostikas]

@phaedrux No I haven't but I'll give it a go.

The thing is that the browser lags after that and the safari just consumes all my RAM so I was thinking maybe a bug on web interface or something just because I didn't have anything similar before updating to rc6 and 1.22.5.

[lolorc]

Hi there,

I'm still not able to upload files to my duet wifi, I'm using latest firmwares, duetwifiserver is still the old 1.21.
Still using cisco access points and linux computers, still loads of tcp dup, tcp retransmission, tcp window full...
and no single issue with a raspberry 10cm away connected to the same ap...

I guess it's not enough just to use a esp8266 and expect it to work in a lot of different environments.

I've been uploading gcodes and firmware through the usb serial port for a while now, not the end of the world...

Happy Xmas.

[Phaedrux]

@lolorc Sorry to hear that. Does your access point have a good 2.4Ghz band?

[mikebridge]

i see the release notes for RC07, but no RC07 files

[dc42]

@mikebridge said in Firmware 2.02RC6 released:

i see the release notes for RC07, but no RC07 files

I hope to release RC7 later today.

[dc42]

@lolorc said in Firmware 2.02RC6 released:

Hi there,

I'm still not able to upload files to my duet wifi, I'm using latest firmwares, duetwifiserver is still the old 1.21.
Still using cisco access points and linux computers, still loads of tcp dup, tcp retransmission, tcp window full...
and no single issue with a raspberry 10cm away connected to the same ap...

I guess it's not enough just to use a esp8266 and expect it to work in a lot of different environments.

I've been uploading gcodes and firmware through the usb serial port for a while now, not the end of the world...

Happy Xmas.

I'm sorry to hear you are having problems with WiFi connectivity. It may be that the ESP12S module on your Duet is faulty.

[lolorc]

@dc42 said in Firmware 2.02RC6 released:

@lolorc said in Firmware 2.02RC6 released:

Hi there,

I'm still not able to upload files to my duet wifi, I'm using latest firmwares, duetwifiserver is still the old 1.21.
Still using cisco access points and linux computers, still loads of tcp dup, tcp retransmission, tcp window full...
and no single issue with a raspberry 10cm away connected to the same ap...

I guess it's not enough just to use a esp8266 and expect it to work in a lot of different environments.

I've been uploading gcodes and firmware through the usb serial port for a while now, not the end of the world...

Happy Xmas.

I'm sorry to hear you are having problems with WiFi connectivity. It may be that the ESP12S module on your Duet is faulty.

it may be, that something I haven't though about. the board connects to the access point fine, I'm able to use the web service, the issues happen when uploading files.
I burnt my first duet board, this is a my second one, it's true I have never encoutered this issue with the first board. but it was 20 months ago...
Have you ever heard of that kind issues that were related to the esp itself ?

Best wishes.

[dc42]

@lolorc said in Firmware 2.02RC6 released:

it may be, that something I haven't though about. the board connects to the access point fine, I'm able to use the web service, the issues happen when uploading files.
I burnt my first duet board, this is a my second one, it's true I have never encoutered this issue with the first board. but it was 20 months ago...
Have you ever heard of that kind issues that were related to the esp itself ?

We know that not all ESP modules work perfectly during testing, but our testing isn't extensive enough to pick up all possible faults. However, another possibility is that your SD card has a very long write time. Have you tried a new SD card?

[dc42]

@frafa, please provide the config.g and homing files you are using, and confirm that the issues you have with the 2.02 firmware release are still as below. That error message should mean that from the current position, it is not possible to move in a straight line to X150 Y150, which is normally because a straight line to that point would pass too close to the proximal joint. You should still be able to use a G0 move to reach that point, assuming that point is reachable.

After print i test this macro file content to debug:

G28
G90 ;Absolute Positioning
G1 X150 Y150 F2500····
Return error on G1: M98 P"0:/macros/test" Error: G1/G2/G3: intermediate position outside machine limits

Second test:

G28
G90 ;Absolute Positioning
G1 X150 Y150 F2500
G1 X0 Y0 F2500
Error: G1/G2/G3: intermediate position outside machine limits 16:24:50 M98 P"0:/macros/test" Error: G1/G2/G3: intermediate position outside machine limits

the arm does the homing, then it makes a mistake, it moves in relative coordinates and not absolute in x150 / y150 (partial ok, not absolu)

but afterwards it is supposed to go to x0 / y0, and it goes to x0 / y300 ???

I think the concern is there is an inverted axis?

[frafa]

Hi David,
yes same problem,

now homing is ok
G28 no longer returns errors

But move absolute return error ...

Test Firmware Version: 2.02RC7(RTOS) (2018-12-22b2):

G28
G90 ;Absolute Positioning
G1 X0 F2500

Return error: 15:40:30 M98 P"0:/macros/test" Error: G1/G2/G3: intermediate position outside machine limits Error: G1/G2/G3: intermediate position outside machine limits

all movements in absolute mode return an error x/y/z...

My config and homing files:
config.g http://dl.free.fr/j7UVd31UF
homeall.g http://dl.free.fr/usibxoSpf (hominig error on "G1 Z10 F250" if i remove no errors)

Reminder everything works perfectly with 1.21RC3

[dc42]

What happens if you make a small G1 S2 move after homing (e.g. at the end of the homeall.g file) to bring the distal arm off the endstop a little? What I suspect is happening is that the end of the first segment of the move you are trying to make ends a little inside the minimum radius. The minimum radius is set slightly higher than the actual minimum radius when the distal arm is on the endstop, to allow for rounding error in the calculation.

Older firmware versions didn't check for intermediate points in a move violating the minimum radius, so for example they would let you attempt to move the nozzle right through the proximal axis, as long as the end point of the move was reachable.

[frafa]

Hi David,

Very strange behavior if I use G1 S2 after homing ...

Example with G1 S2 X1.0 F2000
the arm moves to X: -19.66 Y: 279.36 (while the homing position is X: 30.84 Y: 51.59)

After I send:
G1 X10 F2500

Do not move and forward error:
G1 X10 F2500
Error: G1 / G2 / G3: Intermediate position outside machine limits

The Homing position is inside the bed, (Homing: X: 30.84 Y: 51.59)
the problem would not be there?

[dc42]

It's the distal arm you need to move off the endstop, so in the small G1 S2 movement use Y instead of X. Also, use G91 before it and G90 after it.