Meta commands underscore '_' no longer valid?

[dc42]

@nxt-1 underscores in variable names work for me in RRF beta7+7, so if this was a bug then I think it is already fixed in 3.4.

[Nxt-1]

@dc42 Well, underscores used to work for me in 3.3 as well, over on my duet wifi. That's why this is so weird to me.

[dc42]

@nxt-1 please test again using the 3.4beta7+7 files at https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=0. If you are running your Duet with attached single board computer then you will need to upgrade to 3.4.0beta7 via the package server first.

I can't see any reason why the acceptance of underscores or not in variable names would depend on context.

[Nxt-1]

@dc42 The 6HC is indeed running in SBC mode (with a jetson nanom for wich I plan to write a setup guide in the soon future) I am not willing to go the beta firmware route at this point.
I did however boot up the old wifi again and did a quick sanity check. That Duet is running V3.3.0 (RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01) and there the underscore is in fact allowed.

[dc42]

@nxt-1 so do you think this may be an issue in SBC mode but not in standalone mode?

[Nxt-1]

@dc42 I am not familiar enough with the different versions of the firmware these days (I am not following FW development as closely as I used to ). But my guess would indeed be SBC/standalone or Duet2/Duet3 hardware. I must again disapoint as I cannot test standalone mode on the Duet 3 since clever me a couple of months ago decided RJ45 access was not needed when designing the mount of the board.

Another small update, as a temp fix I removed all the underscores and re-ran the file. This time I got an Error: Failed to read code from macro bed.g: Unexpected closing round brace in line 104
Again something is fishy here, even calling

echo ")"

in console throws that error. This leads me to belive there is something wrong with properly escaping special characters in general for some reason.

[dc42]

@nxt-1 thanks for reporting this. That echo command work in standalone mode, so I've logged this as a bug in SBC mode.

[Nxt-1]

@dc42 I am just adding things I notice to behave differently as I go here. The bed.g script used to output some logs between each iteration of the loop. Now it waits for the whole thing to finish and then prints all at once, in reverse chronological order. So the messages that should be the most recent get printed at the bottom of the blob in console.

[chrishamm]

@nxt-1 This is already fixed in 3.4-b7, any chance you can give that a try?

[Nxt-1]

@chrishamm Again, my appologies. I need my printer at the moment and am not using beta firmware. I will consider a release candidate once a find the time to read up on all the changes.