Advanced Search

We have a very rich and beautiful country, but we still have a lot to develop,

Sounds like a marginal output. This could be a factory defect but
could also be caused by accidental contact of a step/dir wire
to a voltage outside the 0 to 5V range.


You can check the step/dir outputs with this script:

 

(You need to "chmod +x stepgens.txt" to make it executable and
possibly change the IP address in the script)

This will slowly toggle all the step/dir outputs on any Mesa ethernet
FPGA card.

They should swing from 0 to 5V

This does require the latest mesasflash:

github.com/LinuxCNC/mesaflash

 

You remember the episode lol, I was the one who bought thcad, and I had them held up in customs. Thank you very much for doing your best to get the plates to me.

Might be interference issues, use shielded cable for signaling.

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