Advanced Search

Hello! 
Finally the wiring for the EXE and Mesa that worked for me:
I also dont need a extern  12V supply.

Mesa name  /   EXE Pin and colour
1 QA0         /     9  braun
2 /QA0        /     14 grün
3 GND        /      3 grün-weis
4 QB0         /     1 grau
5 /QB0        /     4 rosa
6 +5V          /     2, 6, 10 grün/braun
7 IDX0        /     7 rot
8 /IDX0       /     15 schwarz

And finally the references work! I only can drive the joints very slowly to find the index. Is there a way to drive faster? The index is only 0.001mm wide. sometimes it wont pick up. 

I also milled the first pices! It works great!



I have already recived the 7i74 und the 7i84U´s for the extentions.
On the weekend i will hook up these so i can use the diffrent gear for the spindle. 

This should be close

 


Note that I had to reduce the number of sserial channels to 3 to fit
(the are also renumbered so channels 0,1,2 are on 7i85 channels 0,1,2)

Most info will still work. The problem is that there is not really consensus about what automatic toolbit offset en height settings must do.
I had mine working for a while. I switched to 3d printing and will pick up later this spring.

Are there any potential drawbacks of this? I've wondered why this wasn't the standard implementation - I figured it was for good reason, so never asked. I ended up dedicating a physical button to activate MDI mode instead, but it feels like a waste of a button...

Will this modification switch back to MDI mode after a python based probing cycle (successful or failed)? I find that's the most frequent time I need to switch back to MDI mode.

Hello,

attached are the requested outputs and I added PDOs and SDOs outputs as well.

When working with multiple m codes, i always use Queue Buster before each m-code.
eg.

M66 E0 L0
M169 P9

M66 E0 L0
M169 P6
 

Is the info in this thread still relevant to QtDragon shipped with 2.9.7? I have a 3-axis cnc router with a manual change spindle and I'm looking to automate bit offset/height setting with a tool setter input on my 7i96s.

Don’t worry, I don’t know how often I intended to attach something and then just didn’t. I asked when I was still having problems with the PnCconf setup, so it is not relevant anymore. But thanks.

Yes, probably you are right... tomorrow next try

without knowing how and what you did its nearly impossible to guess, you appear to have been using multiple different old version to test or try things, so i would almost say for someone at your level your best bet is a clean build fro the ground up to ensure you don't have any remnants remaining that could muck up future progress.

Pretty sure yes... i got it to work now. But the latency of my new system is really really slow. I switch back to the old one. 

Last question for today...
" i would remove everything and reinstall from scratch using apt only, be sure to purge all installations"
what exactly i need to deinstall and which commands in the terminal?

If you measure the voltage across C36 I expect you will find a low voltage
instead of the expected 4.2V. What this likely means is that one or both
bus switch parts (74CBT16211) have been damaged by either ESD
or by being connected live to the G540 with no common ground
existing between the G540 and 7I92T before they were connected,
exposing the bus switches to a transient high voltage.

Hi.
I've added a custom M199 code to enable my  spindle-index-enable signal, and this runs fine. (Can see the LED light up in halshow when run.)
So now I'd like to build it into my M19, so the M99 runs just before the M19 is called.

In the [RS274NGC] section of my INI, I have put
REMAP=M19  modalgroup=7  argspec=RQP ngc=custom_M19
my custom_R19.ngc file contains:-
( Custom spindle orientation ngc file)
( M199 raise spindle-index-enable signal)
o<pre_M19>sub
M5
M199
G4 P2
M19 R#<r> Q#<q> P#<p>
o<pre_M19>endsub

The G4 pause is just so I can be sure that the signal is enabled in halshow gui.

I'm pretty sure the file is being read at Linuxcnc fire up, as when I remove the file from the macros folder, the startup parser errors with missing file.

After I home the machine and run the MDI command say M19 R20, the M199 and the pause are not being executed.

I feel I have missed something really obvious..  be grateful for a steer. Thanks

Did you do a
sudo apt update
before
sudo dpkg -i linuxcnc-uspace_2.9.8_amd64.deb
?

I had a quick look at the config files in the first thread. However, I do think it would be good with the latest files, as well as the classicladder part.

In addition to what I mentioned in the last post, I would also say you should have a look at these signals when you issue an M3 command:
If the physical buttons are not connected to (only) LinuxCNC, then I guess it could very well be something on the hardware side as well. In that case some kind of schematic would also be needed for "remote" troubleshooting.