Advanced Search

so on the 225 i still had the io board, so i just used the manuals pinouit on the control. so thats not gonna help.

I have some tc227 data though, ill dig an see if theres anything useful on the encoder - its mostly mechanical drawings.

I was wrong, I've found it, sorry.

It shows a 404 error on Codeberg, and the videos on YouTube won't open at all.

Promise!!! I am hoping that moment is coming soon like any minute I got up to line 197 hal c by commenting out and now I have the stepgen parts. It is amazing that i can have joints 1 and 3 work and o and 2 not work for stepgens. I have checked ini and trivkins and joints all line up correctly shows xyyz and 4 joints but only 2 work with the exact same text in each section???? I will take Rod's suggestions and see if i can get further ahead. One good constilation is I am learning lots all I have to do it put it together before I have a brain anyerism -LOL
Thanks again

thanks Rodw,
I will try that I have been doing similar things in terminal and when get so bogged down I just comment them out and move on and will come back to them later.
I appreciate your help,
Thanks again,George

I think that behaviour was when I had the auto login set up. On power up the computer logged me in without entering user/pw. When it auto logged me out it did come back with a user/pw screen. But I think that timed out and the auto login kicked in.

I am sure, under the configuration changes I made above, that I left the computer logged in with linuxcnc running. When I checked on it later it was running the XFCE desktop but had closed linuxcnc. I'm fairly sure it did a logout/auto login which closed linuxcnc.

I'm also sure running 2.9.8 it logging me out after a set time, between 30-60 minutes. Without auto login it waits with a user/pw screen.

Beyond my comprehension. If you find any insight please let me know. But for now I have 2.9.4 up and running.

Thank you. Hugh

The way to push ahead is to note the error and comment out the line causing it with a #
Then when it opens, open halshow (eg. axis menu: show hal configuration)
Then review the pins. You might just have a minor typo. then edit the commented out line to use the correct pin name

Sorry that did not work for you. Seems odd that settings would force a logout/login. we have not experienced that behaviour 

Please note if you log out, its expected you will have to log in again.

roland100 wrote:

Hello PCW,

I hope to get some help from you again.
I tried to make a custom bit file consisting of these two files 7i96s_2pwmd and 7i96sd_mpgp1. 7i96s2pwmd for pwmgen (Stepgen 4-) and 7i96sd_mpgp1 for mpg on P1.
I used the enfinity software, but it doesn't work because of a version conflict.
Do you know which efinty version works with the 7i96s firmware from the homepage ? Thanks a lot

Did you ever get this working? From the description, this sounds like the firmware I need.  Would you mind posting the bin file?

i just tried to replicate your warning, but i was able t stop and make adjustments and report without running into any of those error pop up. those are actually linuxcnc statement stating that your entered parameters would cause an over travel event, are you certain the parameters you entered would be tool paths within the constrained machine motion envelope?

LOL, i feel sorry for the keyboard!
It is hard for now, but after a while everything starts to fall in place and make sense.
Changing one single thing at a time and testing is much more productive and easy to roll back in case of failure.

Lcvette wrote:

what is your machine setup like regarding tool offsets?

My machine overall is a router style setup with a 30 in x 30 in work area. My spoil board is ~24 in x24 in. The spoil board corner is not at (0,0), well inside the machine soft limits. My tool table only has Z offset and Diameter. After probing the corner of the spoil board, the G54 offsets were: X=5.0161, Y=1.1693, and Z=-7.4953. Z probe Z offset is 2.3607 and cutting tool Z offset was 1.8513. 

Very nice, thank you, and also thank you for sharing the files on GitHub.

Moved to "pathpilot" section.

5. NOT step timing: Tested DIRSETUP/DIRHOLD at 2000, 5000, and 10000ns. 5000 was slightly better but didn't solve it.

If changing the step timing changes anything that suggests that something is marginal
electrically or timing wise

Have you tried doubling the step time?

Are the drives step/dir connections single ended or differential?  (single ended is suggested for opto-coupled inputs)

Does the DRO show the error? if not it's most likely not the Trajectory Planner