Advanced Search

meister wrote:

i prefer the WT32-ETH01, cheap and available

Understood, thanks for the advice/heads up. I have placed an order for the WT32-ETH01 and will receive this within 36~48hrs. I'll update. 

As important; For your review and consideration, Oliver.  I've quickly re-wrote a w5500 UDP protocol driver featuring a robust state machine and both a soft & hard reset (set on hard rst atm - preference). The SPI is a high-performance 50meg judging from the initial tests carried (see attached Gowin project/ZIP file). Additionally, please pardon my arrogance and persistence in trying to get this w5500 badboy to work; the reasoning behind is not fueled by my potential $1.99 investment losses (lol) I assure you, but more or less by the enthusiasm of that wizzy part being as simplistic as they come - let alone a ridiculously low-cost BOM and beyond ease for hardware implementation. All good reasons if RIO is to be adopted by makers like myself (iThink). 

You guessed; I wouldn't know where to begin neither would know how to implement this into RIOCore. Therefore I leave it to you to investigate that possibility (or feasibility rather).




 

That is nice that they used switches. Schaublin embeded Hall sensors into the bed of the 125-CNC. I hope they dont fail.

That makes sense.

Nice work.

I downsize pictures to 1000 pixels on the long side before uploading them.

Hello 
Can anyone share remora pinouts for nvem RT1052 board? 
I'm trying to set limit switches by adding :

net X-min remora.input.00 => joint.0.home-sw-in joint.0.neg-lim-sw-innet Y-min remora.input.02 => joint.1.home-sw-in joint.1.neg-lim-sw-innet Z-min remora.input.04 => joint.2.home-sw-in joint.2.neg-lim-sw-in

To my hal, but without proper pinout diagram I'm not sure which pin is for remora.input.00 etc. 
I've tried by connecting like on drawing in attachment, unfortunately without success.
Also is estop and probe pin counted as a inputs or separately? 

Dear All,

Figured it out with extended reading - thanks for this great forum! - and a bit of creative try-and-error.
All 3 axes are set up and calibrated, homing works like a charm
Next and last open issue is the spindle - but I don't expect much difficulty with that. Otherwise there'll be another post here ...

ORIGINAL POST:
I've started a project to convert a 30-year-old engraving machine (Gravograph UNICA) to LinuxCNC running on a Raspberry PI 4 with a MESA 7C80. I have several Gravograph machines of various sizes available and am looking to roll out my conversion to most of them, if it works out as planned. These machines may be old, but as such they're solid and reliable. Also they are simple as there's just one stepper and one limit switch per axis and the spindle motor to control. The main reason for conversion is that the UNICA machine only runs on it's own Gravograph-unique operating system with a tiny monochrome CRT screen and propietary keyboard, with no communication port. The other, larger machines can communicate via serial port, but they also require Gravograph-only software ...

So far, I got the Raspberry PI, 7C80 and LinuxCNC up and running to the point that the x-axis stepper is operational by using linuxcnc.hal and linuxcnc.ini from this thread:
forum.linuxcnc.org/42-deutsch/52725-3-ac...esa-7c80-und-raspi-4

As far as I can tell, there's no wizard available (stepconf etc.) for configuring the MESA 7C80, so I need to work with the config files directly(?)

I modified linuxcnc.ini so that the stepper runs smoothly, and added three lines for the limit switch and homing. The stepper now starts running when I home the machine in LinuxCNC, and the program is apparently waiting for the limit switch to be triggered.
This is where I'm currently insecure and would like to ask for assistance:

• What terminals to connect the limit switch to at the 7C80?
• How to set it up as a NC contact (Switch opens when x-axis home position is reached)?
• How to set up homing to move the spindle towards home at first if the home switch is not triggered, and then move a short distance away and back to the final home position? 
  
  This is my current linuxcnc.ini:
   

  File Attachment:

  File Name: linuxcnc.ini
  File Size:4 KB
  
   
  Thank you for reading and thanks in advance for any answers!
  
  Best regards,
  Erik 
  captain-panda

Yeah it seems that way.

More reading required. I've got a evaluation board on the way an old Diligent Spartan 3AN. So rather than trying to take everything at once I'll have a chance to "do little bits at a time". And not bother you so much
 
Thanks

Very nice! Congratulations.
How do you set the feed rate? Is there a feed rate override function built in?

I don't want the count - I want pulse + direction so I can combine decoded pulses from the quadrature encoder/MPG with pulses from other sources.

You seem to have a lot going on there.
First thing I would suggest is to simplify things by choosing which jog method you actually want to use and then test this method in the 'Halshow' tool without all the connections in your hal.
For example this situation should jog the x-axis:

 

Alternatively this should also jog your x axis:
 


Also, posting your hal and ini files might give us a better idea of what you have going on.

Hi Becksvill,

Thank you !

I made a short video how it runs on the boomerang gcode file, i enabled using the scurve velocity ends in the kernel code :


I think it run's quite good for a first test.

I removed the boomerang preview (released opencascade memory), to get the gui more responsive. I made a button for this.
During screen recording, the gui even becomes slower.

Removing the boomerang preview works great, however i am thinking when running huge files, to show only a certain portion of the
gcode file.
Like 100 lines before and 100 lines after the current executed gcode line.

Furthermore i can optimize the opencascade memory, to show a memory efficient shape, like a memory efficient linestrip over the path,
this then for huge files like >10000 lines.



 

Cant do this anymore bye all wrote:

I was just throwing it out there.
In all honesty it really doesn't go with the ethos of your project. From the beginning you wanted to stay away from softcores.
Just while I have it on my mind;

i have no problem with discarding initial concepts if it brings an advantage, unfortunately i still see disadvantages in softcore.

Cant do this anymore bye all wrote:

reg [5:0] initialization_progress = 6'b000000;

More code......

[code]end else if (state == STATE_INITIALIZING) begin
spi_clk <= 1'b0;
state <= STATE_SENDING_COMMAND;
initialization_progress <= initialization_progress + 6'b000001;
spi_chip_select_n <= 1'b0;
spi_clock_count <= 10'd0;
is_busy <= 1'b1;

case (initialization_progress)
// TODO: Perhaps add software reset here?

0: current_instruction <= SET_PHY_MODE;

// Set our MAC address
1: current_instruction <= {SET_MAC_ADDRESS_BYTE_0, MAC_ADDR[47:40]};
2: current_instruction <= {SET_MAC_ADDRESS_BYTE_1, MAC_ADDR[39:32]};
3: current_instruction <= {SET_MAC_ADDRESS_BYTE_2, MAC_ADDR[31:24]};
4: current_instruction <= {SET_MAC_ADDRESS_BYTE_3, MAC_ADDR[23:16]};
5: current_instruction <= {SET_MAC_ADDRESS_BYTE_4, MAC_ADDR[15:8]};
6: current_instruction <= {SET_MAC_ADDRESS_BYTE_5, MAC_ADDR[7:0]};

Am I right in thinking that SET_PHY_MODE is never acted on as initialization_progress is incremented before the case stanza ?

[/code]

you must not look at it as a programmer

this is verilog logic, not serial programming.
Everything runs in parallel

that:and this:is executed at the same time and therefore the value in the 'case' is still 0 and only in the next 'always
verilog can be a real brainfuck

1600-1603 1A00-1A03

Thanks Scottlaird,
Please receive xml file exported from lcec_configgen command.
I do not think I can use content from this file
 
I have idea to use modules in one CiA402 as this file
I am not sure it is the best optimization, please advise.
 
In other hand, can you share your xml of 2 and 6 axis device ?.
Thank you.

Custom kinematics written in C can be found in 'src/emc/kinematics'
github.com/LinuxCNC/linuxcnc/tree/master/src/emc/kinematics

Generally I would suggest to write custom kinematics as a component (.comp). Unless of course you have a compelling reason to use C (and know it well enough). See examples like github.com/LinuxCNC/linuxcnc/blob/master...onents/millturn.comp
or the more complex
github.com/LinuxCNC/linuxcnc/blob/master.../xyzab_tdr_kins.comp

For the latter there is a paper with documentation:
forum.linuxcnc.org/10-advanced-configura...mill?start=80#263694

[edit]
to compile and install a custom kinematic file:
halcompile --install <path/your_component.comp>

(prepend 'sudo' if you are on a package install):