Advanced Search

murdemon wrote:

Can share vivado and linux project ?
 

It’s a bit complicated, as it’s part of Riocore and everything is generated.
Furthermore, I don’t use Linux either, but rather baremetal (LWIP)

github.com/multigcs/riocore/tree/dev/riocore/plugins/udp2axi
 

here is web based interface

Can share vivado and linux project ?

  So yeah it's been a good long time since I have done anything with the pick and place
to say nothing of the alignment gui. That said a project at work has put me in a position 
to work with Tkinter. I would not say I am proficient with it or python but it has taught me
how to use it to some degree. I am hoping it will translate to something beneficial.
The only thing I know is that is that I don't know anywhere near enough.

i use the EBAZ4205t as an external board via UDP like normal mesa-cards.

@tim
it's only in the dev branch yet:

rio-flow riocore/configs/CarrotBob/config.json

Just for curiosity: How much would one of those "surplus" cards cost?

Would it be manageable for someone who is only end user level?
Is it really easier to use than a MESA card?
(referring to the original complaint that the documentation and instructions were not sufficient)


Maybe in 2020 the complaint was more valid than it is today. Because some info and updates made it better since then.

In really already have IOs on stmbl drive , now add webui interface, all work on board 

meister wrote:

Thank you Tim,

Thanks very much for the details; I’ve entered the board’s details as best I could,
I hope it’s all correct so far – please do have a look over it.
What’s not quite clear to me yet is, how do you flash it? Are there any connectors on the back?

You’re also welcome to send me some text and a link for the description, and I’ll update it.

Dear meister:

Can I use this config?

Tim
 

Hallo, 
seit einigen Tagen verzweifle ich am Handrad XHC WHB04B-6 Funk. Kurz nach dem Start der Maschine erhalte ich in der Konsole folgende Fehlermeldung 
xhc-whb04b-6: hal/user_comps/xhc-whb04b-6/usb.cc:460: bool XhcWhb04b6::Usb::setupAsyncTransfer(): Assertion `0 == r' failed.

Nach dem was ich bisher herausgefunden konnte scheint es ein Problem auf USB-Ebene zu sein. Die einfachen Optionen (USB Port 2.0, *.rules Datei anpassen habe ich bereits versucht - leider ohne Erfolg. 

Auffällig häufig tritt der Fehler beim drehen am Handrad auf. Die Achsauswahl, diverse Tasten können mehrfach problemlos gedrückt werden und werden in der HALSHOW auch korrekt angezeigt. Beim drehen am Handrad tritt der Fehler relativ schnell auf. Deshalb bin ich nicht sicher ob es sich wirklich um ein USB Problem handelt. 

Meine Maschine läuft auf einem Pi5 8GB mit einer Mesa 7i96s und einer GMOCCAPY Oberfläche 2.9.10. Mechanisch ist es eine Gantry XYY2Z. 

Hat jemand dieses Handrad erfolgreich im Betrieb und kann mir eine "geprüfte" HAL Datei, *.rules Datei zur Verfügung stellen? Einfach um Fehler in meiner Konfiguration ausschließen zu können. 

Vielen Dank 

Grüße Erwin

 

That did the trick, thanks.

It's working!

After reading through the Lichuan LC10E thread ( forum.linuxcnc.org/ethercat/52341-proble...ethercat-servo-drive ), where somebody discovered that the issue is around how the clock is setup, the key are these missing lines from my xml -

<syncManager idx="0" dir="out">
      </syncManager>
      <syncManager idx="1" dir="in">
      </syncManager>
     

Added those for each slave, and all the drives now intialise and activate when LCNC is opened.
Now to decide if I want to re-retrofit them to my little mill, or buy an extra drive and motor for the plasma table I have part built..

tested here on sim and everything is now working as it should be again! thanks for bringing it up to my attention both of you!

I think i have this resolved now and will be pushing out shortly today was a porting breakage that got missed one some other fixes.the object name user_main and user_sb this property determine the name displayed in the ui for the tab button text. so if you name it spumco_sb it will display SPUMCO SB in the ui.

I made a post regarding this thread in the QtPyVCP channel on Matrix and got a reply that it seems to be a bug in the latest version.