Advanced Search

# ---Setup spindle at speed signals---

net spindle-vel-cmd-rps => near.0.in1
net spindle-vel-fb-rps => near.0.in2
net spindle-at-speed <= near.0.out
setp near.0.scale 1.000000
setp near.0.difference 3.333333


#THESE 4 LINES BELOW WERE ADDED FROM MODLATHE TO TRY AND FIX encoder

setp lowpass.spindle.gain 1.000000
net spindle-vel-fb-rpm => abs.spindle.in
net spindle-vel-fb-rpm-abs abs.spindle.out => lowpass.spindle.in
net spindle-fb-rpm-abs-filtered lowpass.spindle.out

net spindle-fb-rpm-abs-filtered => gmoccapy.spindle_feedback_bar
net spindle-at-speed => gmoccapy.spindle_at_speed_led

So...I am not 100% sure if this is a gmoccapy issue or a deeper linuxcnc issue but I suspect it is something with the GUI.

A long time ago, I made a generic XZ lathe + analog motor + external incremental rotary encoder HAL/INI via AXIS gui. All worked well, and the side of the AXIS GUI displayed the spindle speed bar plus the red button indicating if spindle was at speed or not. It worked correctly.

However, now I have build a different machine: a custom XZC lathe with a STEPGEN controlled servo spindle, and I am trying to simply have the same thing work where when I run the servo motor, I see the RPM based on what the encoder sees. The wiring of this machine is all the same as the last one minus a C axis and servo.

BUT... NOTHING I do allows me to see this information and I cant figure out what it is. Axis GUI does not display any spindle speed displays. I thought maybe it was an AXIS issue and switched to gmocappy, which I atleast was now seeing a spindle speed bar. However, when i turn the spindle on, I just see the default comanded rpm instead of what the encoder sees.

This is the relevant section of the HAL:


#Original 4 lines from "MODLATHE" working hal/ini
setp     lowpass.spindle.gain 1.000000
net spindle-vel-fb-rpm => abs.spindle.in
net spindle-vel-fb-rpm-abs abs.spindle.out => lowpass.spindle.in
net spindle-fb-rpm-abs-filtered lowpass.spindle.out

net spindle-actual-rpm spindle-fb-rpm-abs-filtered => gmoccapy.spindle_feedback_bar
net spindle-actual-rpm spindle-fb-rpm-abs-filtered => gmoccapy.spindle_at_speed_led

#above 2 lines added in attempt to get gmocappy to display the correct 


HOWEVER, any time I try to run the program, I get "spindle-fb-rpm-abs-filtered" but no matter what input i place into those two lines it says that pin does not exist

HALMETER: IN halmeter, I see abs.spindle.out and abs.spindle.in working correctly. Also, if I remove the belt from my encoder and monitor spindle-at-speed, if I command the spindle to move and then manually rotate the encoder, I get the value to change from true to false - which makes me think my setup is working and its more of a GUI issue?


Can someone help me figure out what I am doing wrong and how I can get gmoccapy to display my encoder RPM and if the spindle is at speed or not correctly?

my MODLATHE hal/ini is my original machine that had the working gui to show the encoder rpm and if the spindle was at speed or not.
my C+TURN axis hal/ini is my new custom machine i am trying to set up

Nice work! Using PIO board variants might be the way to go. That's how Marlin has managed it and it's so much like how Mbed uses custom targets. They use some custom python scripts to make the magic work.

OK it does work, my test configuration was missing the
default/max velocity and accel settings in the TRAJ section
of the .ini file. This (missing values) seems to work with the
standard TP (maybe it has some kind of working defaults)
but fails with  the S-Curve TP.

Note that I can still trigger following errors with actual
hardware as  the S-Curve TP does not seem to obey joint
acceleration constraints.

The TRAJ and joint accelerations are both set to 200 here:

 

But that acceleration is exceeded (and trips a following error when
it exceeds the hardware's accel limit of 240)

Spyderbreath wrote:

Thank you for the reply Daz, and the offer to help

I now have what appears to be a successfully flashed and converted ST to DAP-link.
 

Now I am at the point where I need to hook this newly converted DAP-link to the NVEM controller. Is there a wiring schematic somewhere or something that tells me which pads on the controller get which wires? The pads are not labeled on the controller.
 

Here are the photos of how to connect to the board. Please note that the microcontroller gets the 3.3v from the board thus you need to power up the board with 24v when uploading the firmware

Here is the CRC check for EC300:

Valid JSON config file, uploading to board
Config file length (words) = 1702
Config file length (bytes) = 6805
Remainder = 1
Padding added = [0, 0, 0]
Config file length with padding (bytes) = 6808
CRC-32 = 0x4731b6

When I'll have some spare time I'll try to fix it.

Ill be honest here Scott, they all do, and they dont use the H437 anymore. I didnt wanna discourage you, but it should be straight forward after the h723.

github.com/cakeslob/Remora-STM32H7xx-PIO/tree/h723

here is my WIP abstraction for multi targets from last night. Still havent copied over the SPI channel stuff just working on the clocks right now. Need to figure out abstraction for UART and CS pin also

Check the pile of shit I sent, I think theres another H7 something there you can test. Theres basically only 4 main profiles and everything else is just pin changes

H743 - 25mhz clock
H743 - 8mhz clock
H723 - 25mhz
H73 - 8mhz clock

You have integrated VGA i have a NVIDIA 610 i think is this the cause of high latency , my motherboard don't have vga output!
can you try use Rustdesk remote desktop with youtube video and try another time latency test?

Hello Daz,Could you please share the serial log during the config upload?
I'm curious about the CRC check.Thanks in advance!

I have these kernel parameters set "quiet isolcpus=2,3 acpi_irq_nobalance noirqbalance irqaffinity=0 processor.max_cstate=0 intel_idle.max_cstate=1"
From what I remember, better results are when you isolate 3rd and 4th core.
The "stress" test should not affect core 3 and 4.

To use NPN sensors with 7I76U inputs (which need a positive signal to actuate),
you must add a pullup resistor to each 7I76U input connected to a NPN switch.

+24V --> resistor_pin_1 --> resistor_pin_2 --> NPN output + 7I76U input

Suggested resistor value is 2.2K 1/2W

(PNP sensors need no additional components)

Murphy wrote:

@cakeslob , I had a look at your hal file again and copied your spindle stuff exactly just changed for my pins etc and it's still the same. So I think that rules out a hal file problem. I don't think it's the vfd because I can change the speed manually by pressing the + and - manually in the  Axis GUI and it responses quick with no dips when changing speeds. 

Hmm probably going to have to do a halscope to see what is happening with that remora.sp0 and/or RPM signal when using css. The fact that it only does it while CSS is making this difficult to narrow down

just do a quick double check of my config ini/hal, and see if anything stands out. This is the config I used to test out threading and css the last time we talked. I dont think my halfile was a whole lot different, but maybe something in the ini file. Im still very new with lathe, but threading and css appear to function as intended.

github.com/cakeslob/RRW_LAB/tree/inc/Lin...mora-RRW_LAB_latheng

Hello everyone.

I managed to get 3 separate NICs in a Fujitsu Desktop with a PCIe adapter, and now i have successfully connected to EtherCAT, Mesa 7i96s, and the internet simultaneously.

I have done this to move a XX,Y,Z gantry. I have 2 motors for 2 Z axis, which will work independently in 2 separate Qtplasmac configs.

I have created a simple 7i96s config from PNCCONF, and tried to adapt it into my CIA402 config. There have been some errors in trying to boot QTplasmac, because i keep getting different errors like the following.



I have to comment this line otherwise the system doesnt boot.

when i comment that line out, the config almost starts but then i get this.




My main goal would be to start the config, and double the X axis signal into 2 motors, altering the cia402 config.

basically get a main axis and a tandem axis with ethercat, which will have 2 home input from the mesa card.

remove the problem of having to comment out the line which provides plasmac z axis position *listed above*

get 2 different Z motor driver slaves to run for Z axis, one for one config, and one for the other

Startup QTplasmac and finish my config according to the machine



Could anyone provide some tips in the right direction please ??
I attach my config below.


Thank you
best regards