Advanced Search

SP+ and SP- need to be supplied with 5 to 20 VDC

Typically this comes from the VFD to maintain full
isolation from the logic side and the noisy VFD side

The spinx1a analog output is basically a potentiometer
replacement, so connects to a VFD where the potentiometer 
connects.
 

Hi again!
Final results:
yes, this code is correct:

halcmd setp ini.0.max_acceleration $accel
halcmd setp ini.x.max_acceleration $accel

M100 Pxx codes works well....it contains keyboard arrow/pendant/program acceleration overrides
so...i wrote small part to pyVCP as well

Thank you all! (specially to Todd)

Ok, that calmed me, I've missed that.
Regarding the output pins, I understood that between SP+ and SP- I should have 10volts, I don't seem to measure anything.
Previously, I was using mesa 7i97 and I was getting the 10v analog from it.

Sorry if I ask stupid questions, I am not quite into electronics

Do you already have it set up for LinuxCNC? What hardware are you using now?

Starting from scratch I think I'd get a 7i93 plus a 7i47S. (I think that might be the most inexpensive Mesa option with full functionality.)

Both -- my setup has steppers that have handles on the ends. Right now it works great for both CNC and manual mode, albeit without a DRO if you're in manual mode (motors off).

My dream is to be able to boot up linuxcnc and use that as a display for a DRO and also have it be able to enable CNC mode at any time.

Here's a photo:
 

Hi all,

I am trying to get my hands around this. Played around with the Docker container a bit. I have so many questions...

I think it would make sense if we collect for the Boards to have a sample config file. E.G. I just ordered the Colorlight5A 75E and will set up a simple milling machine with stepper motors. What do you think?

Either way, if someone could share a running json file with me, that would give me a head start.

I will add to the documentation to make it easier for further users to get started.

The speed and direction LEDS are reversed on the first REV SPINX1A cards
This is mentioned in the manual:


Note that on SPINX1A cards previous to revision A, the DIR CW and
SPEED LED labels are swapped.

 
Also tested the 6.1.75 vendor kernel (with panthor driver), only after loading chromium and watching videos on youtube the latency raised a bit as you can see, but still very acceptable. Isolating all the fast cores improved that, but for me it's not worth it as it becomes noticeable slower.

For the rt-patch only a few had to be done manually for the serial 8250 driver because of some vendor edits.

Kernel/config
drive.google.com/drive/folders/1JglCIPKv...cjOvr?usp=drive_link

An easy way to install with gpu acceleration is to install the kernel on the image 6.1.75 with backported mesa from:
mirror.vinehost.net/armbian/dl/orangepi5/archive/
or
mirror.vinehost.net/armbian/dl/orangepi5-plus/archive/

Install the kernel with: sudo apt install ./linux*.deb
And link the Image file to the rt-kernel: cd boot; sudo ln -sf vmlinuz-6.1.75-rt23 Image

I wonder if there was a functional reason this was clipped to +- 1?

Edit:  I’ll reach out to the author for that commit and see if I can get an explanation.  The commit details explain the negative stuff, but no reason as to why 1 was choosen in either direction.  

I'm afraid I'm not aware of a faster way to set feed-override than halui.
If you feel like experimenting you could try and remove the value clipping for 'motion.adaptive-feed' in 'src/emc/motion/control.c' (you would need to build linuxcnc on your local machine to do that though):

 

I have connected the pins as following but I think something is off with the firmware of the board or smth.

TB4, Pin1 (GND) -> SPINX1A, Pin1 (GND)
TB4, Pin2 (STEP-) -> not connected
TB4, Pin3 (STEP+) -> SPINX1A, Pin3 (PWM)
TB4, Pin4 (DIR-) -> not connected
TB4, Pin5 (DIR+) -> SPINX1A, Pin5 (DIR)
TB4, Pin6 (+5v) -> SPINX1A, Pin6 (+5v)

TB5, Pin24 (Out5+) -> SPINX1A, Pin4 (ENA)
TB5, Pin23 (Out5-) -> SPINX1A, Pin2 (GND)

In hal I have added:
net spindir spindle.0.forward => hm2_7i95.0.gpio.009.out

Checked the pins in hal configuration, I can see the pwm being enabled, and I can see a value that changes as I change the spindle override. This value is either positive or negative depending on the spindle direction.

The problem is that the Speed LED on the SPINX board is always on. When I start the spindle in reverse it says on, when I move it forward it turns off. I think the Dir LED should behave like this not the speed pin.
The enable pin lights on when I start the spindle in any direction.

From what I read on a separate thread, the DIR led on the SPINX board should turn off in one of the directions. For me its the SPEED LED.

Also when I play with the spindle override the DIR pin dims when I increase the spindle speed and it lights up when I decrease the spindle speed. The dimming of the led proportional with the spindle I think its expected, but it should be the SPEED pin not the DIR pin.

I checked the wiring several times, so this leads me to believe that somehow the pin allocation on the mesa board is not correct.
I've used the firmware provided by you in the begining of this thread.

Please let me know your thoughts on this matter.

And mention your location...

yes, just modified my comment to include the context

Hi Bax,
Is this for the EDM's you build?

I considered doing that, however the halui component runs on a much lower frequency that the motion component.
I am running a real time component that very quickly needs to change the feedrate. motion.adaptive-feed can do that, but only from -1...1 I cannot use halui.feed-override unfortunately because it would be too slow, not real-time like the motion component.

Some context here. The application is wire EDM. During normal cutting my software calculates the feedrate and controls motion.adaptive-feed to get the right speed, which normally lies in the -1...1 range of the feedrate. However, there are occasional shorts, for which the machines needs to retract fast in order to prevent wire breaks. Retraction is now performed at -1*feedrate due to the limitation. However this is not fast enough, I need that to be faster.