We are going to have a 5-10 JP3's that will not connect

Updates and News
1

I flashed a some boards for a day with FS first then WIFI, turns out that does not work. I was so busy checking for driver issues I did not check the wifi. Grrrrr. Testing is not easy.

So if you see anyone pop up with " I can not connect to my new JP3" they have to reflash (or they could just flash the wifi raw stuff).

FluidNC Installation | Wiki.js - The fluidNC wiki has this section a little confusing. You do have to flash the wifi package first, if you flash it after the FS package the board works fine but the wifi does not.

2 Likes
2

I edit the install package from fluidnc’s github.

@echo off

call checksecurity.bat
if not %ErrorLevel% equ 0 (
   exit /b 1
)

set BuildType=wifi
set EsptoolPath=win64\esptool.exe

set BaseArgs=--chip esp32 --baud 921600
set SetupArgs=--before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect

echo %EsptoolPath% %BaseArgs% erase_flash
%EsptoolPath% %BaseArgs% erase_flash

set LocalFS=0x3d0000 wifi\littlefs.bin
set Bootloader=0x1000 %BuildType%\bootloader.bin
set Bootapp=0xe000 common\boot_app0.bin
set Firmware=0x10000 %BuildType%\firmware.bin
set Partitions=0x8000 %BuildType%\partitions.bin

echo %EsptoolPath% %BaseArgs% %SetupArgs% %LocalFS% %Bootloader% %Bootapp% %Firmware% %Partitions%
%EsptoolPath% %BaseArgs% %SetupArgs% %LocalFS% %Bootloader% %Bootapp% %Firmware% %Partitions%

echo Starting fluidterm
win64\fluidterm.exe

If I do that wifi / localfs llast the wifi does not work, and shows no errors.

3

P.S. If any of you know how I can also add our configs at this step I would love to know. Maybe this is a question for Claude?

4

You should be able to do it via FluidTerm which it is already calling.

Uploading via command line options.

You can use FluidTerm to upload files as part of a script.

fluidterm -p COM3 -u files\myprog.gc -r /sd/program1.gc

Parameters

  • -p This allows you to specify the COM port. If this parameter is not used, it will automatically select the COM port if only ose exist. If more than one exist, you will have to select if from a list.
  • -u This indicates you want to upload a file.
  • -r This is used to specify the filename on the remote device (the controller). If the filename is omitted, the uploaded file will be placed in localfs with a name the same as the tail name of the source file, for example /localfs/myprog.gc per above.
1 Like
5

Thank you!!!

Dang their docs are good, or at least everything is already in there.

6

You could even go a step further and build your own littlefs.bin for each board (I guess that’s just JP3 now) since that’s what contains the files. So you could do it all at one shot.

If you open the FluidNC repo in VS Code, the contents of /FluidNC/FluidNC/data is what ends up in that. So, just put all of your flash files there.

image
image301Ă—353 5.81 KB

That path is defined by the data_dir in the platformio.ini file:

[platformio]
src_dir = FluidNC/src
include_dir = FluidNC/include
test_dir = FluidNC/tests
data_dir = FluidNC/data

Under PlatformIO → Platform, you can select Build Filesystem Image to build littlefs.bin

image
image348Ă—451 12.4 KB

Which will show this:

Building in release mode
Building FS image from 'FluidNC\data' directory to .pio\build\wifi\littlefs.bin
/config.yaml
/favicon.ico
/index.html.gz

Unless they change the filesystem, and I haven’t seen them do it, this file should stay the same between releases.

2 Likes
7

That’s a great idea! Any step you can remove would make Ryan’s job (or anyone redoing that work) a lot easier.

2 Likes
8

Someone mentioned this a while back with the jp1, I could not get it to work then. I need to try again.

As much as I want to use the webinstaller to go through the exact steps a user would, doing that for each board was a bummer that took forever.

Doing it this way reduces another huge step! Lemme give it a shot.

This would also be excellent for those stubborn boards people have issues with. A zip file with a one click wipe and flash.

1 Like
9

OH It works!!!1 Thank you.

So If I leave my script up above alone and just swap out the littlefs.bin file it will have it all…that is too cool. I will be flashing some boards first thing in the morning!

5 Likes