Software bundle 3.5beta1 released

Exerqtor

@dc42
Trying out some of the new stuff and i can't seem to get the fileexists function to work.

Just to try it out i added this at the end of homey.g:

if fileexists(homey.g)
  echo "fileexists works"

When i run the macro i get this error:
Error: in file macro line 65 column 15: meta command: unknown value 'homey.g'

jay_s_uk

@Exerqtor maybe try the full file path? I.e. 0:/sys/homey.g

Exerqtor

@jay_s_uk said in Software bundle 3.5beta1 released:

0:/sys/homey.g

That returns Error: in file macro line 65 column 16: meta command: expected ')' so I have no idea what I'm doing wrong😅

If I try /sys/homey.g I get this error X Y steppers at 100% of max current! Error: in file macro line 65 column 15: meta command: expected an expression.
And with sys/homey.g I get Error: in file macro line 65 column 15: meta command: unknown value 'sys'

jay_s_uk

@Exerqtor you may need to encase it in ` or "

Sindarius

@Exerqtor you probably need to quote the file name so it is a string

“0:/sys/homey.g”

Looks like @jay_s_uk beat me to it

Exerqtor

@jay_s_uk said in Software bundle 3.5beta1 released:

@Exerqtor you may need to encase it in ` or "

@Sindarius said in Software bundle 3.5beta1 released:

@Exerqtor you probably need to quote the file name so it is a string
“0:/sys/homey.g”
Looks like @jay_s_uk beat me to it

Yup, that sure worked!

Edit:

Don't need the full filepath either, since it's on 0:/sys/ it works with just the filename, and above that you only need /sys/foldername/ if it's located in 0:/ 🤘

MaxGyver

@dc42

I have noticed two minor things after updating:

G10 without L parameter will cause my macros to get stuck
M569.1 without an E parameter defined will trigger a warning/error

Thanks to the Team for all your hard work!

chernogorsky

Create a separate ticket. Movement issue + some minors

dc42

@MaxGyver said in Software bundle 3.5beta1 released:

@dc42

I have noticed two minor things after updating:

G10 without L parameter will cause my macros to get stuck

Please start a separate thread about this. In particular, show the G10 command(s) you are using.

M569.1 without an E parameter defined will trigger a warning/error

Please see the upgrade notes.

dc42

A bug in the 3.5beta 1 main board files has come to light. The bug causes a reset or other odd behaviour if the G32 command is used to perform true bed levelling on a machine with multiple Z motors.

I have now identified the cause and fixed this issue. New main board binary files containing the fix are available at https://www.dropbox.com/sh/28zqy8t165nwa2f/AACZvmVSGhWMSpjKX43MsSWSa?dl=0. A few other changes have been made in these builds, see https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta#reprapfirmware-350beta2-in-preparation for details.

Note, these main board binaries have received minimal testing; however the changes since version 3.5beta1 are small.

A Former User

This post is deleted!

chernogorsky

To anyone like me stacked with SBC and 3.5
my way of resotoring stable version (after changing /etc/apt. ... to stable)

sudo apt install duetcontrolserver/stable duetpimanagementplugin/stable duetpluginservice/stable duetsd/stable duetsoftwareframework/stable duettools/stable duetwebcontrol/stable duetwebserver/stable reprapfirmware/stable duetruntime/stable

dc42

@Nightowl said in Software bundle 3.5beta1 released:

Just out of curiosity @dc42, did you manage to implement any improvements for Power Loss/Resume for CNC machines, please?

It was a while ago, but we discussed it here.

Yes, commands to restore the spindle speed and direction are now included in resurrect.g.