Advanced Search

I have an external momentary button and i want to toggle between halui.flood.on and halui.flood.off
How can do this config ?

Also i have an output pin that activates lubrication pump and an output pin that activates a solenoid hydraulic valve that releases spindle tool clamp
where in hal must connect it in iocontrol v2 ?

7i80hdt that is not xilinx fpga has the pullup only limitation
or can configured both pullup and pulldown with weak internal resistors ?

Thank you! Yes, everything worked out! Your instructions were easier. I'm trying to design)))

In the ini file, this:
[TRAJ]
COORDINATES = XYZ
Should be
[TRAJ]
COORDINATES = XXYZ

My old system that my machine works on is axis 2.8.0 running on linux mint 19.3 xfce with linux 4.19.106-rt46-lcnc.
My new system LMDE 6 Faye,up X1,joint 0, X2 Joint 1, Y Joint 2, Z joint 3. I will try to attach my ini, file and my Hal. If anyone could help me, I sure would appreciate it. Thank you. Travis

Funny thing is, the Mesa 7c81 and a stacked RPi look like a more compact solution.

NVME would be nice, the RPi5 with a NVME drive is blazingly fast.


Did you stick with the Mesa fpga pin to 7c81 layout ? Or did you change it to make routing easier ?

If you change things around, especially the clock signal, the SPI_CLK for comms is a little tricky to work out to begin with.

Sorry don't mean to add feature creep, man I wish I could design a simple board for the KSZ8851 Ethernet chip for my mesa clone thingy. So hats off to you Old Chap.

I sent a message to your email to purchase one of these boards.
my email - This email address is being protected from spambots. You need JavaScript enabled to view it.

changing LT is incorrect. you should instead rewrite the portion of the macro to correctly wait for the available signal. ie use the correct M66 Pn input so the macro verifies the drawbar is in fact in the correct position.

I have this one, used on my mill with a PC platform: Expensive
Planar Pct 2235 22" 1920X1080 Full HD Touch Screen VGA HDMI DISPLAY PORT USB

For the RPi5: Cheap
www.ebay.com.au/itm/225953008741

I would assume if the touchscreen interface is USB you should be fine. Tho the raspberry pi forums maybe a better resource, just look\ask for usb hid compatible touchscreen, stipulate USB HID is the only option.

I made one for my machine, but i don't recall what was changed.  you can use it as a template to create your own machines requirements and make sure the macros are correctly setup.  the docs explain the different M-codes for DIO.

linuxcnc.org/docs/stable/html/gcode/m-code.html#mcode:m62-m65

linuxcnc.org/docs/stable/html/gcode/m-code.html#mcode:m66

again these are changed to work with my machine and may not completely align with the sim macro requirements:

 

After a couple of hours fiddiling with my vfd to get it working using modbus my pi4 died on me... not really sure what happened it just suddenly went black so i purschased a mini pc witth a celeron j4125 with dual ethernet ports.

Ah, good to know. Thank you for the reply (and for Remora)!

Those are just templates, you need to define and edit for your machines sensors and requirements. My machine uses two sensors one for clamped and one for released because it's only reporting when the plunger is actual at the released or clamped height. If you're have just one sensor that's high or low, than you may need to remove a line from the macro. The best thing to do is to map everything out and then review your sensors and the macro sensor inputs and ensure everything is accounted for.

Hmm.. I see. I checked the clamp tool.ngc? I see that the script waits for the sensor to be high. As I connected the "release" sensor, my sensor is high when the spindle is released and not when the tool is clamped. Could this be the issue?

Does PB use two different scripts for releasing (which works) and clamping (which fails in my case)? Anyway, it looks like I need to invert the value in the script. However, then the debug text in the script should say "(abort, Failed to clamp  tool) ; abort if the sensor does not activate in 2 seconds". Correct?

EDIT: Got it working by changing the LT to GT (waiting for it to be low). Is there a current list about the expected signals in PB? Like ATC drawbar to be connected to motion.digital-out-02, sensor to x, another sensor to y etc.

Then something in your hall isn't correct or in the macro. Maybe the delay time?