Macro for getting the Hybrid belts result in crashing

[mighty stone]

See the macro in the picture this make the real time analysis tool crash after the frequence sweep. Strangely the toolhead doesnt move to the coordinate in the macro

[keen fossil]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[mighty stone]

@echo hedge Here is the debug file

Position of the tool head while doing the macro

[echo hedge]

Oh the toolhead never moves?

[mighty stone]

Nope

The first macro with the GENERATE command was moving to the first position but after that crash and then it just continued sweeping through frequency

[echo hedge]

Can you describe the "crash" ?

[mighty stone]

Goes through the frenquencies fine on the first command, stock the data, then both of my computer screen goes black, the Live resonance tool reset and no data is collected anymore. But i see the in the command dashboard that its still sweeping frenquencies

[echo hedge]

your computer screens go black 😳

[mighty stone]

Yes

[echo hedge]

as in no signal to the screen?

[mighty stone]

i mean its stay black for like 1-2 second

[echo hedge]

What graphics card do you have in that machine?

[mighty stone]

3080

[echo hedge]

Browser?

[mighty stone]

Chrome. when i say goes black its more like a black screen of a program crashing

[echo hedge]

Right so you can still see the windows interface etc?

like your start menu? Mouse cursor?

[mighty stone]

let me do it again just to be sure

Also just saw it move to the position then comeback to the middle

Ok yeah its tool that goes black and reset

i can see my windows stuff

Only record the right belt

[echo hedge]

Okay sounds like it's possibly a browser problem. Can you try ms edge?

It's interesting because your log says there's no WebGPU support, but chrome has WebGPU support. Indicates something is funky.

[mighty stone]

trying it on edge lets see, but it still weird that it goes to the position then come back to the middle

[echo hedge]

I think that's part of the GENERATE_RESONANCE command, it's using the points from [resonance_tester]

I can fix that

[mighty stone]

edge also reset

[echo hedge]

wonder if it's an nvidia driver issue

[mighty stone]

Also a couple days ago i switched the commands to TEST_RESONANCE

also in the commands shouldnt there be a Y and Y1 ?

[echo hedge]

i'm testing on a 4090 with version 551.76

works in both chrome and edge

[mighty stone]

dont tell me i need to upgrade my gpu XD

[echo hedge]

ah yeah this one definitely moves the toolhead

[mighty stone]

but it come back

[echo hedge]

No those are stepper names not axes 🙂

[mighty stone]

aaaah

[echo hedge]

Nonono you don't, your 3080 is more than capable, this thing runs on phones 😂

[mighty stone]

when the 5080 comes out ill change 😛

[echo hedge]

I think the problem is related to graphics card interaction.

Not sure where in the stack the problem is however

I assume you play games on that 3080, and don't have any problems usually?

[mighty stone]

nope runs dandy

[echo hedge]

Aight, i'll run some more experiments, thanks! I'll ping you once i inevitably have more questions 😂

[mighty stone]

Aye aye captain

[echo hedge]

Reproduced

I'll figure it out eventually now

[echo hedge]

Problem solved

Was a bug in the charting library i was using.

[mighty stone]

So whats the fix for me ?

[echo hedge]

There's an update coming to the configurator in a few minutes

Fixes the bug, plus adds beacon support and console ouput (and a bunch of other minor fixes)

[mighty stone]

Oki doki so start and then update nice ! Thank you!

[echo hedge]

ready to update now! 🙂

[mighty stone]

Should it be visible in the update manager?