Advanced Search

mooser wrote:

That's what I normally use but ones that are small enough for 28g wire are a little scarce around here.
I've got 100 26g on order but I don't like trying to double them over to make it large enough to crimp securely, seem to put a lot of faith in that spot where it comes out of the insulation

For now I'm seriously looking at trying this, actually seems to have a really good grip.. in theory it should have at least a decent electrical contact...

Ferrules come in smaller sizes than the 0.5mm^2 white one.
www.efixx.co.uk/Know%20How/ferrules
Look for a 0.25 or 0.34mm^2  ones. I found them on Amazon 
www.amazon.com.au/Hanibos-Ferrules-Cable...n/dp/B0CHFP7RGC?th=1

I didn't know the smaller sizes were available either!


 

Everything in Linux is case sensitive, or i just can not think of anything that is not right now.
Edit:
You can add two lines for upper and lower case each, removes the need to keep track of how it was saved.

Never occurred to me that it would be case sensitive.... My Mastercam is set to spits everything out in unppercase including the extension.
Many thanks for making me look at it again.

That's what I normally use but ones that are small enough for 28g wire are a little scarce around here.
I've got 100 26g on order but I don't like trying to double them over to make it large enough to crimp securely, seem to put a lot of faith in that spot where it comes out of the insulation

For now I'm seriously looking at trying this, actually seems to have a really good grip.. in theory it should have at least a decent electrical contact...

Well done, andrax.

There are two homing methods
1. Linuxcnc normal homing. Google "linuxcnc homing" and you will find an article incl illustrative figures describing this. 
2. Ethercat homing. Many people have used it, I have not so can't advise on that.
I propose you start with 1. You can always do 2. later on.
I actually think you are doing 1. and want to use one of the digital inputs as X homing switch. 
The signal you have made looks ok. Just check that din-4 is a general purpose switch, not tied to ethercat homing.
Use the halshow utility to follow/watch pins to make sure they react the way you want.
 

Thank you for the reply. Will try to get something to work. 

Thinking about using Delta C2000 VFD.

I am away from the code for at least one more day. I'll give you some clues for now and give a more precise answer when I am back.
You *must* set up spi. The other pins are set up as needed. Use free-run mode and you don't need them.

Spi is setup using stm32duino standard spi functions.
Somewhere in lib/soes c or h file (also check subdirectories to lib/soes) there is a call to
spi_begin(). Find that . Check there for pins, speed, and Chip Select. And set them to match your dev board.
Use slow speed to start with. Increase as it starts to work. I have on max now (80 MHz?), was on some kHz when troubleshooting.

Actually #if 0 all ethercat code and use the normal arduino setup(), loop() for encoder testing.
If you use serial port output it must be explicitly opened or something, check code.
You should be able to come a long way and then I'm back.
 

Just as a general thought, no GUI configurator can fully support the 7I76EU
(or any other hardware) , though I think MesaCT does support the output options.

In all but the simplest cases, some hand editing of hal/ini files is likely to be needed
and considerable hal customization will be needed for functions like tool changers,
spindle orientation, jogging options etc etc.

The SKR1.4 is not actively supported and the ethernet demo was an early concept testing. Please check this link for ethernet supported boards.

remora-docs.readthedocs.io/en/latest/har...hernet/ethernet.html

Cakeslob also has his F4 repo

github.com/cakeslob/Remora-STM32F4xx-W5500

I recommend you change this:
"
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) any laforter[sic] version.
"

To something like this:
"
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation.
"

This avoids the issue of people taking your code and relicensing it under GPL v3, which is incompatible with v2 (one way compatibility).

You could add a clause stating that your name and "jethornton" shall remain in all documantation and license files.

Reyes wrote:

Any one using this card?

I bought similar but not the same. Most important is that, there is custom bitfile preloaded at factory. If your's card works, do not try load any other bitfile.
I have some files received from seller (in attachment), the mesa-rtcp config is works for me, but not all resources are configured.
.

Hello, 
I have now got all axes running.
I would now like to set up homing. 
When I start homing, the axes start moving.
However, the home switches are ignored and the axes continue to move.
I have linked the home switches in the HAL as follows:

net X-home-sw        <= lcec.1.6.din-4        => joint.0.home-sw-in

Is this correct, or does the home switch have to be set to HomeSwitch(DI3) from the A6 servo drive?

Hello,


With the help of @Hakan, I will try to make a SinCos encoder input ethercat compatible board.
I'm a beginner so please don't give credit to my post, this is a learning project.
chip used: STM32F407VE and LAN9252

Here is the git project: 
github.com/paulsvc/Firmware

Done:
Step 1: Quadrature Encoder input 

Ongoing:
Step 2: Ethernet layer

@Hakan, I struggle to setup the ethernet part. I use the following pins:
SPI2_MISO: PC2
SPI2_MOSI: PC3
SPI_IRQ: PA8
SPI2_SCK: PB10
SPI_NSS: PB8
SYNC0:PC6
SYNC1: PB15

I went through the EASERCAT7000 project but I'm not sure when do you setup these previous pins

Thank you in advance for your help

Sandro wrote:

Is there a way to manually apply the Monokrom filter plasma_gcode_preprocessor to a G-code file outside of Monokrom, just to see what the output looks like?

Does Monokrom have an option to save the current G-code file? (I can see that it might well not have, as you can't typically change the file in the GUI, so there is no point). 
You might be able to view the file-as-run in the GUI though, and see something odd around (I stress "around" as the reported line number can be off by several lines) 

Unary operators are things like SIN[] COS[] etc so I would be looking for unexpected square brackets. 
 

mooser wrote:

While waiting I've got to find a better solution to using these fine wires from the sensors and pendant into the terminal blocks.

Maybe bootlace ferrules? Effective at stopping stray strands bridging between channels. 

(And some of the crimpers are fun - there is a little video of a 6-segment one here, though the 4-segment ones work better in cage clamps, I feel. 
www.amazon.co.uk/s?k=ferrule+crimper&crid=284PIPYNNE1CT )