Advanced Search

The drives common or GND signal should be connected to the 7I77 power GND with a separate wire. Where is the power GND on the 7i77? 

This would be the drives analog common, or if the drive has differential inputs, Analog in -

Since I don't use windows and therefore also a TwinCat,
I have been looking for a way to convert my ESI files under Linus and write them to the EEPROM.

I have to say that there is already such a tool in C,
but you can only use it for their hardware.
So I thought I'd write one in Python under the GPL.

it's still in the early stages, but the test data I have is written 1:1 bit-accurately in the same way as the siitool does.

github.com/multigcs/esitool/

 

In cases where you have an unsigned spindle speed device (like an analog 0..10V VFD)
and encoder feedback, It might be better to use the signed commanded spindle speed
into the PID and just use the ABS on the output of the PID component to always get positive
analog values and also use the ABS components is_positive and is_negative pins for driving
the VFDs FWD/REV controls.

 

ready for testing:
github.com/multigcs/esitool/

there are some testfiles in tests/
and they are all bit exactly as generated by the siitool

but i need more testfiles and maybe some tester

That points to hardware issues, are you sure:

The index wiring is correct.

The encoders actually have an index output.
 

i do that, but never nothing

Note that 'genserkins' uses 'modified' DH parameters.
Have a look here (there is also an example of how to derive the parameters for a manipulator):
www.linuxcnc.org/docs/stable/html/motion...ml#cha:dh-parameters

Do the joints not move at all when you try to home them?

As a short-term expedient you can turn off the requirement to home (INI NO_FORCE_HOMING) and (if you are using the Axis interface) switch to world mode with Ctrl-$.

But don't forget that then the machine will have no idea where the joints are, so the end-effector motion will be a very curly version of cartesian.

"Bad character" should tell you which line of the G-code the error is on. This is much more likley to be a problem in your G-code than in the G71 code. (not that I exclude that possibility)

At a guess you have closed-loop control of the spindle, but the PID is being commanded by absolute spindle speed request.

I am not sure why you used Stepconf at all. You should have been able to just copy the old "linuxcnc" directory from one drive to the other, and carry on as before.

M3 probably _could_ be remappable. It would just need the hooks adding to the code. After literally seconds of contemplation I can't think of anything that means it fundamentally couldn't be remapped if the code was modified to handle it.

The issue is that I'm not even able to move the robot arm, because it requires me to perform a 'Home All' operation before initiating any movement. I'm 90% sure that the problem lies in the incorrect application of DH parameters on my part. The tricky part is that it's so simple, I have no further idea what could be going wrong. I've been stuck at this point for a couple of days now, and still no progress. Later, I plan to rebuild the project from scratch to avoid any unnecessary correlations with the original Puma source files. Maybe that will help.

My guess would be that you lost the { at the end ofor possibly the one that terminates that set.

If you still have the good and bad files, then could you attach them? I don't think that I can make the compiler more helpful in it's error messages, but possibly the preprocessor could be.

How good are the clones they sell o AliExpress?

Has anyone tried one of these on a Nena 23 motors.

embeddedtronicsblog.wordpress.com/2020/06/24/tmc2160/