|
|
Post by fracturedtom on Jun 24, 2022 19:58:42 GMT
I cannot connect my PC to my M3. I noticed the LED on the UNO board was not on. I removed the CNC shield, reconnected the UNO board and the LED is back on. Plugged the CNC shield back in and LED goes off.
Any ideas?
Also, if I need a new board, can someone please attach an Amazon link to the correct item?
|
|
|
|
Post by S. Ronin McGowan on Jul 19, 2022 7:08:11 GMT
Hey Tom! without a lot of testing it's definitely simple enough to assume you've got a dead board. Keep in mind your drivers may not be dead, and you could possible use them as spares in the future (the ICs that are in the removable spots, 4 of them in the center section of the board). That said, you're on an M3 like me, so your board is a Protoneer CNC Shield, v3. That'll help you search. Here's some links: www.amazon.com/s?k=protoneer+cnc+shieldbit.ly/protoneer-cnc-aliexpress |
|
|
|
Post by fracturedtom on Jul 20, 2022 22:19:34 GMT
Hey Tom! without a lot of testing it's definitely simple enough to assume you've got a dead board. Keep in mind your drivers may not be dead, and you could possible use them as spares in the future (the ICs that are in the removable spots, 4 of them in the center section of the board). That said, you're on an M3 like me, so your board is a Protoneer CNC Shield, v3. That'll help you search. Here's some links: www.amazon.com/s?k=protoneer+cnc+shieldbit.ly/protoneer-cnc-aliexpressHey, thanks for chiming in!
After plugging them in, the LED on the counterfeit UNO board stays on now. But, it's still not seen by the PC. I have read and performed many tuts on this issue common to Win 10 without success.
It does not show under Device Manager. The arduino app tells me "no port detected" or something like that. It could be the driver. I do not know what driver the M3 was using. I have a laser using the CH340. Is there a different one?
|
|
|
|
Post by S. Ronin McGowan on Jul 21, 2022 17:09:29 GMT
Definitely check into the driver. Whenever possible, find UNOs with an IC, not the SMD, and always reload the device driver. Also, you're going to want to adjust your DRV8825 modules per the M3 installation doc, lest you burn something up
|
|
|
|
Post by fracturedtom on Jul 23, 2022 22:13:43 GMT
Definitely check into the driver. Whenever possible, find UNOs with an IC, not the SMD, and always reload the device driver. Also, you're going to want to adjust your DRV8825 modules per the M3 installation doc, lest you burn something up
I could not really find any info on the driver. However, I think the UNO board is busted. I ordered a new one by ELEGOO instead of same unbranded shite that came with the M3. Apparently, it's a very good Arduino clone. I also ordered a new shield just in case. We'll see.
|
|
|
|
Post by S. Ronin McGowan on Jul 24, 2022 4:16:00 GMT
I replaced my M3's Uno with an ELEGOO one a while back, definitely good boards. I reloaded my driver (the software one) when I replaced the Uno. Having a spare Protoneer CNC shield around never hurts, I've got a spare around here as well.
Good luck mate!
|
|
|
|
Post by fracturedtom on Jul 29, 2022 19:40:26 GMT
I replaced my M3's Uno with an ELEGOO one a while back, definitely good boards. I reloaded my driver (the software one) when I replaced the Uno. Having a spare Protoneer CNC shield around never hurts, I've got a spare around here as well. Good luck mate!
OK. I have the EEGOO board connected and it's talking to my PC. That's good. The original board was bad.
When testing:
X axis works fine Z axis raises and immediately drops. Y axis makes noise but does not move
Thoughts?
|
|
|
|
Post by S. Ronin McGowan on Jul 29, 2022 22:09:30 GMT
First things: 1. You need to set the idle timeout to 255 (GRBL settings, diymachining.com/grbl-settings-101-a-how-to-guide/). The Z is dropping because when going idle (or set to 0, ie immediately idle) the stepper motors are not energized and therefore won't hold the Z axis "up". 2. The Y axis issue is likely because your voltage/current limit is not set properly. Refer to M3 documentation on how to use a multimeter to set that, it's on the driver, a small pot with a phillips head. |
|
|
|
Post by fracturedtom on Jul 30, 2022 13:59:11 GMT
First things: 1. You need to set the idle timeout to 254 (GRBL settings, diymachining.com/grbl-settings-101-a-how-to-guide/). The Z is dropping because when going idle (or set to 0, ie immediately idle) the stepper motors are not energized and therefore won't hold the Z axis "up". 2. The Y axis issue is likely because your voltage/current limit is not set properly. Refer to M3 documentation on how to use a multimeter to set that, it's on the driver, a small pot with a phillips head.
Sounds like a plan. I did the voltage/current setting already. I can re-read the boards or maybe one of them is crap-ola.  |
|
|
|
Post by fracturedtom on Jul 30, 2022 22:37:20 GMT
I swear, this is some BS!
Okay, after readjusting the small boards to 6.0v, they were already at 6.0v, BTW. X and Y were working, Z still falls. I edited the grbl code as requested. It will raise and set, but you can't move it too high or it just drop as if hit the limit switch. It doesn't hit the switch though. It's probably an inch away from the switch.
|
|
|
|
Post by fracturedtom on Aug 6, 2022 14:27:21 GMT
After watching the Z fail over and over, I decided to remove the router. To my surprise, the Z works now. Deciding that the router was too heavy, I put a spindle on. Z still drops before reaching limit switch. I have to assume that it's the belt-driven system that is failing, but I cannot find the problem. All screws and nuts seem to be tight as does the belt. Now I get why several uses at OpenBuilds had a good laugh when I mentioned my belt-driven Z.
|
|
|
|
Post by bLouChip on Aug 8, 2022 12:31:18 GMT
It's worth a double check; command $$ will display the config values.
|
|
|
|
Post by fracturedtom on Aug 8, 2022 22:06:15 GMT
It's worth a double check; command $$ will display the config values.
Thanks, but I have done that. The stepper motors hold, for a bit, then once it reaches a certain height it drops to the table.
|
|
|
|
Post by S. Ronin McGowan on Aug 8, 2022 23:01:27 GMT
It's worth a double check; command $$ will display the config values.
You're right about the 255, that was my bad. I was thinking subnets for some reason. Good catch, I'll edit my post |
|
|
|
Post by S. Ronin McGowan on Aug 8, 2022 23:04:58 GMT
Tom, please go ahead and post the output of the command $$
|
|
