Ortur OLM2 S 2 will not update to firmware v191

LightBurn Hardware Compatibility
, ,
1

I’ve found some posts by people having problems updating some older, 1.8x versions, which sound like the same behavior I’m seeing. The few that had solutions, didn’t work for me, and the rest just simply went silent with no solution posted.

I’ve had no luck with Ortur tech support. They insisted that I must be doing it wrong, so at their request, I sent them a video of me doing the upgrade, and then I never heard back.

What’s happening is I get it into firmware update mode, it shows up as a removable device on my PC, I copy the bin file over and the Ortur immediately disconnects and shuts down. When I bring it back up and fire up Lightburn, it still shows version 190. I do the $RST=* command to factory reset, still 190.

I’ve verified several times that I’m downloading the correct firmware, and redownloaded it just in case something is going wonky there. I’ve tried different USB cables, different ports on my PC, unplugging everything else from the Ortur, letting it sit with no power before the upgrade, Debian 12 and Win 11 Pro. Always the same behavior every time.

The only potential solution I haven’t tried, is to spin up a Win98 VM and do the upgrade from there. One person apparently had success with that.

I have tried it probably 20 times at this point. I’m positive that I’m doing it right. Here is the Google Drive link to the video, if anyone would like to see if I am in fact messing up the procedure somewhere.

Thanks in advance for any advice.

Edit: added Google Drive link.

1 Like
2

Please share the video of your experience. The more information you can provide, the better picture we’ll have of what’s going wrong.

1 Like
3

Will do. I’m one of those people that is generally wary of clicking on Google Drive links posted by people I don’t know, so wasn’t sure how it would be received here.

4

Thanks, I’ve reviewed your video. After you’ve put the .bin file in, can you leave your laser off for a few seconds longer? I wonder if your laser isn’t getting enough of a power reset to recognize the .bin file?

Maybe @gilaraujo will have some insight

5

Thank you @JessN

Normally when an Ortur turns off immediately in firmware mode its a .bin file rejection

@deadtom With the current firmware, can you connect to LightBurn?
In the console window type
$i
press enter.
Post the output, please?

6

Sorry the information is in the video.

190 OLM2 S2

I would follow Jess suggestion
a) unplug 24v Power
b) use JUST usb - and if possible use a different computer with a simple non modified Explorer. Seems you are using a 3rd party file explorer right?

At times just changing computer makes all the difference

7

@JessN I considered that, and I have left it off for several minutes before turning it back on. Unfortunately, same result.

@gilaraujo The OS in the video is Debian Linux, nothing modified in the file manager. I have tried it from another Linux laptop, and from a Win 11 Pro laptop. I have not tried it with just USB, so I will give that a shot when I get home this evening.

Thank you both!

8

I never had much success using Linux as a Firmware updater OS for Ortur.

Do note, 1.90 to 1.91 has no actual many changes, except a Version Bump update.
G20 on Inches mode fix and M7 M8 fix for the Ortur Enclosures compatibility

9

The M7 M8 fix is the one I need. I could just get another power supply for the fan itself, and manually switch it on or off when I need it, but that means I’m still stuck at 1.90 if there are ever any more significant bug fixes released. I’d also just like to automate as much as I can.

Thanks again.

10

I would suggest a Windows machine if possible. And be sure no antivirus scans the ORTUR drive before transfer.

Its a bit sensitive at times

11

I’ve done that. Also failed. :frowning:

12

Any chance you could borrow or take the motherboard with you to some other PC Windows?

I have seen it happen where - for no particular identifiable reason PC 1 dont work, PC 2 does.

13

I can check out a different laptop from work, and see how it goes. I’ll do that this evening as well.

14

Remove the board enclosure from the laser.
All you need is the board and an USB cable.

And easier to carry! :smiley:

1 Like
15

I got it to work, but I’m not smart enough about file systems to be able to properly explain why it works.

I first tried putting the Ortur in upgrade mode without the power supply plugged in. I got the same behavior. Filed coped, and the Ortur shuts off abruptly. Upgrade doesn’t take.

I then fired up a different Win 11 laptop, did the same thing, and got the same behavior.

Then I got to thinking about how the Ortur can be persnickety about file names, and if anything is off, it will reject the file. I don’t know enough about how different file systems read file names to know the specifics here, but I do know that what we read as a file name is not the same as what the file system reads as a file name. When transferring a file between two file systems, there is some translation that takes place, making it so that the receiving file system reads the file name correctly.

What I had been doing was copying the bin file from my Debian system, which uses an ext4 file system, to the Win 11 laptop, which uses an NTFS file system, and then from there to the Ortur, which uses an msdos file system. Something was getting missed when moving it from ext4 to NTFS, and then sticking so that the msdos system wasn’t reading it right. The Ortur thought it was an incorrect file name, and rejected it.

When I copied the whole zip file over, and then extracted the bin file from the zip on the Win11 box, the upgrade was successful.

I’ll post this over on the Debian forum, and see if someone there can explain it to me, but that is how I got the upgrade to take.

Sadly, however, this did not resolve the M7 M8 bug that is supposed to be fixed in this upgrade. Lightburn reports that it is now version 191, but the enclosure fan is still shutting off when the air-assist fires up.

It’s annoying, but at least it’s a partial win, I suppose. I’ll just have to run the fan on its own power supply with a switch, and operate it it manually.

Thanks again @gilaraujo and @JessN for your help.

2 Likes
16

Sorry but I’ve not been around the LightBurn forums for a while since they stopped making a Linux version. I solved this problem a few years ago and posted the solution in a few forums here in on other sites. Ortur implemented their bootloader and firmware uploading to use more than basic FAT filesystem directory names, so in Linux and on Mac you have to install the MSTOOLS package and use the mcopy command. Search these forums for mcopy and you’ll see a number of posts I made about this.

mcopy -D mM OLF_000.BIN /media/–userID–/ORTUR\ LASER/
up-arrow enter, , reset, initiate 2nd update process. the mcopy command can write the FAT directory file short name and the FAT16/32 directory long name.

mcopy -D mM OLF_134.BIN /media/$USER/ORTUR\ LASER/
then keyboard up-arrow enter to repeat and make sure it’s written
then reset the Ortur laser controller.

17

I saw those posts. I tried the mcopy command and didn’t have any luck with it. Same exact behavior.

18

My scripts had running the mcopy command 2 times for each bin file and I recall that was how I did it on the commandline too. I also made sure to run the sync command before unmounting the Ortur virtual drive.

Ortur shared their bootloader file with me so I could help some people out who bricked their systems on Macs and I had bricked mine so after putting on the bootloader I hashed out why a Win95 VM worked and Linux or Mac didn’t.

You probably didn’t run the mcopy command a 2nd time and that was why it wouldn’t accept the firmware file. Unless they changed the bootloader to make it worst than before. So silly requiring those hidden directory structures when they themselves controlled the firmware file names and could keep them 8.3 compliant.

19

The zip I downloaded only has one bin file in it. As soon as I run the initial mcopy command, the Ortur immediately shuts down, so I never get the opportunity to run it a second time.

20

The OLF_000.BIN file was a file which cleared( zero’ed ) the firmware area of the controller. I don’t recall if it was supplied with all Orture firmware updates but I got it off their website and I used it just to be sure people were getting fresh firmware installs without the chance of data corruption from something hanging around from the old firmware upload. Again, I was supporting people who shipped their controllers to me, was doing it for free, and wanted to not have to have the resend their board later.

The OLF_134.BIN was the actual updated firmware file. And if you were getting immediate shutdowns something was odd for sure. IIRC the Ortur virtual USB drive was very small, under 64K in size and each of the BIN files I had were 48kB and 46kB in size. Mac people bricked their Ortur controllers because they used the Finder to copy the files and that tool copied the file but also copied a database file over which Finder would try to use later but that database file was WAY larger than 64kB and once filled with junk, nothing could get put on it. People on Windows were having problems because the files they were copying were named OLF_134.BIN.txt or something like that because the Windows Explorer file browser added the extra hidden extension.

I’ve not updated my Ortur machines in a few years so not sure what size recent firmware files are and if they would brick or fail to install. GRBL v1.1 has been working good enough so I’ll not try v191.