MPCNC Rambo to Jackpot 3 Upgrade (setup)

Software / Firmware Jackpot Board / FluidNC
1

All my upgrade parts have finally arrived and have been installed.

I have the Jackpot 3 + FluidTouch installed.

The Jackpot 3 has turned on without releasing the smoke and all steppers bar the z stepper are locked.

However when I try to jog on the FluidTouch the display indicates it did so, but no steppers actually moved.

Additionally when I manually turned the z axis lead screw the Jackpot 3 reset itself

Also when I tried to view the FluidNC SD contents via FluidTouch it has nothing to show but when I switch SD card from the Jackpot3 to the FluidTouch and select the FluidTouch SD card to view all the files are visible. l seem to recall someone else having this same issue.

Troubleshooting help greatly appreciated :blush:

2

Letā€™s start out by seeing the output from the $SS command in the terminal.

Use the preformatted text option in the forum editor window when you paste so it r ds up readable. The icon for that formatting looks like this on the toolbar:

</>

3 
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
$SS
[MSG:INFO: FluidNC v3.9.9 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:config.yaml]
[MSG:INFO: Machine Default (Test Drive no I/O)]
[MSG:INFO: Board None]
[MSG:INFO: Stepping:RMT Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:255ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-1000.000,0.000)]
[MSG:INFO:   Motor0]
[MSG:INFO: Axis Y (-1000.000,0.000)]
[MSG:INFO:   Motor0]
[MSG:INFO: Axis Z (-1000.000,0.000)]
[MSG:INFO:   Motor0]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: AP SSID FluidNC IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
ok
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100>
4

Good grief, Iā€™ve finally been able to make the sd reader workā€¦. I was getting errors such as failed to mount, Error: 60.

I noticed the Flash file area had a default config which was the ā€œTest Drive no I/Oā€ profile??. So I looked at it and the SD setup was totally different from the V1E version loaded onto the SD card. So I just uploaded the MPCNC JP3 config.yaml file to the Flash area and rebooted. Voila SD card is now being read properly.

Jogging and x & y homing did seem to be doing what they should be doing, I donā€™t remember the steppers sounding so smooth in the past (I might be imagining it). However I did encounter an Error: 8 or alarm 8 when I homed the Y axis before I turned it all off (its very late in the evening, and I didnā€™t want to keep going)

2 Likes
5

Youā€™re not imagining it. LOL The Jackpot drivers are a lot smoother. Glad to hear you are making good progress.

6

Looks like you do not have any config files on your board. you have 3.9.9 loaded fine but you need to load all the config file (4 of them) from jackpot firmware config link.

1 Like
7

Excellent. I had incorrectly guessed that if it saw an SD card it would start using that.

So after sending the rest of the files to the Flash area I used $limits to check the limit switches and probe.

x0, y0 x1 & y1 seem to all be in the correct order and axis. However Iā€™m getting a warning about z axis active and it is constantly on when Iā€™m polling to the terminal.

I donā€™t actually have a z limit switch on the machine. I have the Tiny Touch Plate which I have plugged into P (36), nothing is plugged into z (32). Iā€™m guessing I should just jumper 32?

8 
  z:
    steps_per_mm: 200.000
    max_rate_mm_per_min: 900.000
    acceleration_mm_per_sec2: 80.000
    max_travel_mm: 150.000
    soft_limits: false
    homing:
      cycle: 1

The homing cycle for z should be set to 0 for the MPCNC.

@vicious1 donā€™t you think that should be the setting since it doesnā€™t home the z axis?

1 Like
9

The jumper cleared the warning. I also edited the config.yaml with the suggested cycle: change - thanks.

Next on the list is my router control relay. My relay is I presume standard with +/- wires & a signal wire. Iā€™ve plugged the + & - into the module pins for gnd & 5v. and the signal wire into gpio.26 pin marked as ā€˜-ā€™.

I also added the following lines to the config file (copied from Fluidnc wiki).

relay:
  direction_pin: NO_PIN
  output_pin: gpio.26
  enable_pin: NO_PIN
  disable_with_s0: false
  s0_with_disable: true
  spinup_ms: 0
  spindown_ms: 0
  tool_num: 0
  speed_map: 0=0.000% 0=100.000% 1=100.000%
  off_on_alarm: false

However when I use the macro to turn gpio.26 on if fails with

[MSG:ERR: Bad GCode: M62 P0]
error:39
[MSG:ERR: P param max exceeded]
10

I think Iā€™ve figured out I cant use ā€˜relay:ā€™

Here is what I have now (instead of relay:ā€¦.)

spindle:
output_pin: gpio.26
enable_with_s0: false

the macro still does nothing.. but this time no errors are thrown in the terminal.

When I multimeter the +/- of pins of output 26 I get 0v both on and off.

11

I think it is easier just to use analog outputs for pwm, and digital outputs for on off.

The current config has all 4 outputs set as digital and should work out of the box. Supported Gcodes | Wiki.js M62 p0 or p1-4 is on, M63 is off.

12

I donā€™t know if you are responding to me or not, if you are replying to me I do not understand what you are trying to say to help get it going.

from the 192.168.0.1 dashboard I click on 26 on or 26 off and the commands show-up in the terminal window but I do not detect any voltage on the gpio.26 pins.

13

What about the other three outputs?

14

I have it working on 26. I was led up the garden path by google.

ā€œnd the signal wire into gpio.26 pin marked as ā€˜-ā€™.ā€ ā†- should have been +ve

Also

Can you confirm if I was correct or incorrect. I was making changes to the config file in the flash area, scratching my head when they were not making any discernable change in the behaviours I was modifying. I discovered that it was indeed using the config file on the SD card and not the flash areas one.

and

Can you also confirm if Britt was correct;

15

Sorry I assumed that last reply meant your problems were solved.

What is currently not working?

16

Where do I upload config file changes to? The Flash area/the SD card - Is it one or the other or both?
I thought I read in v1e docs that you are supposed to put the files onto the root of the SD card. Which did not work for me until I uploaded the config.yaml to the flash area.

Where am I supposed to be uploading config file changes to? The Flash area/the SD card - Is it one or the other or both?

Was Britt correct? ā€œ@vicious1 donā€™t you think that should be the setting since it doesnā€™t home the z axis?ā€

17

The config.yaml file must be uploaded to the root of flash.

18

It can/should but it also doesnā€™t matter as long as you do not push the ā€œhome allā€ button.

19

If I have learned one thing from software design, itā€™s that if a button that should not be clicked is present at all, users will click it.

If something is made 100% clear from reading the label on the control, users will not read it.

This still applies to otherwise intelligent and educated users.

1 Like
20

Thatā€™s like the first button I clicked on my MPCNC and the core drove up and up and upā€¦ :stuck_out_tongue:

1 Like