RepRapFirmware 2.02RC4 released

[fcwilt]

@alexlin said in RepRapFirmware 2.02RC4 released:

@fcwilt maybe confusing skirt with brim....

That may be the case.

Thanks.

Frederick

[dc42]

@garyd9 said in RepRapFirmware 2.02RC4 released:

"Warning: motor phase A may be disconnected reported by driver(s) 2"

(I thought this was resolved in RC2 or RC3??):

I think it's happening during the very slow Z movements when doing G32 probing, but I can't be sure. I know it happens sometime between issuing G32 and getting the results on the paneldue console page. On this machine, I'm using the manual bed leveling assistant (that tells me how far to turn each of three leveling screws.)

Can you try to pin this down? In RC4 I increased the minimum motor speed below which the open-load status from the drivers is ignored; so that message shouldn't be generated at low speeds.

Also, please use M115 to double check that you are running 2.02RC4.

[Danal]

@fcwilt said in RepRapFirmware 2.02RC4 released:

@alexlin said in RepRapFirmware 2.02RC4 released:

@fcwilt maybe confusing skirt with brim....

That may be the case.

Thanks.

Frederick

Yikes, correct!!! I was confusing skirt with brim...

So, let me change it to:

If you have room for a skirt, sure, that works. There may be circumstances where there is room for a prime line, but not for a standard full skirt.

[garyd9]

@dc42 said in RepRapFirmware 2.02RC4 released:

@garyd9 said in RepRapFirmware 2.02RC4 released:

"Warning: motor phase A may be disconnected reported by driver(s) 2"

(I thought this was resolved in RC2 or RC3??):

I think it's happening during the very slow Z movements when doing G32 probing, but I can't be sure. I know it happens sometime between issuing G32 and getting the results on the paneldue console page. On this machine, I'm using the manual bed leveling assistant (that tells me how far to turn each of three leveling screws.)

Can you try to pin this down? In RC4 I increased the minimum motor speed below which the open-load status from the drivers is ignored; so that message shouldn't be generated at low speeds.

Also, please use M115 to double check that you are running 2.02RC4.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02RC4(RTOS) ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2018-11-18b5

As for pinning it down, I'll try this evening (US Eastern time.) Do you have any suggestions on how I could go about doing that? Just perform manual Z movements via "G1 Zxx F100"?

It's difficult to isolate via G32, as the message doesn't appear until the bed.g is completed, so it might be happening in the very first move that G32 performs, it it might be the very last... there's no way to really tell (that I'm aware of.)

As well, it doesn't happen every time I level the bed, and I believe it's more frequent the first time I level the bed after transitioning from standby power (5VDC via USB) to full power (24VDC via VIN) using the ATX controls.

[dc42]

@garyd9 said in RepRapFirmware 2.02RC4 released:

It's difficult to isolate via G32, as the message doesn't appear until the bed.g is completed, so it might be happening in the very first move that G32 performs, it it might be the very last... there's no way to really tell (that I'm aware of.)

No, if it happens at the end then it's the leadscrew adjustment move that is causing it, or possibly a command at the end of your bed.g file.

• Do you have any movement commands after the last G30 command in bed.g?
• How long does the leadscrew adjustment move take, in the worst case?
• Do you change the motor currents in bed.g? Sprious open-load reports are more likely at low motor currents.

[garyd9]

@dc42 said in RepRapFirmware 2.02RC4 released:

@garyd9 said in RepRapFirmware 2.02RC4 released:

It's difficult to isolate via G32, as the message doesn't appear until the bed.g is completed, so it might be happening in the very first move that G32 performs, it it might be the very last... there's no way to really tell (that I'm aware of.)

No, if it happens at the end then it's the leadscrew adjustment move that is causing it, or possibly a command at the end of your bed.g file.

I think that I might be causing a misunderstanding: I read the "console" messages from the paneldue. When I start the "manual bed leveling assistant" from the paneldue, there is no console output (on the paneldue) until the entire process is completed. At that point, I might get 3-4 messages all appended to each other. For example, I might get a "Warning: motor phase A may be disconnected reported by driver(s) 2" message with a warning appended about an inconsistent probe, and append to that I get the output from the leveling assistant (that tells me which screws to turn and by how much.)

• How long does the leadscrew adjustment move take, in the worst case?

Your phrase "leadscrew adjustment" is confusing me. The only leadscrew in my printer is my Z axis (bed moves in Z.) I don't adjust that. I use three (manual) adjustment screws and manually adjust them as suggested by the duet after running the manual leveling assistant.

If you're referring to the Z-axis movement when probing, then it's perhaps 5 seconds worst case.

• Do you have any movement commands after the last G30 command in bed.g?
• Do you change the motor currents in bed.g? Sprious open-load reports are more likely at low motor currents.

I've posted the entire bed.g file above. The only thing after the last G30 is a M402 and no current adjustments (or things that would impact current.)

However, my Z axis stepper motor (with the leadscrew) is a low power stepper and configured for 300 milliamps. (from config.g: M906 X810 Y810 Z300 E810:810 I30)

[3dmntbighker]

@dc42 said in RepRapFirmware 2.02RC4 released:

@garyd9 said in RepRapFirmware 2.02RC4 released:

"Warning: motor phase A may be disconnected reported by driver(s) 2"

(I thought this was resolved in RC2 or RC3??):

I think it's happening during the very slow Z movements when doing G32 probing, but I can't be sure. I know it happens sometime between issuing G32 and getting the results on the paneldue console page. On this machine, I'm using the manual bed leveling assistant (that tells me how far to turn each of three leveling screws.)

I saw this message once with RC3. I wasn't sure what it meant, but the print had completed.

[garyd9]

@dc42 - an example of what I meant by:

@garyd9 said in RepRapFirmware 2.02RC4 released:

It's difficult to isolate via G32, as the message doesn't appear until the bed.g is completed, so it might be happening in the very first move that G32 performs, it it might be the very last... there's no way to really tell (that I'm aware of.)

As you can see by the message at 0m05, multiple messages are combined into a single entry, so I'm not sure where in the bed leveling assistant that the warning occurs.

[dc42]

What is your Z steps/mm and VIV voltage? It's just occurred to me that if the driver can't maintain the requested current due to the motor inductance being high, motor speed being high, and supply voltage being low, that too would give rise to an open load report.

[fcwilt]

Hi,

I would first fix the heater issues and the power supply issue.

Then see how things go.

Frederick

[garyd9]

@dc42 said in RepRapFirmware 2.02RC4 released:

What is your Z steps/mm and VIV voltage? It's just occurred to me that if the driver can't maintain the requested current due to the motor inductance being high, motor speed being high, and supply voltage being low, that too would give rise to an open load report.

M350 Z16 I1
M92 Z401.0

VIN is 24VDC.

Again, I want to point out that this doesn't seem to cause any harm, and it only seems to happen once in a while: usually the first time I run the leveling assistant after turning on the 24V PSU (via M80.) I can (and often do) run the manual bed leveling assistant 3 or 4 times before printing and it will only happen the first time.

If I run the assistant again before the PSU is powered down, I usually won't see the warning. However, if the PSU powers down (via M81 S1), it will usually happen again once I power it back on, heat up the build plate, and run the assistant again.

[dc42]

After turning on the power with M80, do you have any sort of delay before you run the bed probing command? You mentioned waiting for the heaters - do you always do that?

[garyd9]

@dc42 said in RepRapFirmware 2.02RC4 released:

After turning on the power with M80, do you have any sort of delay before you run the bed probing command? You mentioned waiting for the heaters - do you always do that?

Yes. My procedure is to run a macro (from paneldue) that turns on the 24V PSU via a SSR (and also turns on LEDs attached to one of the always-on fan headers.) I then prep my build surface and begin heating the bed. I don't start the manual leveling assistant after until the build area has reached 65C (PLA) or 90C (PETG/ABS/ePC) and settled.

I also often heat the nozzle I'll be using to a standby temperature while heating the build plate (130C or 160C depending on material.)

All of this is initiated on the PanelDue. For this machine, I rarely use DWC for anything besides remote monitoring.

[dc42]

Thanks. Does the problem only ever happen when it is the first time you have run the motor after VIN power has been restored?

[garyd9]

@dc42 said in RepRapFirmware 2.02RC4 released:

Thanks. Does the problem only ever happen when it is the first time you have run the motor after VIN power has been restored?

I think so. I started paying much closer attention to the warning yesterday after my post (but I've only started 2 prints since then.) I'll certainly keep you informed if it happens other than the first time running the stepper after VIN is restored.

[garyd9]

@garyd9 said in RepRapFirmware 2.02RC4 released:

@dc42 said in RepRapFirmware 2.02RC4 released:

Thanks. Does the problem only ever happen when it is the first time you have run the motor after VIN power has been restored?

I think so. I started paying much closer attention to the warning yesterday after my post (but I've only started 2 prints since then.) I'll certainly keep you informed if it happens other than the first time running the stepper after VIN is restored.

As luck would have it, this evening I had it happen when starting a new print with the printer NOT going into "ATX Off" first. Print ended, I hit the M80 macro (to counter a pending M81 S1), prepped a new plate, heated it up, and got the warning when leveling the build plate.