Advanced Search

Update.  Want to post this before I bothered anyone with a response.  Was able to get connected.  I had 7i92 instead of 7i96. Obviously this was the problem.  I will post again when and if I hit the next sang.  Thank you. 

I'd like to report an experience I had with too-short timings.

All of my software/hardware is circa 2012 but mostly not used until now. I am using a g540 and 5i25 running hostmot2 from LinuxCNC.

I was using:

DIRSETUP = 2000
DIRHOLD = 2000
STEPLEN = 1500
STEPSPACE = 2500

With these settings, at very low velocities I was losing steps. I actually thought I had a backlash problem for some time. However, I eventually accidentally tried jogging at extremely low speed and noticed nothing happened at all, and after some time my position was significantly off from what LinuxCNC displayed.

Based on another thread here, I tried some more conservative timings:

DIRSETUP = 2000
DIRHOLD = 2000
STEPLEN = 5000
STEPSPACE = 5000

With these settings, my problems are gone. So if you are running at very tight settings, I recommend you try jogging at extremely low velocity and see if you get into a mode where the axis does not move, just in case you encounter the same problem.

If you are using the 7I73 input for a limit switch, I would debounce it.

Also why are you not using 7I96S isolated input for the limits? These are more resistant to EMI
and have built in debouncing (set the inm "slow" attribute for the corresponding inm input pin)
 

Ich habe in der axis_mm.ini geschaut. Dort gibt es kein JOINT_0, JOINT_1 usw.
 

Hi rod, thank you for your help. 
I manually tried both switch and they are working well. Here is what I don't understand :

If I manually push on one limit switch, my signal joint.0.pos.lim.sw in become high,I get the joint error, then the tickbox "override limit" which is normally greyed out become available 

But when I don't manually push the limit switch, bot signal pos and neg lim sw are low, the tickbox is still greyed out and I get the error. 
So I'm not sure my error is linked to the limit switch. And my homing routine works fine with a first rough touch, then a second fine touch and then come back 10mm. 

mBender wrote:

digiex_chris wrote:

Zayoo wrote:

Only thing hire is missing one good in depth help file!  
Anyone can open a PR with updated documentation!
 

I stared to use the Github Wiki. If that's the way of moving forward with the documentation, I am happy to help. Here is a simple example. github.com/xsnoopy/riocore/wiki/BitIn
 

the problem with your test page is that the plugin readme's are all generated from the source code,
so they are always up to date and the text is also visable in rio-setup.

A kind of tips&tricks page would be cool for a wiki or installation instructions, for example

If someone wants to describe the plugins better, you can do that in plugin.py, e.g. here:

github.com/multigcs/riocore/blob/dev/rio...ns/bitcopy/plugin.py

than you can update the readme.md with:
 

rodw wrote:

Finally! you decide to follow the solution from the first reply you received in this thread!
 

Take better pictures.

Hi,  

I am back.  I got very busy and got sick and have just now been able to get to the software side of things.  I added a picture of the pumps I am using because that is kind of fun. 

But I am having trouble connecting to my board using Mesaflash. It seems like this is not an uncommon problem for people to have, but despite reading the multiple forum post about this issue I am unable to find a solution that works for me.  I am getting the error "No **** board found" I have tried every board name I can think of but nothing is working.  I currently have a 7i96s and a 7i85s linked together, so I assume the board name is a combination of these two.  There doesn't seem to be a way to see what board is connected.. 

A note about the 7i85s.  At one point I had 6 drivers connected to my machine, which is why I needed the 7i85s.  However, I am no longer using all the boards.  One of my drivers is still connected to the 7i85s but I can move it to the 7i96s.  I am saying all this because I am assuming that the new firmware (the 7i96s_pmd.bin) will not work with the 7i85s connected. I am assuming this because of the name.. 

Anyway.  Can someone please help me figure out how to get in communication with the board I have.  I am talking to it through an ethernet cable, I don't know how to tell the terminal that that is how I am communicating though.. I have tried both 10.10.10.10 and 192.168.1.121.  
 

Start at the beginning and test every step progressively.
1. If you get an error finishing read, all inputs are disabled. 
2. Confirm with a multimeter that the wiring is correct and you can see voltage changes at the Mesa input
3. Confirm that your hal file is referencing the  pin you have connected your wire to in halshow
4. Check all pins in halshow for activity when the switch is activated in case you have wired it to the wrong input

It is so easy to wire things up wrong so it's important to follow a step by step approach to trouble shoot issues.

With qtdragon I have blank toolpath screen, but it only appearing when exit prompt appear.
I tried with fkms,kms -pi5 etc but without results, regular axis display working correctly.

digiex_chris wrote:

Zayoo wrote:

Only thing hire is missing one good in depth help file!  
Anyone can open a PR with updated documentation!
 

I stared to use the Github Wiki. If that's the way of moving forward with the documentation, I am happy to help. Here is a simple example. github.com/xsnoopy/riocore/wiki/BitIn

Finally! you decide to follow the solution from the first reply you received in this thread!

 

cool new feature/plugin:

github.com/multigcs/riocore/tree/dev/riocore/plugins/bitcopy

@TntMold, @sockheavan,
Please follow this sticky if you repositories are not installing
forum.linuxcnc.org/ethercat/53785-instal...thercat-repositories

Unfortunately, there are licencing and legal implications that prevent Linuxcnc from doing what Grotius did.
If the developers do not deploy the changes to the ISO I have made on my request, These issues will continue.