Advanced Search

GeckoWorks wrote:

So, as for the question about signal levels for the B2 servos' Z pulse, I am honestly a bit daft when it comes to eletronics and don't even yet have a grasp on when a signal is digital vs. analog...

I can only find a mentioning of: " Z-phase Differential Signal". Not sure if that's what you're after. And then some screenshots from the manual:
 

 

 

Ok I think you've got a differential encoder.  Differential encoders will use 6 wires but you can also configure them to only use 3 if you wanted being single ended.  The wires will be A+, A-, B+, B-, Z+, and Z-.  Sometimes the encoders Z will be called Index or I.  So it would instead of Z+ and Z- its I+ and I-.  There both the same I and Z.  If you get the Mesa 7i96s theres a jumper called W3 that you can change the boards encoder input from single ended(3-wire) to differential(6-wire).  They come out of the box already set in differential so you wont have to move it.  Differential is what you want anyways its more accurate.  Also sometimes this differential and single ended terminology is called biphase encoding.  Theres like four different kind of encoding signal/protocols its all really complex and is difficult to understand sorry

It's a please copy us project, vs blab about some design and maybe release files after the kickstarter. This is inspiration for low cost makers of additive tech similar to how mSLA is now available for <$300 using smartphone and tablet LCD panels.
Example: www.amazon.com/ELEGOO-143-43%C3%9789-6%C...Carbon/dp/B095K3JWP3

Updated to 3.5.9, still get Invalid bitfile header!

Assume the firmware on the 7i96s is still the default, dont think I had any reason to attempt to change it any time I tried setting something up before. I do get a reply with the —readhmid.

The dpl firmware just turns my spindle encoder header back into general I/O, right?

There was a fairly recent PB update in response to various requests (including mine) to make disabling keyboard jogging easier.

To enable keyboard jogging, you'll need to edit your INI file.  Specifically:

[DISPLAY]
KEYBOARD_JOG = 1

If that doesn't fix it report back and we dig in to it a bit more.

You may need to update to 2.9 for the pncconf discovery option
to work, or just use the g540 option to start

Thanks for sharing!Great job! We all understand how much work this is. I'm sure I'll have a lot of questions. Now I have some work to finish the lathe from the other thread. and I will start working on the mill.

@Tommy,
I think it's not related to rtai or something like that.

@Tia,
same here on the rt kernel on debian 12, try to start the AppImage the terminal just hangs there, no output at all
Maybe i will try it myself on a virtual machine. If this works, then it supposed to work at other places.

@Arciera,

How do I do that?
Using the cmake system, compile everything and then run it. When u use no sudo for the "cmake make install" step,
it will run non-realtime. I will do that, but now i have no time to do that. Family visit.

 

same here on the rt kernel on debian 12, try to start the AppImage the terminal just hangs there, no output at all

Yeah, nevermind. I didn't mean to include that one.

Yup, this is non RT kernel, will try on a RT kernel later.

Create a new HAL_COMMAND entry in the ini file:
MDI_COMMAND=G10 L20 P0 X0 Y0 Z0

and call that from your hal:
net zero_all => halui.mdi-command-your_number_here <= and2_C.out

If you still keep core dump, i can edit the appimage to run Using POSIX non realtime

How do I do that?

I was thinking about the core dump. This is kernel related.

Just tried the updated AppImage and I also get a CoreDump on my non-RT LinuxMint machine. I then tried it on a machine with a preemt_rt kernel and when I try to start the AppImage the terminal just hangs there, no output at all.

I look forward to seeing how it turns out