On Tue, Jul 13, 2021 at 7:01 AM Jon Elson wrote:
> I have a customer that has a router with
> Meldas MDS-B-SVJ2-10 brushless servo drives.
> ...
> Does anybody know if these drives can be controlled with
> any of the standard schemes - analog velocity command,
> step/dir, etc?
hi!
the only way
On Fri, Apr 16, 2021 at 3:37 PM andy pugh wrote:
> I am not sure that you can guarantee that the ini.X.home_offset pin is
> read at the right time.
>
> My suspicion (without looking very hard) is that the ini pins are
> polled in user-space and the homing code runs in realtime.
you're right... i
i think it can be done without any mods to the linuxcnc by a wrapper
component for hm2.encoder, HOME_USE_INDEX and using the
ini.X.home_offset pin to set the abs position.
1. wait joint.X.index-enable -> set encoder.latch-enable
2. wait for encoder.latch-enable to reset (on 1st index mark) -> save
>
> I told you the fix before, and I will tell you again. Intel and nVIDIA DRM
> KMS drivers have been disabled in kernel Kconfig.
> To run at 1080p, 4K, or whatever you want, use xf86-video-fbdev:
>
yeah, thanks. just wanted to answer to andy what happens if i boot the rtai
kernel. i myself ok wi
>
> > it boots, hangs for a while with a blank screen before X logins is
> > displayed. the resolution is set to 1024x768 instead of the panel's
> > native 1440x900. hangs on shutdown waiting for a few minutes for
> > stopped tasks. otherwise seems to be ok.
> Actual "minutes" or just a slightly lo
> Can you try the RTAI kernel?
> wget http://www.linuxcnc.org/temp/linux-image-4.14.148-rtai-amd64.deb
oops, sorry, missed that. i mean i did try the rtai-patched kernel before...
but anyway. can't repeat it on N3150 now, used i7 M 620 instead, debian 9
it boots, hangs for a while with a blank s
>
> This all sounds as if its is only applicable to servo systems, us
> hobbyists with steppers running everything might as well sit back and
> enjoy the "what ifs" since steppers have their own insurmountable jerk
> problems when useing common $40 50 volt drivers, and mesa cards.
>
but us hobbyis
On Thu, Nov 14, 2019 at 9:00 PM andy pugh wrote:
> > afair, the intel graphics driver i915 is not compatible with 64-bit
> > kernel. tried to run it on a celeron (N3150?) and display resolution
> > was limited to something like 800x600.
>
> Which kernel?
4.14.148
i915 Kconfig has: depends on X86
On Thu, Nov 14, 2019 at 7:25 PM andy pugh wrote:
> The current version of RTAI that has been used to build the 4.14.148
> kernel that I have been experimenting with does not support 32-bit.
>
> I suspect that it will not be missed?
afair, the intel graphics driver i915 is not compatible with 64-
> > > I see in src/Makefile, motmod-objs
> > > gets emc/motion/motion.o, emc/motion/command.o, etc., but where are
> > > these object files being built from the .c files? Submakefile under
> > > emc/motion only copies headers to ../includes. There is nothing to
> > > compile these source files.
> >
> In some ways the important testing comes from _not_ using it. If you
> have run a machine for a long time with a reverse-run version and have
> not seen any problems with conventional working, then I think that
> counts as a good indication that the feature does not break existing
> behaviour.
s
responds in half duplex I assume it's a MF-S13...
>
> Mark.
>
> Dmitry Yurtaev wrote:
>
> hi!
>
> very cool projects!
>
> i played a bit with mitsubishi serial encoders, maybe i have some info
> you may find useful.
>
hi!
very cool projects!
i played a bit with mitsubishi serial encoders, maybe i have some info
you may find useful.
i also collected info on some basic parameters of most mitsubishi
servo motors: like IDs, rated/max current and speed, number of poles
and few other constants in unknown units.
here
ly
satisfied how they look now, but i need to experiment a bit to think
it thru
but here it is. if someone think it is worth refining - please, comment
/dmitry
On Mon, May 2, 2016 at 11:57 PM, John Kasunich wrote:
>
>
> On Mon, May 2, 2016, at 04:37 PM, Dmitry Yurtaev wrote:
>
> You want the pyvcp LEDs to always be associated with the
> same hardware pins, even if you change the function (aka
> net name) that the pin is used for
exactly!
> This is kind of an odd application - usually the mapping of
> hardware pins to functions is determined by the physical
> wiring
ry
> 04/30/2016 02:47 AM, Dmitry Yurtaev rašė:
>> i'm trying to organize my configs and having trouble doing it
>> conveniently. i'd like to localize external connections in one place
>> and give signals meaningful names. e.g.
>>
>> net x-neg-limit sscii.0.gpio.
i'm trying to organize my configs and having trouble doing it
conveniently. i'd like to localize external connections in one place
and give signals meaningful names. e.g.
net x-neg-limit sscii.0.gpio.0.in-not
net x-pos-limit sscii.0.gpio.1.in-not
net stop sscii.0.gpio.11.in-not
and then use signa
On Wed, Apr 13, 2016 at 2:29 PM, andy pugh wrote:
>> or is it possible to
>> change HOME_SEARCH_VELOCITY at run-time? if so, then it will do
>
> I don't think you can change the homing data at run-time.
> One option might be to choose a different config depending on whether
> absolute position ha
>> - to eliminate homing i've added a "halui.joint.N.set-homed" pins
>> which. when set to true, just execute SET_JOINT_HOMED_FLAG(joint, 1)
>> without performing a homing procedure
>
> Does this work differently to just setting the HOME_SEARCH_VELOCITY to zero?
i do need homing initially and in a
hi!
i see a topic of absolute encoder support arises rather regularly.
i've been playing with mitsubishi J2 super sscnet servo drives for
quite some time and finally i have a working PCI controller. as J2S
series motors feature absolute encoders i've made a quick and dirty
hack to support them in
20 matches
Mail list logo
