Advanced Search

I just used the free output instead of the one I used for the X by changing the parameters on the existing configuration file. The error disappeared and everything is perfect again, so I have a problem on exit 0 of the Mesa... This thing doesn't make me happy at all.

Because the 7I96S RS-485 interface is 6 pins of TB2 (15 .. 20)
and has a 6 pin connector.
 

Why 6 pin?
and is it TB2 pin 15,16,17,18,19,20 or pin 15 and pin 20 ?

please elaborate a little bit further

 

Hi all,

The problem:
I probed distance from machine Z=0 to the tool setter trip point (G90 G53 G0 Z0, then Z probe, result=4.5xxx). I set Spindle Zero to this value plus the measured length of my master tool (4.000), total 8.5xxx. Then with the master tool still in the spindle, I added a new tool number to the tool table (all zeros, saved & reloaded), loaded this number in the spindle, and did Touch Off Current Tool. I would expect to get the measured length of my master tool in the tool table, but I consistently get 4.038x".

The 0.038x" error is not reflected in the machine Z when I jog down and barely trip the tool setter with the master tool. From Z=0, I get a negative Z value that precisely matches the probed height I used to set the Spindle Zero. My tool setter speeds are set the same as my probe speeds. I cancelled or zeroed offsets and this didn't make a difference. My tool setter is a base-mounted Renishaw MP1s, and it repeats to within a couple of tenths using the Z probing routine. I'm running a PB "stable" install from the github repo on bookworm.

What am I missing? Any ideas what could cause this offset? I was on Discord last night (for the first time) looking for help with this and chatted with a couple of folks (thanks if you were in that group). Someone mentioned that a new release of PB was imminent. From something I read recently I understand the tool setter is changing quite a bit, going away from using G59.3 (IIRC)? If this problem is likely to go away as soon as I upgrade, please let me know.

I got the tool setter working after finding the docs for the new PB version, with the new pictures showing what the tool setter values mean. I also watched videos including a couple by Small Shop Concepts. I followed almost the same setup procedure for setting Spindle Zero as the video, but instead of probing the spindle itself, I used a "master tool" I set up that is a known length (4.000").

My Hurco KM3 has a Kwik-Switch 200 spindle, and the gage line is at a specific diameter of the taper. It isn't a surface you can readily probe, and there aren't any good alternatives because the spindle nut encloses the whole bottom of the spindle. I used a spindle probe turned upside-down on the table (in a KS200-300 adapter) and some trig to measure the spindle taper and figure out where the gage line is vs. machine Z=0. Then I iteratively adjusted my master tool length until it measured dead-on. But the master tool length, it turns out, is irrelevant. The problem I have could be demonstrated with any length tool.

I'm *really* enjoying using the GUI with my new 22" touch-screen monitor. My Hurco hadn't been upgraded for a long time, and I needed a newer PC to run a current OS, which also meant a new Mesa ethernet-based control board. Big thanks to everybody who helped develop PB!

Chris

It may be fixable but hard to say without further testing

OK if all I/O are high on power up and low after the mesaflash commands,
that means All P1 I/O bits are functional. so it's not likely a hardware issue.

Maybe the next step is to verify that you can do a loopback through the P2
RS-485 port.

 

 (you will need to "chmod +x echo.txt" to run it)

Will check if the 7I96S RS-485 hardware is OK

It requires a simple 6 pin loopback plug with TX+ connected to RX+ and TX- connected to RX-

When the plug is not inserted,  the expected result is
0000EFFF
00002FFF
00006FFF
 When the loopback plug is inserted (TB2 pins pin 15..20), the expected result is
0000EFFF
00000FFF
00006FFF




 

Thank you for the suggestion, i have edited the initial post and added some photos and changed everything to be a bit clearer about the machine as a whole. I will add some more photos as i am progressing with modifing it.

If you just want to check for any motion, there is 'motion.current-vel' it is OUT FLOAT, i think you can use COMP for float to bit

OK! with adress 0x1008 and 0x1108 all gpio are low

sorry, its

2. Then set all GPIO pins on P1 low by:

mesaflash --device 7i96s --addr [ipaddr]  --wpo 0x1008=0
mesaflash --device 7i96s --addr [ipaddr]  --wpo 0x1108=0xFFFFF

 

Have a look at these:

 

www.linuxcnc.org/docs/html/man/man9/motion.9.html

post powercycle:

0 / 5     this is the side where GND and VCC are attached to the board
0 / 5    
0 / 5    
0 / 5
0 / 5
0 / 5
0 / 5
0 / 5
0 / 5
5 / 5
5 / 5
5 / 5
5 / 5  this is the side where the  ETH PHY is mounted

all pins low except top-right after the commands

I made this Arduino based push-button display gizmo that is mounted at eye level on the front of my mill.

When in jog mode the display has enough room to display the feed and jog rates (left image).

When in MDI mode the display is cluttered with "soft" buttons for MDI entry so not enough room to display the feed and jog rates (right image).

Want I want to do is while in MDI edit mode, hide the feed speed (as shown), however as soon as the enter key is hit to initiate motion I want to display the feed speed,  basically hide the G3, G3  soft key row and instead display feed speed in that location only while in motion.

So I need a halui pin/signal that will be active whenever there is motion to enable the dynamic speed display.

Any suggestions as to the best signal to use?
 

I Solved it! Holy cow! it was crazy simple.  So here's the lowdown of what needed to happen.  The ngc in the remap had to be lowercase.  That's it.  I had no idea that you couldn't use an upper case ngc name when remapping.  Is this a bug or it's supposed to be that way?  Goodness that would have saved me about a year of challenge. 

I believe Andy has a more elegant solution using pure python as: index_lathe_tool_with_wear but I can't write in python so I was in too deep.  
So here's my road to success with T.   Paths and directories are very important and you need to pay attention to where your python and subroutine code lives (mine is home/jake/linuxcnc/python, and ./) respectively.
Since I had already put together a M6 remap it got pretty tricky with what to do.  I kept thinking that remapping with the fanucy lathe example was creating a circular loop but it wasn't. 
My turret has a closed loop stepper with fault output an air cylinder to lock/unlock the turret, an index, and a inductive sensor to see if the hirth joint is locked.  With that my m6 remap ngc just goes through and rotates the stepper motor as joint 2/axis A and I scaled everything so that one tool pocket is equal to one unit on A. ex: T0=A0 T1=A1.0 T4=A4.0  It has an exit if the stepper is faulted for whatever reason, or the turret hirth fails to lock.  The downside to using this method and not a carosel component is that g30 causes the A axis to want to go home so use G28 instead. In the end I leave the remapped M6 alone.
Next up was making sure the remap.py in the python directory had the remap.py with has an added"get_t_number" from the fanucy_lathe example config. 
Also make sure you've got stdglue.py and toplevel.py in that same directory.  
Modify your ini file to remap T using the prolog=get_t_number and then this is where I made the fatal mistake I named an ngc Ttotool.ngc
(I always got this weird error "file not open" with that name)  the name ended up ttotool.ngc and it worked perfectly.
Next make sure you copy the toolchange.ngc that's called out in the lathe_fanucy example remap T but rename it with the exact subroutine you plan on having in your subroutine directory.  MAKE SURE IT IS ALL LOWERCASE. 
Remapped T should theoretically work after you complete these steps.  If you get issues with python crashes, just go through the remap linuxcnc.org/docs/devel/html/remap/remap.html and reimport the python directories and try again editinging with the lathe_fanucy python changes.  
Good luck. 

After following the advice from tommylight and downloading and installing the files in that order did in fact work , the names aren't the same but i will post the files that worked for me .

After downloading i wasn't able to install by the GUI Package Installer , so i used the cmd :

the same for the rest of the files , after that is just to continuing to follow the tutorial from this link and it will be done.
Thanks to tommylight and rodw for the continuos help.