Advanced Search

cakeslob wrote:

tommylight wrote:

What GUI?
Every GUI that existed in 2.5 should exist in 2.9 and much more....
If you want to have stuff saved to USB, google "debian 12 persistence usb"

mini and keystick were axed after 2.7

I was not aware of that, thank you very much.

I use Probe Basic exclusively but I'm about 2-3 months behind on updates at the moment.

Haven't come across the errors you describe but I did have to add a debounce filter with a delay of 10.

I've been following the QtPyVCP and Probe Basic changelogs on GitHub and if my memory serves me right there has been some probing related changes in the past few months. Maybe Lcvette or TurBoss can figure out why you are seeing this behavior.

Tinine wrote:

The best single-chip solution for motion control is without doubt The P2 Propeller 64 "smartpins" (all can decode quad @ sysclock/4 with no impact on any of the 8 identical cores) any pin can be a 16bit DAC, etc.

For the price, i always will choose Mesa, the fact it has 16 bit DAC is nice but still Mesa support wins.
It is good, though, for sure.

As far as I understand it as long as they're part 107 licensed and have a laanc authorization they can fly almost anywhere
unless it's highly restricted airspace. The homeowners have no say over the matter. It's frustrating to say the least.

I fixed it, but probably not in the easiest way. I completely rebuild my *.ui file with the designer, but used the designer on the new pc instead. Screens look the same, use the same widgets and now the UI runs.
Loading a *.ui made on a older version apparently is not backwards compatible...

After the ui finally loaded I ran into other issues. Took me a while to find what was causing that. Turned out my existing python user scripts refused to run. To fix that the first line in the *.py files needed to be changed from:
#!/usr/bin/env python
to
#!/usr/bin/env python3
also I changed the rights to the python files with chmod u+x

After that the scripts ran without any problems.

tommylight wrote:

What GUI?
Every GUI that existed in 2.5 should exist in 2.9 and much more....
If you want to have stuff saved to USB, google "debian 12 persistence usb"

mini and keystick were axed after 2.7

I was thinking of using 2 different drivers with different microstepping...does not seem to work...any other workarounds?

I don't see why that would not work. Basically a tandem axis, one axis mapped to two joints.

What is the current state of this as i will be getting some W5500 to play with soon?
More importantly, any long term use results on reliability?
Thank you.

The only difference between LPC1768 and LPC1769 is the working frequency, so everything should work for both, see last post on the link.
community.nxp.com/t5/LPCXpresso-IDE/LPC1...ferences/td-p/578600

Hi...so one more question...I was thinking to drive 2 tools off same axis from computer...the only thing is that they have different scales..meaning one is screw...other is gear....almost 10 to 1 difference...I was thinking of using 2 different drivers with different microstepping...does not seem to work...any other workarounds?

Thanks,

Rick

So I tried a few things but it seems the burnout is holding back progress. The burnout is when the table rapidly accelerates without command. It always burnout in the same direction regardless of table movement direction, in the X axis case its in the negative direction. When P=100, the x-offset from home is 2 thou. P=200, x-offset from home is 1 thou. P=300 burnout. So I can't get to P values that allow the machine to home to 0,0,0.

I caught a burnout on the Halscope doing a G01 F50 X1 move and you can see the following error oscillates then shoots vertically to 1 (P=300). This is where the burnout starts, and you can see the velocity command drops to 0 when the following error cuts power. Even though power is cut, the table has enough initial acceleration to move almost 2 inches. I put a Halscope of P=100 for reference (there is still a bit of oscillation, not sure if that's normal). See attached.  

Any idea on what could be causing these runaway oscillations?

-- EN
Hello everyone,

I am aware that this is not a pleasant topic and that some things do not always work as they should. Above all, there is a lot of work behind it, and for that I would like to thank everyone who actively supports here.

However, I have noticed that a Joomla version 3.10.xx is still being used for which there is no longer any support or security updates. If I see it correctly, the forum (Kunena) is not up to date either.

Yes, moving to a new Kunena forum is tricky to almost impossible, and even upgrading Joomla to the current version 5 doesn't seem feasible without moving the forum.

Nevertheless, I wanted to address this topic without anyone feeling offended - quite the opposite. I just want to encourage a conversation about it.

I would be interested to know whether an upgrade is being considered or what the plans are for the forum in general. Because there will probably not be much support from Joomla or Kunena.

Greetings Mücke
Translated with DeepL.com (free version)

-- DE
Hallo zusammen,

ich bin mir bewusst, dass dies kein angenehmes Thema ist und dass manche Dinge nicht immer so funktionieren, wie sie sollten. Vor allem steckt viel Arbeit dahinter, und dafür möchte ich mich ausdrücklich bei allen bedanken, die hier tatkräftig unterstützen.
Allerdings ist mir aufgefallen, dass immer noch eine Joomla-Version 3.10.xx verwendet wird, für die es keinen Support und auch keine Sicherheitsupdates mehr gibt. Wenn ich es richtig sehe, ist auch das Forum (Kunena) nicht auf dem neuesten Stand.
Ja, ein Umzug auf ein neues Kunena-Forum ist heikel bis fast unmöglich, und auch ein Upgrade von Joomla auf die aktuelle Version 5 scheint ohne einen Umzug des Forums nicht realisierbar.
Trotzdem wollte ich dieses Thema ansprechen, ohne dass sich jemand angegriffen fühlen soll – ganz im Gegenteil. Ich möchte lediglich ein Gespräch darüber anregen.
Mich würde interessieren, ob ein Upgrade angedacht ist oder wie die Pläne für das Forum generell aussehen. Denn von Seiten Joomla oder Kunena wird es wohl keine große Unterstützung mehr geben.
 Gruß Mücke

Im not sure yet, i know skr 1.4 uses LPC1768 , SKR 1.4 TURBO uses LPC1769 , but can i use the same config.txt for both ?

SKR 1.4 uses LPC1768

Looks nice!