Advanced Search

Yes, correct!
But I’m still having some issues with the config upload, which I’m currently investigating on the EC500 board.
If you're unable to change the config, you may need to erase the entire chip first:

Then flash the firmware again and upload the new config.

This worked for me, but it's definitely not an ideal solution...

not sure i follow about the speeds thing? maybe your configuration settings for default jog speed? not sure about the keys things, been completely covered up with work and haven't had any time to dig into probe basic recently. maybe ask the linuxcnc devs if they could add a keyboard assignment to the configuration? for lathe? if its such an issue im sure more folks would want a global resolution that translates into any gui running the lathe option in the ini.

Happy to help, just a small payback for all the help I have received in the past from this site and members.

did you get this resolved?

I did set the acceleration in the TRAJ section, it does affect the acceleration
but the scaling seems not to be correct. The Acceleration/Velocity bounds are important
since they are per joint physical limitations.

(sorry if I am getting out the sandpaper when construction is at the chainsaw stage)

It is great so see  a jerk limited profile working with LinuxCNC as it fixes the inevitable
following error at the start/end of motion due to the impossibility of having instant force
application in any real drive system.

yeah that delay is a bugger.. the drive should be enable constantly and just be looking for a direction voltage and step pulse stream. i would have the drive enabled anytime the the machine is on and not estopped. and have it sitting idle waiting for pulse command.

cakeslob post=326968 userid=25269

Are all the drivers the same, or did you do your check all axis with the same drive

 jjdege post=326970 userid=32556

hi
the same driver for all axes.
I tried to unsolder the chip, without success
the board does not respond, for now I do not think I will buy another
thanks for the support
 

Hi guys

I couldn't resist and bought a new board, this time I opted for a 3-axis EC500,
it has LEDs that indicate the I/O status, I think it's more complete.

I tested it with Mach3 to make sure it was working well, given the previous ones,
and it worked on all three axes.

When loading the firmware, it got to 29% and timed out and everything froze,
the DAP wasn't receiving signals.
I reread page 115 of the thread that talks about how to unlock and after having
bridged BOOT_MO and 3V3 I managed to delete and write the new firmware!!

Now all 6 axes work.

Thanks again to Scott and to whoever made all this possible.

great!

Do not ever run an OS from a USB key long-term.

The flash memory will wear out and the bandwidth will be limited b/c USB only has 1 unidirectional dataline.

It cannot read and write simultaneously.

USB 3.0 and greater fixes the bandwidth issue, but the weardown of the flash memory is still very problematic.

I recommend you install Ventoy to a USB, download an ISO of LinuxCNC from the downloads page, and install to an HDD from that.

Chrome downloads files slowly for some reason, use Firefox, curl, wget, or JDownloader to avoid waiting all day.

You can reduce latency by setting the CPU governor to performance.
echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor > /dev/null

I prefer Ubuntu's GRUB to Debian's.

(the Debian version is ugly)

Very nice next blacklisted intel backdoor! six windows of youtube no junction error!! But nest use rustdesk error coming 
 

.exe = Windows.

On a Unix-like filesystem, files must be marked exucutable to be executed.

It's a security thing.

Chmod +x will mark a file as executable.

I once helped a user who needed to get a ATC turret working that used a stepper and needed to lock the tool by rotating backwards against a pawl (which I _think_ is what yours does):


To get this working we modified a component called 'toolchanger'. The final version is attached here:
forum.linuxcnc.org/38-general-linuxcnc-q...lved?start=80#188377

Looking at these sections in 'carousel.comp' makes met think that the reverse action does not work in 'counts' mode :



Note that there is nothing changing 'counts_target'.

@Pcw,

Thanks for reporting this.  For now i will keep this in mind, and will test this later on.

The [TRAJ] section is responsible for setting the planners max-acceleration values.
The planner doesn't look at the individual joint max acceleration values. Maybe that is causing trouble.

@All,

Ok, for the cia-402 component i made a home sequence intrusion in the homemod.so component.
It basicly enables external homing, and not triggering following error etc during this procedure.
All is done with a few hal pins.

When using the servo's internal home sequence the lcnc home sequence can now be done by a connecting a few hal pins.

For each joint, you can activate the cia-402 home sequence.
In this way, a non cia-axis, can be homed by lcnc's original method as usual.
 

1. You can set pin for enabling the cia-402 internal servo drive home sequence.
Set this flag "setp" in the .hal file after you load the cia component for example.

2. The cia-402 recieves a home command from homemod.so
Connect the cia-402 home command pin (input) -> homemod home-drive (output)

3. The cia-402 servo pos feebback is passed to the homemod.so when the servo is homing and changing position.
Connect the cia-402 pos-feedbak (output) -> homemod.so pos-fb

4. When the cia-402 drive is homed, it updates a flag in homemod.so wich set homed = 1.
Connect the cia-402 is homed flag (output) -> homemod.so drive-is-homed.

libhome

source code intrusion

Sinds i have no cia hardware, i tested this ok in a linuxcnc simulation config.

Wow, yes that does help immensely. Fortunately I was up early enough this morning to retrieve the hardware from the trash before the truck came down the road to hall it away. Unfortunately, not before I ordered a 7I96S, but I'll find a use for the both of them as I have a Emco 120P to retrofit after I get this mill up and running.

The info in 3. is the first time I have seen any reference to that file.

About 8. ? The post that Daz made if you are referring to this one - forum.linuxcnc.org/18-computer/44828-rem...rd?start=2140#327240 - is for an EC300, not an NVEM. From what I am seeing I will need to follow to the letter up to step 8, then use the nvem-rt1052.txt instead of the ec300-rt1052.txt linked to in that post. Is that correct?