Advanced Search

I'm not worried about the DRO at this point - the widget rules are accomplishing what I want -  and I understand I'm working on an edge-case.

My intent now is to add LED's to the user sidebar tab, not circle back and mess with the DRO again.

I'll try it again without saving the probe_basic.ui file and see what happens.

EDIT

I just did an update/upgrade and managed to overwrite everything, since I was 'just fiddling around' I didn't bother making a copy of the PB config folder.  ARGH.

I'll have another go tomorrow.

you should not be saving the probe basic ui file only the files from the config folder. however, the main probe basic ui must be opened first to load the qtpyvcp widgets correctly. you can open it but not save it, only save the config user files. each one must be saved and then close designer and reopen for the next that should avoid the call for the qrc file which is located in the usr/python3/probe_basic system wide directory. you really should never have to go into that for this work.

the dro ui's like i said above have a timer that prevents them currently from registering the hal widgets on initial startup. I was too tired to mess with it tonight, but will have aquick look in the morning to see if its something simple. i know i had to add the timer to prevent other issues i was dealing with from loading multiple ui files so i make no promises. you may need to add the led's to the sidebar tab or something which shouldn't have any issues as demonstrated previously above.

Once your drives are connected with LinuxCNC, it won't care if you have Mesa cards or ethercat.
Ethercat may be more complex to install 

Ok, HalLedIndicator is now showing up in halshow.

Every time I tried to edit probe_basic.ui I couldn't save it due to permissions.  And trying 'sudo editvcp probe_basic' resulted in an error before opening.

Had to

• make a copy of probe_basic.ui and probe_basic.qrc
• paste copy in some non-root folder
• open sudo -thunar and rename the original
• open the copy in vcp
• open the user_tab.ui file and edit/save both ui files
• using sudo-thunar paste the probe_basic.ui & .qrc file copies back in to the python3/dist-packages/probe_basic folder.

I suspect my earlier failure is that I didn't have probe_basic.ui open, or the right .qrc file in the right place.

The user tab is not showing up on the screen (see attached), but at least I've made some progress.

try creating a config using lcec_configgen

so the dro's were not really meant to be customized in that manner so they went last in the loading sequence using a timer to stop any conflicts during load, that being the case the hal widgets do not get registered for the dro ui's only for the usertab uis.. i will see if there is some magic i can do to include the dro's and post back when i have an answer on it!

tietouwa wrote:

Is simply improving heat dissipation enough, or are there other solutions? The N100 is too expensive.

No it was a fault in the kernel. There is nothing wrong with a J1900, I used one for years, its just the baytrail chipset.

Billy wrote:

Aside: I have not been able to find any documentation that really explains how ESTOP is expected to work?  I'm unclear on if I should work with estop_latch or not?  The estop_latch documentation is also pretty thin and does not appear to include any examples for either simple or complex configurations?
 

Yes, you should use estop-latch if you have an external estop button (or a safety relay but that's another story). Its pretty well described in the man page and there was a hal tutorial about it on the forum.

works fine!  how are you creating things?  are you opening using editvcp probe_basic and then opening the user ui?

No, I edited the user ui directly.  Sounds like that may be my problem.  I'll have another go at it and report back.

I'm on trixie, did a pull just a week or so ago so I should be up to date.

 

Any progress on this?
Pictures of drive wiring might help, if there is no schematics.

Having read this several times, i still do not know how to reply to it, as there is no question or answer, just some statements and some pictures....
What is missing? Or what am i missing?

Did you manage to fix this?
-
We would need much more info about your setup, as that can be caused by incorrect settings in the ini file or by interference on the parallel port from touching material that is not in the same potential as the PC.

Probably needs to be tied to one of those pins, not as you have them to iocontrol as it is for enabling/disabling the machine so not controlled by e-stop.
You can also wire it directly in haland it should work fine.

maybe try bringing over the latest user files, there have been some changes and some may no longer be up to date with the porting we did.  the testing i was using used the latest develop branch for the trixie debian 13 probe basic for reference, i do not have a bookworm machine at the momenht while im working on another project so cannot test there if that is what you are on. if so i would recommend updating to the trixie version
 

works fine!  how are you creating things?  are you opening using editvcp probe_basic and then opening the user ui?