Advanced Search

ok, I understood that, but how will my axis move if I don't give any speed? it will never detect my plus Z. I can't understand the logic ☺

If there was no communication, LinuxCNC should exit.

Are you saying LinuxCNC is running but you have no activity light
(green LED on 7I92 RJ45)?

What does:

ip a

report when in this state?

Hallo Herr Jansen,

ich habe Ihnen unter This email address is being protected from spambots. You need JavaScript enabled to view it. eine E-Mail gesendet.

Mfg Mario Gnad

Hello, I want to use QtDragon to determine the tool height using Utils - Workpiece and then save the result so that I can access the value in the G-code. My idea was to save the result to a file, which also works by slightly modifying the auto_height.py file. I added the following line:

def show_result(self, data):
        diff = float(data) - float(data)
        self.lineEdit_height.setText(format(diff, '.3f'))
        # New line by me:
        with open('/home/dg/linuxcnc/nc_files/probe_height.txt', 'w') as f: f.write(str(diff))

But how can I access the value stored in the probe_height file in a measurement routine.ngc, or can I save the measured value directly in
the G-coder as a variable, e.g., #5000
 

you need a clock of min. 10Mhz for the ICE4018Mhz clock, not 5Mhz, don't know why


than you need to set the osc value to your new clock speed in
riocore/boards/IceShield/board.json

you can test the spi connection with the rio-test tool:i think to have the gpio commands you need to install WiringPi:
github.com/WiringPi/WiringPi/releases/tag/3.0

sorry, can not test it at the moment

Guten Tag zusammen,wir sind ein Maschinenbauunternehmen aus Norddeutschland und suchen einen Partner, der uns bei der Entwicklung einer CNC-Software für ein Bohr- und Fräszentrum unterstützt. Die Software soll auf LinuxCNC basieren und eine eigene, individuell gestaltete Benutzeroberfläche mit verschieden Features erhalten.Das beauftragte Unternehmen sollte die Erstinbetriebnahme übernehmen und einen langfristigen Support sicherstellen können.
Ein Lastenheft mit den Anforderungen an die Software liegt bereits vor.Bei Interesse an diesem Projekt freue ich mich über Ihre This email address is being protected from spambots. You need JavaScript enabled to view it.

Gruß

Martin Jansen

 

my board is now here too.

I also managed to get the LEDs to flash,
but the FPGA with Vivado is very complicated for me.

In addition, the bridges you have to set on the board are extremely small (R1485 / 25Mhz clock).

somehow it is also possible to clock via PS (ARM-Core),
but I can't get it to run so easily with the console tools

Flashing via JTAG doesn't really work either, I can only write to RAM.

I'll keep playing around with it, but please don't expect RIO integration.

Otherwise the FPGA is cool with its dual-core ARM running Linux
 

This circuit will prevent the spindle direction from changing so long as the spindle is not stopped:
www3.langdonstaab.ca/Spindle%20direction%20circuit.png

(Just an idea)

First off, my apologies for not responding earlier, I've been waiting for my 7i76u to be returned before moving forward plus chores around the homestead have been a hinderance for time.

As Peter said the board was tested and found within specs. Out of an abundance of caution, I ordered as 24 v laptop PS which I received it this morning. After putting it on my scope and monitoring it for several minutes I found only glitches of < .1 v while holding an output voltage of 24.5 v which was the same with the previous PS only at 24.1 v.

Next I reinstalled the MESA board and mapped the X,Y and Z limits to inputs 0,1,2 and the probe to input 4 with EStop on 5. Restarting LCNC with sserial set to 20xxxxxx I monitored the fldvoltage and the four analog inputs. 0,1,2 (the limit switches) reflected the fldvoltage at all times. The probe voltage (input 04) fluctuated wildly between 0-3 v until I grounded the probe plate at which time it matched the other three inputs.

Next step was to reset sserial back to 00xxxxxx and restart LCNC. None of
first four inputs responded as expected.

After shutting down and powering off the machine I remapped X/Y/Z limits, Probe and EStop inputs to inputs 04-08 respectively. After power up and restarting LCNC the Limits and EStop responded as expected, however the Probe on input 07 did not. LCNC sees it as triggered on startup and going low upon contact. OK, shutting down LCNC and changing the HAL file to invert input 07 then restarting pin 07 still responds the same, i.e. high on startup and going low when contact is made.

My next step will be to rewire all of the inputs as sourcing inputs by moving the power legs from the +24v buss to the GND buss, change HAL to reflect the changes and retest.

Taking a break for a couple of hours then I'll let you know of my progress.

Tpm is disabled
Also the device is visible in:
lspci | grep 2718

Good to know, the only thing is that as soon the linuxcnc is open there is no lights activity at the Ethernet port,

Si

New video

I had forgotten that the spindle  ratio setting was not set correctly. I had 8192 in the ini file, the new value is 14700. 

Not sure about pncconf, but LinuxCNC deliberately blocks card access when running.

I'm using 2.9.4

Did you select "Arc Voltage" on the encoder menu on the TB1/TB2 tab?