Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MKS RUMBA32 FAN M106 open it, incorrect voltage output #17519

Closed
vivary opened this issue Apr 13, 2020 · 11 comments
Closed

MKS RUMBA32 FAN M106 open it, incorrect voltage output #17519

vivary opened this issue Apr 13, 2020 · 11 comments

Comments

@vivary
Copy link

vivary commented Apr 13, 2020

Bug Description

  1. Use the old version of marlin2.0, the voltage output to RUMBA32, FAN is normal;
  2. Use Marlin2.05 firmware, compile and download it to the RUMBA32 motherboard through platformio, use the command M106 P0 S255 to control to open FAN, but the output voltage of the FAN interface is only 2.2V, the normal voltage should be to the power supply voltage
    image
    image

My Configurations

Marlin-RUMBA32.zip
This is my config.

Steps to Reproduce

  1. Upload marlin2.0.5 to RUMBA32
  2. Use pronterface send command to RUMBA32 board by USB
  3. Measure FAN output voltage

Additional Information

  • Provide pictures or links to videos that clearly demonstrate the issue.
  • See How Can I Contribute for additional guidelines.
@ellensp
Copy link
Contributor

ellensp commented Apr 13, 2020

The mosfets are on the low side of the cct. Ie the +v is directly connected to the 12v power supply. (12v is generated from vin on your board)
The gnd is switched.
To measure the voltage you have to use the GND pin of the fan plug as your meter gnd.
See https://github.com/Aus3D/RUMBA32/blob/master/Schematic.pdf

@vivary
Copy link
Author

vivary commented Apr 13, 2020

RUMBA32 motherboard, sending M106 P0 S255, the voltage output is abnormal, which may be caused by the HAL library timer or other causes.

@ellensp
Copy link
Contributor

ellensp commented Apr 13, 2020

Is your 12v there?
What is the voltage at the mosfet gate compared with real gnd.
Can you put a scope on the gate see if its is PWMing or constant high.

@makerbase-mks
Copy link
Contributor

image
This setting can solve the problem.

@sjasonsmith
Copy link
Contributor

It works if you comment the following three lines out of the variant file:

// PWM resolution
//#define PWM_RESOLUTION          8
//#define PWM_FREQUENCY           20000 // >= 20 Khz => inaudible noise for fans
//#define PWM_MAX_DUTY_CYCLE      255

This causes it to run fine, but with only a 1 kHz PWM frequency. I believe this is how the SKR Pro runs right now also, and has been the subject of some complaints.

There have been some changes involving PWM in more recent frameworks. The 20 kHz PWM seems to work fine in stm32duino 1.8, but some other issues are preventing that upgrade right now.

Ironically, with the fan I am using 1 kHz PWM works great, but the intended 20 kHz PWM is unusable, even though it looks perfect on the scope. I would have to use FAN_SOFT_PWM or perhaps add capacitors for the higher frequency PWM to be useful at all.

On another note, there is a timer conflict on this board between the TONE timer and the STEP timer. That will cause problems if anyone enabled SPEAKER.

@boelle
Copy link
Contributor

boelle commented Jun 21, 2020

Lack of Activity
This issue is being closed due to lack of activity. If you have solved the
issue, please let us know how you solved it. If you haven't, please tell us
what else you've tried in the meantime, and possibly this issue will be
reopened.

@boelle boelle closed this as completed Jun 21, 2020
@sjasonsmith
Copy link
Contributor

I had reproduced this one, so I’m going to open it back up and call it confirmed.

@sjasonsmith
Copy link
Contributor

I believe the fan PWM will be fixed with my open PR that upgrades the STM32 framework, although the conflict when you enable SPEAKER will probably require some timer reassignments.
#18496

I intend to test it against that PR, but have not gotten around to it. If somebody beats me to it, please post your testing results on that PR.

@github-actions
Copy link

github-actions bot commented Aug 4, 2020

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

@github-actions
Copy link

github-actions bot commented Sep 3, 2020

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

@github-actions
Copy link

github-actions bot commented Nov 7, 2020

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants