Advanced Search

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.

I don't have any of the qtpyvcp pins listed in any of my hal files - but they're still loading.

I get that connections to any of the qtpyvcp hal pins needs to be done in post-gui.hal.

Would you mind trying to create a qtpyvcp hal pin like I'm attempting and see if you can make it work?

I don't want to start fiddling with the main probe_basic.ui file, but you or one of the other devs might have some test configs to see if you all can figure out if this is just me or a bug.

the user tabs get loaded after so they may need to be loaded through post gui hal so they get initialized during startup otherwise they may be created after the initial ui loads but before the child ui is loaded. but just guessing as i have not tried what you are doing before with halpins,. if you have them listed in the main hal file i would move them to the post gui and retest.

just loaded up a new computer today and copied and pasted the config and it just works.  conversational stuff all works fine.  which shows there are not library's that are needed.  its all internal to the config files

the file auto loads also with axis load remote file feature.  so i am not getting the bug that tuxcnc got earlier.  however i am using axis gui so other gui's might have issues.  can't be bothered currently supporting the other gui's but i might if more people post here and are using the software.  but no stress.
 

If using Axis GUI (other GUI's may also have this), use the "show hal configuration" from the machine menu to see if the hal stuff is working correctly, on the left side choose the pins to watch on the right side, then toggle e-stop and see what toggles and what not.

Here is fixed firmware fro the 7I76EU/7I76U that fixes the MPG encmode
parameter direction issue. This is the full image that needs a PIC programmer
to install. Will have a bin file for remote updating soon.

 

Now is it possible you have a 7I85S instead of a 7I85?
(look at the paper label on the back of the card)

That would show these symptoms ( only the last sserial channel works
as TB1 pin 17..24 is the only serial port on a 7I85S )

 

OK tested a 7i76E with 7i76e_7i76x1_7i85x1D.bit firmware:

md5sum 7i76e_7i76x1_7i85x1D.bit
0d0922e5c4306ceba4e077fff3c02097  7i76e_7i76x1_7i85x1D.bit

And it works as expected, that is sserial devices 0..6 work

SSerial channels are organized as follows:

0 Local 7I76E field I/O
1 7I76E Serial expansion slot TB3 15..20
2 7I85 Serial 0 TB2 9..16
3 7I85 Serial 1 TB2 17..24
4 7I85 Serial 2 TB1 1..8
5 7I85 Serial 3 TB1 9..16
6 7I85 Serial 4 TB1 17..24