Advanced Search

Bevor ich das vergesse, der Treiber ist zurück gegangen. Modbus wurde versprochen, aber ist quasi nicht nztzbar. Es wurde etwas in die Firmware des Treiber gebaut, damit konnte man ein wenig lesen und auch etwas schreiben, aber wirklich Modbus ist es nicht. Das was in der Beschreibung versprochen wurde, konnte definitief nicht gehalten werden. Ein anderer Händler hatte dann wenigstens zugegeben, das damit angeblich speed Modus möglich wäre, aber position funktionniert nicht.

same advise as above, follow how the pb launchers are working and do the same thing for your vcp1, they are calling scripts and will require the terminal be in venv mode and the scripts pointing to the correct files.

the existing atc macros are designed for dumb motor carousel operation. if you are using the carousel.comp component, you would need to follow the components setup instructions and integrate into the macros or build new macros based on your machines mechanical configuration. you could use the existing macros as a template for the qml graphics connections.

Thanks for the insight. I'll do some testing outside of pncconf once I get all the stepper drivers installed.

Hi,

Thank you for your time and response. I think the UI polls data from the STATUS data. Probably, if a signal is only high fraction of a second, the UI might not refresh quickly to show that. But I think the underlying logic in HAL is catching all states. 

I just run linuxcnc with debug and verbose output from the terminal, but nothing other than the latch return error is printed to the console during the issue  .

Hello,

Thank you for your efforts, I thought I was the only one.
But I did not pursue this further due to time constraints, especially since no further reactions were made to my post.
The switching states are displayed properly on my mesa card. However, if I quickly press my mesa card in a row, the mesa card reacts correctly, but the LED in QT_DRAGON_HD sometimes does not react as expected.
Possibly a timing problem with signal processing.
I have a flying button that measures both workpiece and tool length. Workpiece height is the built -in routine and tool length and change your own, but that makes no difference.

Many greetings Frank.

What do you have selected to enable the spindle?

Typically you need one output for single direction spindles 
and two for reversible spindles.

On a 7I96S, in hal, these would normally connect to the isolated
outputs on TB3, which in turn need to be wired to appropriate
VFD control pins.

Discovery is an option in the board name menu:


 


Then:


 


Next setup the card name and communication details:


 


This shows the additional stepgens, encoders and PWMgens after discovery
Using 7i96s_5abob. bin firmware on the 7I96S:


 




 

Use the serial monitor feature to see if the ESP is connected and working.
Use ping to make sure network is set up properly, ping the W5500 on the address you set in PlatformIO/Code

My tool setter in NC , probe is NO.
So I'm using the remora.input11.not to invert the pin. But that dosnt seem to work with or 2.0.
When I use the normal remora.input.11 pin the prob works as it should triggering the motion.probe signal. Tool setter when pressed triggers only the or2 in. 

Addf or2.0 servo-thread
Net toolsetter remora.input.11.not or2.0.in0
Net Probe_tool remora.input.12 
or2.0.in1
Net probes or 2.0.out motion.probe-input

Is there a way to get this to work other than a relay

^^^^ I got this to work with classic ladder

Hey all, 

I've got a Bridgeport BTC-1 milling machine, controlled by an old Dell Optiplex 755 and a Mesa 5125 card. The 5125 card connects to a Mesa 7177 card with a parallel port cable. It is in a barn without AC, and it seems the Dell is the weakpoint. It often breaks, probably due to the heat and humidity. I can get new ones for about $80 on Ebay, but would prefer to have a more permanent solution.

Can anyone recommend a good computer for this application that wont' break the bank?

Thanks, 
-Hunter Long

I don't know, with the latest Windows 11 update screwing up SSD's and such " Artificial Incompetence " may
be Windows epitaph.

Ok thanks for the tip. I tried to setup the spindle via pncconf but it didn't run. I have a screenshot below of what I tried. In the TB1/TB2 tab I selected spindle PWM as you can see. Is this the wrong place to setup the spindle?

Thanks for the reply PCW. I was going through pncconfs and I couldn't find anything like discovery(Im new to LinuxCNC). While going through pncconfs I was a little confused because I flashed the 7i96s_5abobd.bin file but I couldn't find this as an option in pncconf as you can see in the image below. Anyways, I tried all three of the options that were there and none of them gave me the option of adding the BoB. Thank you for your help

Hi,

I'm trying to get my toolsetter to work, but i'm running into "Probe tripped during non-probe move" just as the probe is tripped. I've been though a lot of the usual stuff i found on the forum, like electrical noise, debouncing and so on....I'm fairly new to gcode, macros and stuff, so bear with me on this...

I'm using all the standard stuff that comes with Probe Basic, but looking at the "default" tool-touch-off macro here: 
github.com/kcjengr/probe_basic/blob/0490...ol_touch_off.ngc#L59
(And again later in line 69 with the slow probe retract)

I think that this G1-move might be the one causing my issue? I'm trying to understand why this isn't a G38.5 move instead? Then it would be a probe-movement which allows the probe to be triggered while moving...at least as far as i've understod...or maybe a combination of a G38.5 first and then a G1 move, since G38.5 stops after untripping the probe per the documentation...am i completely off here?

I've been really hesitant to post this, because a lot of people use this macro(i guess?) and i assume it work for all of these people, so chances are very high that I'm mistaken and something else is going on...

Any input will be highly appreciated! Thanks!

/Thomas