It overrides it. There is only 1 report interval setting.
But the polling can happen in parallel in V3.
V2 it’s one or the other.
You can also just send ‘?’ Yourself at any time in the terminal for an update
It overrides it. There is only 1 report interval setting.
But the polling can happen in parallel in V3.
V2 it’s one or the other.
You can also just send ‘?’ Yourself at any time in the terminal for an update
Right, I guess I worded that oddly. I get that the $Report/Interval would be overridden. I was referring more to in v3 where I have it set to polling but if I was using the tablet extension, it would end up doing both.
Sorry, I just re-read what you wrote and realized what you meant.
When polling happens, it still marks the last time sent.
So it can affect the auto poll, but in your scenario you will just get an extra update every second more than you need
I keep an extra long poll at like 1 minute. I’ve never had it happen, but it’s just in case it misses a last update or something I have it as a fall back
I came back out and re-flashed 3.7.17 probing working great! I think I will stay here for quite a while, nothing really benefits me that I know of,
I probed and it seemed just fine. I can test more Monday though. That is not good to hear.
Now, I have a tinybee. I am not sure if that is part of the problem, but my whole system is more responsive.
Tinybee talks to the stepper drivers a bit different than the Jackpot does, and I’m not sure there’s a large userbase.
It’s very possible some of the changes may be adversely affecting your setup and the only way that would be corrected is to have good bug reports to test against.
I’m not sure if Bart or Mitch have a TinyBee board to test against.
Interesting, well, I am barely smart enough for 3.7.17, so I think I will be fine with it.
Done.
That is awesome I just got stuck at that screen by accident, what a bummer. At least you can resume.
Well i posted in discord, he said he tested tinybee, would like me to github told them i would this weekend.
Not sure if you saw it, but in the other thread you posted in, I think this comment was meant for you.
Proably both me and original poster, as i did not use batch file. I used web installer! But i did not see that, thank you!
Yeah, just the highlighted part I think was in response to you saying yours was sluggish. The rest was for the other guy
I think i did have to power it up, so maybe i had a bad cable too. If so that sucks on my part!
Now i feel the need to go try it!
AHHHHH, you need to change a jumper to get usb power up! I am an idiot
Thank you, thank you, thank you! it seems good, I will post over on Discord.
You are right, @RockinRiley UI v3 does not retract after probing as default but there is a very simple workaround to make it do that. Here is the result from adding a retract of 5mm: Notice the gcodes used in the Terminal panel.
To enable it, you need to open the settings page and locate the Probe Panel, add this to the end of the line in “Finaliaze Probing Commands”: ;g91;g1 z5;g90 Hit save at the buttom of the page and you are good to go.
Good to know!