Advanced Search

ok, if the sim opens and runs fine then this is definitely in your machine configs, go through the doc and make sure what is needed by probe basic is in fact in your files and that the files/folders are in your config directory per the docs!

Gmoccapy support indeed touch screens, but does it support 1024x600 displays?

Hi,
very cool !!!!

for my board without oscillator, i need to run:
```
gpio mode 7 clock
gpio clock 7 5000000
```
to provide a clock signal for the FPGA


for flashing i use this script:
```
riocore/configs/IceShield/spiflash.sh
```
all as root.

LinuxCNC runs as user,
i think i use the normal LinuxCNC RPI image (bookworm)

if you use the default config with:
```
{
"type": "blink",
"pins": {
"led": {
"pin": "LED:G"
}
},
"frequency": 1.0
},
```
on of the LED's have to blink with 1Hz after flashing

to test the connection, you can also use the rio-test tool:
```
bin/rio-test riocore/configs/IceShield/config.json
```

How its connected depends on what the 7I96S is driving.

If the 7I96S is driving a relay with less than 100 mA of current
I would use 7I96S OUT5. Also a relay needs a flyback diode.
This may be included in the torch control switch wiring in
the plasma source.


 

This will only help with Realtek interface.

total cost for 2 assembled boards and 3 spare unpopulated pcbs shipped to Canada was $96CAD, so just under $50/board. Not bad! That goes down with a larger order of course, the assembly fee doesn't really go up much to populate all 5 boards, it's just I didnt want to pay the parts costs if I'd made a mistake and it doesn't work.

I will have to look again. But either way I just need a pinout for the Torch ON/OFF on the mesa board.

 did a little small rework of the IceShield to make it so that JLCPCB can assemble the SMD parts for us, just got them in my hands. I just soldered the through hole components myself, it's pretty easy. I rearranged the connectors so that the routing to the FPGA is a little simpler, because everything has to be on one side of the board if we want the low cost assembly ($7 USD to assemble 5 boards!!! not including components). I used 4 layers for RFI reasons and making it easier to route to power and ground planes with single sided SMD assembly, and the cost to produce the board only increases by $1.50 USD to go to 4 layers.

They arrived yesterday, I plugged it in and was able to flash it using the riocore tooling, but linuxcnc throws bad data warnings with lots of zeros (I assume that's a log of the request data). I have to confirm my CE0 pin is hooked up correctly, that JLCPCB didn't flip the 2v5v dropping diode, and go take a look with a logic analyzer, but I'm wondering if there's some tooling somewhere to interact with the IceShield in a simpler way, perhaps command line? So I can test it without having to run linuxcnc.

The firmware seems to run, because it lights the one LED after it's flashed and rebooted. I have a feeling I have permission issues with the GPIO pins used by the chip select pins, I had to run as root to flash it but linuxcnc isn't happy running as root, something to do with rtapi_app running without a backup uid.  /dev/spidev* are the correct permissions in the spi and gpio group, my user is in that group, but running the flash script as my user fails for permission problems with gpio. That's just linux problems, those I can deal with, just ran out of time. @meister are you running your iceshield on the official linuxcnc pi image? Do you still use it over spi or have you converted yours to an ethernet spi bridge?

Well that I hadn't thought of. I'll be very interested in your results.

you maybe reaching the tolerance that MDF can hold, while MDF is More Stable than other woods it still changes shape massively compared to metals and some plastics. i will try to run some holes on my phantom s4. it does many small move like your, I suspect I will get the similar results as you. that would mean tool deflection and/or material movement

tommylight wrote:

See the included spindle "orient" component, might do what you need.

I saw it before, but not really understand how to use it with a VFD (mesa 7i96s analog output generated with the PncConf) and with one fake encoder.

Compress the entire machine config and attach if here. It's really impossible to do more in depth troubleshooting without seeing all the files.

Also try to uncomment one of those lines at a time and see when the bug appears again.

mBender wrote:

Hi all,

I am trying to get my hands around this. Played around with the Docker container a bit. I have so many questions...

I think it would make sense if we collect for the Boards to have a sample config file. E.G. I just ordered the Colorlight5A 75E and will set up a simple milling machine with stepper motors. What do you think?

Either way, if someone could share a running json file with me, that would give me a head start.

I will add to the documentation to make it easier for further users to get started.

yeah I'll share my working setup once I get everything where I want it.

You are welcomed, always.
Also see this about the multiple network icons:
forum.linuxcnc.org/38-general-linuxcnc-q...little-issues#226480

Good afternoon everyone

Can you please help me with how to configure the Z axis drive and recognize the THCAD2 as an encoder? I have tried several times without success.

 

When trying to move the axis, an error appears calculating the movement of the Z axis.

 

This is the INI file type configuration

 

this is the HAL type file configuration

Please, can someone guide me?

INI and HAl files attached