file format error

[ajzbern]

when sending to printer adventurer gives file format error even with extension changed to .G

[andycb]

Hi,

I might need a little more info to get to the bottom of what's happened here, so some questions for you :)

What are you running the app on? (macOS, Windows 7, 8, 10..)? What version of the app are you using (shown on the about screen) Did you download the app directly, or from the app store? Which printer are you using it with (Flashforge Adventurer 3, Flashforge Adventurer 3 Lite, Monoprice Voxel, Bresser Rex..)? What is the printer firmware version When you say not valid, is it saying "Failed to connect to printer, is the address correct"? or some other error Does force closing the app and restarting fix this issue, or did it work one ever? If you're using version V1.2 can you attach the error log file please. You can find the log files for the app at this location: Windows: C:/Users//AppData/Roaming/adventurer-client macOS: ~/Library/Logs/adventurer-client

Thanks Andy

[ajzbern]

I have win 10 newest update AMD Ryzen 3900x gtx1080ti have the ff adv3, with newest firmware update. newest flashprint 5, and also have cura 4.12 beta cused both with all file extension changes. Tried .g and .gx I'm away from the PC I use for printing and can upload a log when I get to it tonight. The printer screen spits..... error with file extension.

I have since been just using flashprint but would love to use cura with it since the ff finder extension in marketplace. Also there used to be a coder on GitHub that was able to get cura to send the file directly to the printer but that's neither here or there since it's busted lol.

On Mon, Nov 8, 2021, 6:06 PM Andy Bradford @.***> wrote:

Hi,

I might need a little more info to get to the bottom of what's happened here, so some questions for you :)

What are you running the app on? (macOS, Windows 7, 8, 10..)? What version of the app are you using (shown on the about screen) Did you download the app directly, or from the app store? Which printer are you using it with (Flashforge Adventurer 3, Flashforge Adventurer 3 Lite, Monoprice Voxel, Bresser Rex..)? What is the printer firmware version When you say not valid, is it saying "Failed to connect to printer, is the address correct"? or some other error Does force closing the app and restarting fix this issue, or did it work one ever? If you're using version V1.2 can you attach the error log file please. You can find the log files for the app at this location: Windows: C:/Users//AppData/Roaming/adventurer-client macOS: ~/Library/Logs/adventurer-client

Thanks Andy

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/andycb/AdventurerClientJS/issues/197#issuecomment-963654065, or unsubscribe https://github.com/notifications/unsubscribe-auth/APS6SN2DCSQC4GDFOVTGIUTULBJXPANCNFSM5HMMBJHA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[350d]

I have the same error on macOS, Big Sur 11.6 Printer: Flashforge Adventurer 3 Client Version: 1.3.142

[andycb]

Thanks both for the info. I think Flashforge have changed something with the latest firmware on the printer (possibly by accident, or to lock this app out). I'm going to keep this bug open while I look for more data, but I don't have a good solution right now. If you're able to rollback the firmware, that might help.

[Stratoco]

Debug logging gives me the following after all the instructions:

<<<\n
<<<~M29\n
<<<~M119\n
<<<~M119\n
<<<~M119\n
<<<~M119\n
<<<~M119\n
>>>CMD M29 Received. \nDone saving file. \nok \n
<<<~M23 0:/user/file.gcode\n
>>>CMD M23 Received. \nFile opened: file.gcode Size: 0 \nFile selected \nok \n
<<<~M119\n
<<<~M119\n
>>>CMD M119 Received. \nEndstop: X-max:1 Y-max:0 Z-max:0 \nMachineStatus: READY \nMoveMode: READY \nStatus: S:1 L:0 J:0 F:0 \nLED: 1 \nCurrentFile: \nok \nCMD M119 Received. \nEndstop: X-max:1 Y-max:0 Z-max:0 \nMachineStatus: READY \nMoveMode: READY \nStatus: S:1 L:0 J:0 F:0 \nLED: 1 \nCurrentFile: \nok \n

[andycb]

It looks from that log that the file was correctly transferred to the printer - The printer checks the integrity of everything we send it to, and the app screws up the printer normally rejects it here.

So it's likely that it's the content of the file the printer dislikes, which is what I've seen from others on this latest firmware.

One contributor was able to make some progress by changing all the temperature values to remove the .0: https://andybradford.dev/2020/01/12/using-the-monoprice-voxel-with-ultimaker-cura/#comment-717

Are you able to try that?

Andy

[andycb]

Oh, also: If you want to isolate the slicing from the app, you can drag the gcode file from cura in to flashprint, and use it to transfer without re-slicing.

[Stratoco]

Oh, also: If you want to isolate the slicing from the app, you can drag the gcode file from cura in to flashprint, and use it to transfer without re-slicing.

It wouldn't let me just drag it in, found another limitation was the 32char limit on file name. However I was able to use the exact same file (once renamed - I had edited out the file name in the logs) through the multi-printer-control function on flashprint to send the gcode file over.

I will say that aside from flashprint's limitations I greatly prefer it to cura. Cura is way uglier, has some weird bugs, and my prints from flashprint just tend to turn out nicer.

[ikcir07]

Just updated firmware and now file transfers don't work. I get a file format error. It doesn't matter if the file is generated by cura or flashprint. If I transfer the file using usb it's ok. So, the problem is definitely due to the firmware update.