No movement #1192
Comments
|
Mitch just wrote a new wiki page with a flow chart to help with that. Give it a try. |
That means that FluidNC cannot find your config file. If you uploaded it to a name other than "config.yaml", you must tell FluidNC the name by sending "$config/filename=YOUR_CONFIG_NAME.yaml" in FluidTerm, or else set it via WebUI |
FluidNC does not directly support 4 motors on one axis. The most is 2 motors per axis. It might be possible to connect 2 motors to one driver and 2 motors to another driver. |
|
Good evening Mitch, |
|
Good evening, board: 6 Pack |
The usual cause of "slow, different directions, and noisy" is a bad connection between the stepper driver and the stepper motor. A stepper motor has two coils. Motion happens when coils A and B are energized in sequence - A B A B A B etc. - with a particular timing pattern (phase) and polarity. If there is a broken connection to one of the coils, the motor sees the pattern A _ A _ A _ instead. Instead of moving smoothly, the motor will sometimes move slowly with jerking, sometimes move in one direction for awhile then switch directions, and sometimes just sit there shaking. The other things that can cause this behavior, in addition to a broken wire or bad connection, are
Those causes are listed in the order of most common to least common. Connections fail more frequently than motors. When a stepper driver fails, it usually fails so catastrophically that there is no motion at all, not just one coil driver. |
|
I measured the motor 2.5 ohms on both channels so that should be ok. Even put the two wires together and the motor was hard to move. Changed to a different driver, problem is the same. 6Pack is in SPI mode, card on 5 V, TMC2130 on 1.5 volts. When I send a movement command I measure about 21 volts. Still the motor makes a loud noise and goes back and forward. Do you have any other idea? |
|
What do you have the Vcc set for? |
|
On 5v |
|
And I just read it should be 3.3v. Now I have no movement at all and not change in voltage on the motor. |
|
You could try a different motor, or swapping that motor to a different stepper. |
|
It should be 3.3v. The TMC2130 can run at either voltage, but SPI returns data to the ESP32 so it must be 3.3v or it can break the ESP32. It usually does not hurt in the short term, but definately leave it at 3.3v. Can you show us your startup messages? |
|
Do you mean the yaml file or something else? board: 6 Pack |
I did all of that already, no change. |
|
Maybe you are trying to move faster than the motors can go. I don't see any details above about what commands you are using to perform the motion, nor any information about your mechanical system. |
|
I am only sending commands through the web interface, using CNCj for example doesn't work either. I connected 1 X motor on X to the 6PACK and that's it. |
|
Here is how to check your startup messages. http://wiki.fluidnc.com/en/support/troubleshooting_config_files#check-the-startup-messages |
|
Ah you mean is this. Ok that is a new chapter then for me and I will attend to that tomorrow. Thank you for you help today. Time for me to go to bed. [MSG:INFO: uart_channel0 created] |
If I were to tell you that I spoke to someone over the telephone, you would not know what I said. Similarly, knowing that you sent commands through the Web interface and CNCjs doesn't help me know what the commands were. |
|
Good evening, Still no movement by the way after I have changed to 3.3 volts. I reset, the motor will lock for a few seconds. |
|
Try sending $MD and $ME commands. Check the lock state after each command. |
|
No it does not lock, but does for a few second after reboot. If I make a bridge between 1A and 1B the resistance is higher but not a lock. |
|
The each coil mounts to adjacent terminals.
|
|
Ok, so I reconnected it to the picture above. It all stays the same, locks when I reboot for a few seconds and then you can move the stepper again. Do you have any other ideas? |
|
$ME does not lock the motors? |
|
No |
|
I am running out of ideas. Try changing |
|
Changed, no result. $ME has no effect. It still makes me think why the motor unlocks after reboot. Could that be a thing? |
|
That is strange, but I have tried to test everything I can think of regarding that. Send $axes/x and paste the results. |
steps_per_mm: 800.000000
max_rate_mm_per_min: 5000.000000
acceleration_mm_per_sec2: 100.000000
max_travel_mm: 300.000000
soft_limits: false
homing:
cycle: 2
allow_single_axis: true
positive_direction: false
mpos_mm: 150.000000
feed_mm_per_min: 100.000000
seek_mm_per_min: 200.000000
settle_ms: 500
seek_scaler: 1.100000
feed_scaler: 1.100000
motor0:
limit_neg_pin: gpio.33
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000000
tmc_2130:
step_pin: I2SO.2
direction_pin: I2SO.1
disable_pin: I2SO.0
r_sense_ohms: 0.110000
run_amps: 0.750000
hold_amps: 0.250000
microsteps: 32
toff_disable: 0
toff_stealthchop: 5
use_enable: false
cs_pin: I2SO.3
spi_index: -1
run_mode: StealthChop
homing_mode: StealthChop
stallguard: 0
stallguard_debug: false
toff_coolstep: 3 |
|
You could try adding I doubt it will work, but it is the only thing I can think of. |
|
I think I found it, I let you know tomorrow if I am right. Hardware issue, but not the card. |
|
Sometimes if it locks for a few seconds, then unlocks, it is because the driver overheated and shut down to protect itself. I have also seen cases where the power supply shut down or glitched, causing the driver to shut down. |
Wiki Search Terms
Good evening,
I uploaded everything I need onto the ESP and its working all fine. Uploaded the 6_pack_2130_XYZABC.yaml and that is also now loaded. Still when trying to get 1 motor moving it does not happen.
Controller Board
6-pack
Machine Description
I need to have 4 Y motors at the same time, 1 X and 1 Z motor to move.
Input Circuits
No response
Configuration file
Startup Messages
User Interface Software
WebUI
What happened?
I try to understand how things are working with the pins and the 2130 SPI I have placed on the board. I did not change anything from that standard yaml file.
GCode File
No response
Other Information
No response
The text was updated successfully, but these errors were encountered: