Advanced Search

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?

 

 

Awesome, thanks!

Can you try a HalLedLight and see if it shows up too?  That'd confirm I'm off the rails somewhere.

here it is working.. i did not change anything at all just dropped the halbutton widget in the usertab and gave it a pinbase name saved then started probe basic and everything was there!

ok i just tested and i see the test button i created in halshow, i can set and clr it to enable and disable it, it is under Pins/qtpyvcp/hal_test_button. sooo it is working here, not sure what you might be doing differently?

That is a cool trick! Glad to know about Show Hal Configuration. Thanks.

I am using the Axis GUI.

When I watch the ESTOP-ext variable (is variable the correct term here?) I see that it changes state when I toggle the hardware ESTOP. Hal Show Configuration shows yellow when the hardware ESTOP is not active and red when the hardware ESTOP is active. That seems right to me.

When I watch ESTOP-out, it just stays red the whole time regardless of what I do in hardware or software. This seems wrong to me, but it is also consistent with the problem I am having.