Advanced Search

The 7I96S_7I77 configuration moves the 7I96S encoder to encoder 6 (and aliased encoder 7)
This was done to be compatible with 7I77 configurations that expect the 7I77 encoders
to be encoder numbers 0..5

Note that you need to set num_encoders=8 (or leave the num_encoders
out entirely) to access encoder 6

 

THANKS I increased the Z travel distance to 7" and that seems to have cured the problems. I did not get the errors and I an repeat the surface detection over again with out a error too.

tommylight wrote:

Not the same drives, pretty sure, this one is step/dir only, the above is analog only.

The manual is not for those drives as stated above, it is for something similar but new-ish.
The picture of his actual machine shows wiring and labeling for analog +-10V control, and so does the first PDF with the machine wiring schematics.

Grotius, thank you for you interest in this subject. 20ms is not bad for a component such as halui, the problem is mainly to do with timing, since it runs in user space its execution time is unpredictable. Now when you connect halui to hal components (realtime components) configuring becomes difficult. When I configure hal logic I rely on experience and intuition, if I encounter an execution problem I correct it by setting he proper execution order of the components. But with halui the execution time is unpredictable. Configuring mix of hal and halui is a pita.
If you have chance have a look at simple logic such as  run/step pause resume logic and you will see that its not easy to configure such simple logic. If the same configuration was done with halui running in realtime that configuration would be much simpler to create and behavior will be predictable and repeatable. 

In nutshell halui running in user space its execution time is unpredictable. 

Since I am not C++ & RTOS programmer. I am hopping that someone from the community with those skills would try convert (probably no the proper word) halui from user space to realtime space. It's probably a lengthy process. I will be more than happy to help with the testing.

Thanks again Ben

In a "switchkins" XYZABC" serial link machine...

If all the joints are defined angular, do I set Max_Velocity or Max_Angular_Velocity under [JOINT#] ?  Or is it sufficient to only set under [TRAJ] ? Same for [TRAJ] do I set Max_Velocity, Max_Angular_Velocity or both?

I'm thinking I need to set the values at the [JOINT#] level to handle the various gear ratios.

What would you recomend?

I have never used clasicladder, but i always use Axis, PlasmaC and QtPlasmaC.
Gathering some stuff to build a mill, so might start using QtDragon or QtPyVCP, no idea when though.
-
Rant
Been 8 days since i got delivery of 410W solar panels, they are still inside the house...

What GUI do you intend to use?
Axis should work, mostly, and there are some made specifically for small screens, like:
www.forum.linuxcnc.org/21-axis/38188-axi...reen-with-qtvcp-tabs
forum.linuxcnc.org/forum/41-guis/26174-s...signs?start=20#61123

You have 1 encoder on Mesa 7i96S and 6 more on Mesa 7i77, so you can use any of those for THCAD.
The issue of it not working might be changed encoder number in hal in the firmware, so use the "show hal configuration" from the "machine" menu to check what number is assigned to Mesa 7i96S encoder, should be 0 or 6.

That is not an error, it is just a warning about older style cards and you can ignore it.

After you select the Boardname and the appropriate Firmware on the Mesa Card 0 page you need to click "Accept Component Changes" which will load all the details for that particular card.

First up i am apologizing for the silly thing that i have missed or dont yet understand but i hope i have tried.  

I have my Probe basic (now will be previous stable on 2.9.3) setup mostly working for what i wanted with Pendant etc.. but wanted to customize the physical buttons that i have for start / resume, Step / feed hold and well stop works fine.

(Currently 7i76 with physical buttons mapped through to the following
I started with forum.linuxcnc.org/47-hal-examples/13201...ume-buttons?start=40 and thought that i would like to have it when i press the start button and the system is in a feed hold state to resume.  So first part was to change from the single mapping to using an And to only allow start to happen when idle. (I know that is how the above cycle-start works but i was trying to do it to just prove i could get it working)
#Mapped physical button with no issues to one leg of And
net my-start-resume-button-in1 and2.pause-resume-0.in0 <= hm2_7i76e.0.7i76.0.0.input-07
#Then when trying to map one of the existing pins / signals is where  i get all screwed up.  
net my-start-resume-button-in2 and2.pause-resume-0.in1 <=  halui.program.is-idle

I thought that read as the following Netname = my-start-resume-button-in2, name of signal wire to set and2.pause-resume-0.in1 (the 2nd leg of the And), The trigger signal = halui.program.is-idle 
Instead of that working (Knowing i have no output yet) i get the following error.
custom_postgui.hal:67: Pin 'halui.program.is-idle' was already linked to signal 'prog-running'

So i was well lets change the trigger to be prog.running and see what happens then.
#net my-start-resume-button-in2 and2.pause-resume-0.in1 <=  prog.running
#.../custom_postgui.hal:68: Pin 'prog.running' does not exist (I can see that prog.running is a signal not pin but i am then back to confused about how to do the 2nd part of the and)

Then i was trying to even take the output of the and to trigger 'cycle-start'
net my-start cycle-start <= and2.pause-resume-0.out
#.../custom_postgui.hal:75: Pin 'cycle-start' does not exist

i hope that i am so close but yet so far.  (The reason that i posted this in the Probe basic is my aim is to use qtpvcp.feed-override.reset to remove from feed hold (I hope that is the correct way))
Thank you for reading this far and hoping someone can fix my broken understanding.  Full code block of what i was trying to do below with no extra typing.

Okay, Thankyou. That is actually what I did first but then wasnt sure, so I tried rerunning them seperatated by the | symbols. I'm going to delete the configs and redo.

Jim

Hi Tom the picture Matin  shows in the previous message is not for the servo drives. I open his servo drive manual and it indicates that the drives are step direction. Here is snap shot of the drive schematic. My advice is to hold on before he makes purchase of an analog messa card. 





 

You have to run the command in the main terminal line by line. So 4 commands in total.

Just to clarify.

The directions say: Run the following commands in the main terminal one at a time:

sudo apt install curl
echo 'deb [arch=amd64] repository.qtpyvcp.com/apt stable main' | sudo tee /etc/apt/sources.list.d/kcjengr.list
curl -sS repository.qtpyvcp.com/repo/kcjengr.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/kcjengr.gpg
gpg --keyserver keys.openpgp.org --recv-key 2DEC041F290DF85A
Im not certain what the individual commands are. It's probably obvious to most... but I'm very very new to LinuxCNC

Hi,

I just re-installed my Debian as I messed something up with my system config. I saved my Linuxcnc config so I just needed to reinstall and put back my config. So far, everything worked except for the Probe Basic GUI that is missing a few buttons.

In the lower left, I noticed a few buttons missing (run from line, Flood mist etc). I first used the APT Stable install and then switched to the develop branch but I have the same issue.

Does anyone know how to fix this?