Hey folks! I’m doing an LR4 build in the UK so sourced the Jackpot controller from Elecrow along with the custom ESP32 and stepper drivers.
I’ve assembled the board and I’m getting ready to power it on for testing, but I’m not sure what the next steps are in terms of firmware / config?
Had a search around and a lot of what I’m seeing assumes the board was purchased from V1E |(which I would have loved to), so I’m a little lost. Is it as simple as flashing FluidNC?
You would make sure the Jackpot is not getting power from an AC to DC power supply, and use a USB cable to connect it to a computer. If the computer does not seem to have a port connecting to it, you may need to install drivers for that. I think a driver link can be found in the docs.
If you have trouble getting the ESP32 to go into developer mode, hold down the “boot” button on the top of the ESP32, for a little while and release as you are trying to connect.
After you get the firmware installed, you should be able to disconnect the USB cable from the computer, boot up the Jackpot with the DC power supply, and connect to the Jackpot via WiFi in AP (Access Point) mode. Using the WebUI, you should be able to upload the config.YAML file made by Ryan for your given machine, as downloaded from V1E in the docs.
I hope this helps, and if you have issues or questions, post back with pics and details.
Thanks both, this all worked well! As always, now I’ve asked the question and followed your instructions, I found them all very neatly and clearly written up in the Jackpot docs
/electronics/jackpot/#updating-installing-firmware
If I had a time machine I’d go and tell myself off.
Hi, I would like to hook in into this thread. Today my Jackpot-Board and the ESP32 from elecrow dot com arrived. I want to use the webinstaller of fluidnc but I have no WIFI-Button on the left side!? I tried to install fluidnc … it seams to work but after install the terminal throws errors over errors. So I decided to follow the guide ( github dot com / Longus / FluidNC / wiki / Set-Up-FluidNC-Using-macOS ) along and up to point 2 of the Install FluidNC firmware all works as described. After that I see the same errors in terminal.
My Setup:
Controller → elecrow / jackpot-cnc-controller
ESP → elecrow /custom-v1-engineering-esp32-devkitc
MacOS → Sequoia 15.2 ( M1 chip )
I already have installed the additional drivers and tried again. Also tried with ESP32 on the board and without board.
Can anyone help, please!?
Here is what I have typed in the Terminal:
PS: As you can see I have two serial ports … before the installation of the drivers there was only one … of course I have tried both … first one → don’t work then second one → don’t work
TERMINAL OUTPUT
Last login: Fri Jan 31 13:51:02 on ttys000
username@iMac-von-Steffe ~ % cd /Users/username/Desktop/fluidnc-v3.9.4-posix
username@iMac-von-Steffe fluidnc-v3.9.4-posix % /Users/username/Desktop/fluidnc-v3.9.4-posix/install-wifi.sh
esptool.py --chip esp32 --baud 230400 dump_mem 0x3ff5a018 4 SecurityFuses.bin
esptool.py v3.1
Found 5 serial ports
Serial port /dev/cu.wlan-debug
Connecting........_____....._____....._____....._____....._____....._____....._____
/dev/cu.wlan-debug failed to connect: Failed to connect to ESP32: Timed out waiting for packet header
Serial port /dev/cu.usbserial-140
Connecting.......
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: f0:24:f9:59:20:48
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 230400
Changed.
Read 4 bytes
Done!
Hard resetting via RTS pin...
esptool.py --chip esp32 --baud 230400 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 wifi/bootloader.bin 0xe000 common/boot_app0.bin 0x10000 wifi/firmware.bin 0x8000 wifi/partitions.bin
esptool.py v3.1
Found 5 serial ports
Serial port /dev/cu.wlan-debug
Connecting........_____....._____....._____....._____....._____....._____....._____
/dev/cu.wlan-debug failed to connect: Failed to connect to ESP32: Timed out waiting for packet header
Serial port /dev/cu.usbserial-140
Connecting........_____....._____....._
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: f0:24:f9:59:20:48
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 230400
Changed.
Configuring flash size...
Auto-detected Flash size: 8MB
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x001d2fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Warning: some reserved header fields have non-zero values. This image may be from a newer esptool.py?
Flash params set to 0x023f
Compressed 17568 bytes to 12205...
Wrote 17568 bytes (12205 compressed) at 0x00001000 in 0.7 seconds (effective 199.5 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 970.1 kbit/s)...
Hash of data verified.
Compressed 1844816 bytes to 1100003...
Wrote 1844816 bytes (1100003 compressed) at 0x00010000 in 49.1 seconds (effective 300.7 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 129...
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.0 seconds (effective 583.7 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
Starting fluidterm
--- Available ports:
--- 1: /dev/cu.Bluetooth-Incoming-Port 'n/a'
--- 2: /dev/cu.SLAB_USBtoUART 'CP2102N USB to UART Bridge Controller'
--- 3: /dev/cu.debug-console 'n/a'
--- 4: /dev/cu.usbserial-140 'CP2102N USB to UART Bridge Controller'
--- 5: /dev/cu.wlan-debug 'n/a'
--- Enter port index or full name: 4
--- FluidTerm v1.2.0 on /dev/cu.usbserial-140 115200,8,N,1 ---
--- Quit: Ctrl+] or Ctrl+Q | Upload: Ctrl+U | Reset: Ctrl+R | ClearScreen: Ctrl+W ---
.....
`x昘fff~f~fff~ffff`x昘ff``fx`ff怘~f~xf~f~~~f~xffx`f怘f~f~xxxx~`怘怘~fffffff`ff`~fxfff`ff`f`fxf~f~fff~fxfffx~fx~`fx~fx~`fx~~fx~`fx`xx~xxxxxxf怘xfxxfxxf`f昆怘[MSG:INFO: uart_channel0 created]
[MSG:RST]
[MSG:INFO: FluidNC v3.9.4 github dot 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: STA SSID is not set]
Brownout detector was triggered
After I use the Webinstaller → Install FluidNC → 3.9.4 Processor type esp32 Wroom → wifi → fresh-install I get the info, that the controller now is ready to work. When I click continue the site loads and tells me:
The controller does not seem to have FluidNC installed, do you wish to install it?
Hi, thanks for writing … after choosing port 2 I’m not able to write / type something.
What I get is very half second those lines … and again … and again …
— Available ports:
— 1: /dev/cu.Bluetooth-Incoming-Port ‘n/a’
— 2: /dev/cu.SLAB_USBtoUART ‘CP2102N USB to UART Bridge Controller’
— 3: /dev/cu.debug-console ‘n/a’
— 4: /dev/cu.usbserial-140 ‘CP2102N USB to UART Bridge Controller’
— 5: /dev/cu.wlan-debug ‘n/a’
— Enter port index or full name: 2
— FluidTerm v1.2.0 on /dev/cu.SLAB_USBtoUART 115200,8,N,1 —
— Quit: Ctrl+] or Ctrl+Q | Upload: Ctrl+U | Reset: Ctrl+R | ClearScreen: Ctrl+W —
After type in 2 and press enter this comes …
…
[MSG:INFO: uart_channel0 created]
[MSG:RST]
[MSG:INFO: FluidNC v3.9.4 LINK DELETED]
[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]
When that brownout is triggered, it’s resetting the ESP32, so it’s stuck in a loop.
This “brownout” error basically means that when it goes to connect to wifi, it doesn’t have enough power. The ESP32 gets 5v from USB and converts it to 3.3v.
Do you have this plugged into a USB hub or directly? Can you try a different USB port? Can you try a different cable?
Disconnect the ESP from your USB cable and plug it into the Jackpot. Then connect the Jackpot to your power supply and turn it on. Look in your computer wifi settings for Fluidnc and connect to it. You should be able to log in directly to the WiFi SSID “FluidNC” and the password = 12345678
Open your browser and connect to http://192.168.0.1/
With the Jackpot connected to your power supply and powered up plug in the USB cable and run Fluidterm again. Copy the output for $SS and paste it here.
I‘m rubbing my eyes … just connected the ESP to the jackpot - then inserted 24v dc from power supply … power on … checking wifi networks and TADAAAA - there it is …
Thank you so much for this hint. Never mind that the power from usb is not high enough. Fantastic! I will send pictures and Videos when i‘m done! Great! Have a nice day - we see - ahhh read us! Kind regards, Steffe
Thanks a Lot - to all the people here - everyone is doing an awesome job. Everyones here for everyone - in forums in germany everyone is keeping knowledge private and talking so all others are stupid. Here it’s marvellous! Thanks - i will be posting pictures soon … and if i have any questions i will write - in mind that here are awesome people
If you mean the German woodworker forum: there are some idiots, but also a few cool people. Around here it is all glitter and unicorn farts and everyone is always friendly. It‘s the absolutely nicest forum there is.
