M906 reports E:0 on update to 1.19.2

CRPerryJr

Try deleting and re-typing the M906 line in config.g in case there is a hidden character in it.

I tried this several times with no change to the issue.

Are there any M906 or M584 commands in your homing files or in bed.g

No other M906 commands found in any config file.

When using 1.19.2, if you send M906 X1000 Y1000 Z1000 E1000 from the command console, are the motor currents OK after that?

This did set the proper current settings for the extruders and a M906 reported X:1000 Y:1000 Z:1000 E:1000:1000:1000:1000:1000:1000

2. Does it make any difference if you put the I60 parameter on the first M906 line instead of on a separate M906 line?

This made the difference. Once I placed the I60 command on the same line as the first M906 line, the E parameter was read and configured correctly.

So now I am working great on Firmware version 1.19.2 and my new config.g M906 line looks like this:
[c]M906 X1000 Y1000 Z1000 E1000 I60[/c]

Thank you for your help!

dc42

I've just spotted the problem in the config.g file you posted:

[[language]]
M906 X1000 Y1000 Z1000 E1000            ; Set motor currents (mA) 
M906 I60                                : Set motor Idle current

The comment on the second line needs to be introduced by a semicolon, not a colon. It worked with older versions of RRF because they only accepted uppercase letter in GCode commands. Version 1.19 accepts lowercase characters too, so the 'e' in 'Set' was being taken for an extruder current setting command.

madhunm

I seem to be having the same issue with firmware version 2.01

It starts off with 0mA current; when I type in M906 E(any current over 1000ma), it starts to work fine.

Here is my excerpt from config.g:

M906 X2000 Y1500 Z1500 U1500 E1500:1500 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

Thanks,
Madhu.

dc42

@madhunm, please post your whole config.g file.

madhunm

@dc42 said in M906 reports E:0 on update to 1.19.2:

@madhunm, please post your whole config.g file.

here it is:

0_1537895572014_config (2).g

Phaedrux

@madhunm Try retyping the line from scratch in the config.

madhunm

@phaedrux said in M906 reports E:0 on update to 1.19.2:

@madhunm Try retyping the line from scratch in the config.

Done; no use.

After rebooting, M906 in the console results in:

M906
Motor current (mA) - X:2000, Y:1500, Z:1500, U:1500, E:0, idle factor 30%

dc42

What happens if you use E1500 in config.g instead of E1500:1500 ?

What happens if you enter that M906 command in the GCode Console, exactly as you have it in config.g?

madhunm

@dc42 said in M906 reports E:0 on update to 1.19.2:

What happens if you use E1500 in config.g instead of E1500:1500 ?

When i use E1500, it works as expected; M906 reports:
Motor current (mA) - X:2000, Y:1500, Z:1500, U:1500, E:1500, idle factor 30%

When I type E1500:1500 in the gcode console, i get:
Error: GCodes: Attempt to read a GCode float array that is too long: M906 E1500:1500

Thanks,
Madhu.

Phaedrux

@crperryjr said in M906 reports E:0 on update to 1.19.2:

M92 E146.27:146.27:146.27 ; Set steps/mm for extruders

I just noticed that your M92 for the E steppers steps per mm comes much later than for the other axis and after your other commands specify settings for a single E motor.

Try moving your e steps per mm M92 back up with your other axis.

dc42

@madhunm said in M906 reports E:0 on update to 1.19.2:

@dc42 said in M906 reports E:0 on update to 1.19.2:

What happens if you use E1500 in config.g instead of E1500:1500 ?

When i use E1500, it works as expected; M906 reports:
Motor current (mA) - X:2000, Y:1500, Z:1500, U:1500, E:1500, idle factor 30%

When I type E1500:1500 in the gcode console, i get:
Error: GCodes: Attempt to read a GCode float array that is too long: M906 E1500:1500

Thanks,
Madhu.

That's as expected. Your config.g file contains this line:

M584 X0 Y1 Z2:3 U3 E4 P4

So you have only one extruder drive (E4 in the M584 command), not two.

madhunm

@dc42 said in M906 reports E:0 on update to 1.19.2:

That's as expected.

Thanks a ton for your support!