Firmware 1.19.2 released
-
Thanks for the feedback.
The next release won't be until October, due to preparation for the TCT show and other commitments I have.
-
Seems ok for me too on my Delta
Good job David
Thank you -
Will it be showing up on github?
-
Also working here with my Prusa-Style 24v, E3D-Chimera Dual and BLTouch. IR-Probe from David also works without any glitches.
Good Job David as always.
Cheers from Germany
MoS-tekknix -
Thx for that Update
-
Thanks for the update.
M37 Seems to do more than pure simulation. At the end of processing, my heater went from Active to Standby. Not sure if this is intended.
-
Immediately after the update my Heater 1 is showing 2000 degrees Celsius. Its not even on right now. Although my machine had trouble with a print last night. I'll have to inspect the wiring.
(UPDATE) Yes I have a wire that came loose. So no issue with the firmware.
-
Working good for me, still a few issues with network dropping.
One suggestion, is the new M37 Command, if it could be part of the context menu that pops up when right clicking a file in the G-Code file section. So i don't have to type out the whole filename each time.
Great work and amazing products with exceptional customer service
-
One suggestion, is the new M37 Command, if it could be part of the context menu that pops up when right clicking a file in the G-Code file section. So i don't have to type out the whole filename each time.
I've already made that request to chrishamm.
-
I'm still on 1.18 on the Railcore. Been too busy to get it upgraded. I have some time today, I'll get 1.19.2 on it and see how it does.
-
Good here are Cartesian home brew.
-
Run heat free tests on my core x-y machine and not seen any issues.
1.19+4
Actual build time: 2hr20m36s
Time to run the simulation: 0hr5m30s
Predicted build time: 2hr211.19+5
Actual build time: 2hr24m37s
Time to run the simulation: 0hr5m32s
Predicted build time: 2hr251.19.2
Actual build time: 2hr24m37s
Time to run the simulation: 0hr5m35s
Predicted build time: 2hr25Only minor comment so far would be that as the file system is case preserving on the SD Card that the response from the build time estimation shouldn't mangle the build file name to all capitals.
-
I'm glad the simulation facility is working well. The case of the filename when it reports the print time will be the same as the case that was received in the M37 command. So my guess is that whatever program you used to send the M37 command converted the input to uppercase.
-
Did we lose the ability to edit an existing macro with 1.19?
I haven't been able to since the upgrade.
I can check the box next to one but don't see a delete or edit option. Clicking the name pulls up the confirmation dialog asking if I want to run it or not.
Also since the 1.19 update, when I scroll down in Chrome to look at time estimates/etc, within 2 seconds it updates something at the top and resets the scroll back to the top.
-
Did we lose the ability to edit an existing macro with 1.19?
I haven't been able to since the upgrade.
I can check the box next to one but don't see a delete or edit option. Clicking the name pulls up the confirmation dialog asking if I want to run it or not.
Also since the 1.19 update, when I scroll down in Chrome to look at time estimates/etc, within 2 seconds it updates something at the top and resets the scroll back to the top.
Hover over the name of the macro and right click and you'll see a menu popup to edit and delete
-
Fair enough! Not really an issue since the Fat16|32 file system won't let you have test.txt and TEST.txt in the same directory anyway.
I'm using version 1.19 of Christian Hammacher's Web Interface.
-
I think DWC has a configurable option to convert input to uppercase, that is enabled by default. As firmware 1.19 accepts gcode commands in lower case, you should no longer need to use that option.
However, I also thought chrishamm changed it so that quoted strings don't get converted. Perhaps I was wrong.
-
Did we lose the ability to edit an existing macro with 1.19?
I haven't been able to since the upgrade.
I can check the box next to one but don't see a delete or edit option. Clicking the name pulls up the confirmation dialog asking if I want to run it or not.
Also since the 1.19 update, when I scroll down in Chrome to look at time estimates/etc, within 2 seconds it updates something at the top and resets the scroll back to the top.
Hover over the name of the macro and right click and you'll see a menu popup to edit and delete
Ah, thanks. Not sure it's very intuitive but I'll go with it.
