Advanced Search

the first part is what you add to the bottom of your hal file

the second part is a sample of the NVEM config.txt. the config.txt is what configures the remora hardware to the remora software. the hal file is what connects the remora software to the linuxcnc software. i included it to emphasize the relationship between which IO on the board does what in linuxcnc

The ini file is what configures your linuxcnc machine, so speeds of each axis, the travel, where the home switch is, how many axis/joints, the gui, etc

Just type the command "ethercat debug 1"
 

I can't even get QtDragon to work at all.

Good luck.

Today I rewired the carousel stepper driver to the MESA hardware stepgen nr4, which was a 5min job.
Consecutively, I spent 4 hours trying to get it running again.

The stepgen in velocity mode is controlled mainly by "velocity-cmd" which takes a float value.
Positive for CW and negative for CCW.
Main problem was setting the float value with the two digital outputs ( motion.digital-out-03 & motion.digital-out-04) that are triggered for CW and CCW carousel rotation. 

But in the end I solved it using MUX4: linuxcnc.org/docs/2.4/html/man/man9/mux4.9.html

# --- (Carousel CCW / REV) 
net ATC_Motor_CCW mux4.0.sel0 <= motion.digital-out-03
net ATC_Motor_CW mux4.0.sel1 <= motion.digital-out-04 

net ATC_Motor_DIR_VEL hm2_7i96s.0.stepgen.04.velocity-cmd mux4.0.out 

net ATC_Motor_CCW_SPD mux4.0.in1
sets ATC_Motor_CCW_SPD 5000

net ATC_Motor_CW_SPD mux4.0.in2
sets ATC_Motor_CW_SPD -5000 

net ATC_Motor_OFF_SPD mux4.0.in0
sets ATC_Motor_OFF_SPD 0 

net ATC_Motor_OFF2_SPD mux4.0.in3
sets ATC_Motor_OFF2_SPD 0  


#*******************# ATC Stepgen#******************* 

# Step Gen signals/setup
setp hm2_7i96s.0.stepgen.04.steplen 20000       # Step length (nanoseconds) 20 usec
setp hm2_7i96s.0.stepgen.04.stepspace 20000  # Step space (nanoseconds) 20 usec
setp hm2_7i96s.0.stepgen.04.maxaccel 50000    # Maximum acceleration (steps/second^2) so 1/10 second to full speed
setp hm2_7i96s.0.stepgen.04.maxvel 5000         # Maximum velocity (steps/second)
setp hm2_7i96s.0.stepgen.04.step_type 0           # Regular step type
setp hm2_7i96s.0.stepgen.04.dirsetup 50000      # Direction setup time (nanoseconds) 50 usec
setp hm2_7i96s.0.stepgen.04.dirhold 50000        # Direction hold time (nanoseconds) 00 usec
setp hm2_7i96s.0.stepgen.04.control-type 1        # Control type (1 for velocity control)
setp hm2_7i96s.0.stepgen.04.enable True            # Enable the step generator initially 


No more delayed response!!!
 

Do you have an idea how can i solve this issue?

Correct me if I am wrong, being all new to this, but that first bit of "code" you listed there looks to be from a .hal file and not an .ini file? If so then that gets me even further along and might be enough for me to get dangerous and take a stab at it.

who needs odrive when you can also use rio directly

www.youtube.com/shorts/L-D2a9atD_0

What do you mean with "SoE"?
Maybe i try to get a used Beckhoff AX5xx from eBay when thats easyer to use with LCNC.

... the SIEMENS etherCAT pcb is hard to get. it starts to annoying me...


endian post=327010 userid=29161
AX5xxx from beckhoff is SoE and it can be pain to create custom .xml which should be editable out of Sachas own .xml files...
 

SoE does mean - Sercos over Ethercat ... similar to CoE - CANopen over Ethercat ... You can imagine that ethercat itself is a empty lorry train were many different buses/networks shape members can sit a transport itself where they are need ..but very fast, synchro and with many many diagnostic stuff

I have never creating custom .xml file for them only for CoE stuff I have done it... I think if you are basic user it should be enough for you to use .xml config from saschas shop but ... it has many many very usefull stuff as monitoring the native I/Os ... external encoder - basically for external encoder as linear scales to run velocity loop over them ...

hmm i thought we had a full config somewhere with spindle. I guess its time to make one (aka copy flexihal). Ill try to mash out a regular config based on my setup

yes the config wizards will be less than helpful in most cases. limits are easy, but estop is a case by case basis depending on how you wish to wire/config your estop. tux posted his estop example a few pages back, and there is an estop example in the remora docs hal section.

for the ini file, yes read the manual, but dont start adding a bunch of options that might not apply to remora.

based on my friends rast's config, the endstops might look like this depending if you do a limit or a limit+ home config. it looks like he has included both in his ini file.


the important part is making sure your remora.input.xx match the config.txt file. from the nvem config, label IN03 on the cover of the NVEM board is connected top data bit 6, aka remora.input.06

Some ethercat drives offer built in digital IO that can be used. Ideally the VFD used would also have an ethercat interface.
Many VFDs also offer an RS485 (Modbus) interface which can also be connected to linuxcnc via a USB-RS485 adapter.

LPT can certainly work but it can be a bit tricky to find a PC with low enough latency.

Given the isolation of your market you might want to start out by looking for a used PC with an LPT and an ethernet port and see how low you can get the latency. Mind you, I have no idea how easy/cheap it is for you to find used PCs to try but this would give you an idea of what step rates you could get out of an LPT port solution before buying the drives.

[edit]
I think it should be possible to use ethercat for the drives and the LPT port with one of those cheap breakout boards for the digital IO and the VFD.

Old card nvidia 
 
new amd gifted by my friend 


4 winodws firefox youtube 4k and rustdesk!

Thanks for that fast reply! OK, so if I am understanding correctly, the EC500.hal is universal for all 3 RT1052 based controllers and I just need to edit the .ini file for my machine?

I have uploaded the nvem-rt1052.txt to the controller, and that seems to of worked well.

Looking at the ini file I am now seeing what my first problem has been, as nothing is there but the config for X Y and Z. No Estop, limit switches, spindle, etc.. So at this point I will need to go and RTFM, (this? linuxcnc.org/docs/2.8/html/config/ini-config.html), on the ini file and try to figure out what I am suppose to put there to get the rest to go.

Given that I am unfortunately a 101% tactile learner, where would be the best place on the forum to ask my questions about what I'm getting wrong as I proceed with this editing attempt?

Thanks again for the info as I have not seen that part explained before. This is a bit of help in the right direction. I'll take it none of the configuration wizards will be of any help in this endeavor?

tommylight wrote:

Do not wire Enable until you get things working.

 

Yep, on simple step drives, its a DISABLE input.

Brushless motors should last almost forever.

You can probably keep the old motors.

Motor drivers have improved a lot.

Motors are mostly the same today as they were 30 years ago.

The induction motor is a very, very old invention.