Advanced Search

Hi Friends,

Circling back here, it was a blown driver, I've it replaced and now the motor acts as expected. Thanks for the support, i am no longer having this issue.

The _average_ PWM voltage (what a voltmeter reads) with be the output voltage (~5V)
times PWM_value/PWM_scale

The PWM amplitude is always 5V, its duty cycle changes with the PWM value

I would set the PWM value manually for testing as I have no idea what the velocities
are relative to the PWM scale

The PWM scale is voltage right? setp hm2_5i25.0.pwmgen.00.scale 5.0 means the amplitude of the signal is 5 volts.
Does PWM in our context go positive to negative!! I did try setting it like this with 7i77 board.
When I measure the PWM output with a voltmeter, it shows positive 5 volts with both positive and negative jog directions with direction pin providing +5v when using negative jog and staying at 0 volts with positive jog.

Since I mentioned scale as 5.0 and I'm getting 5 V PWM signals correctly but why an initial spike of 0.25 volts and it goes back to zero and then climbs to 5 volts is the mystery that needs solving. I'll plot the velocity and PWM signals tomorrow and report back but isn't the PWM signal the one with drives the position thereby driving the velocity? Maybe setting max jog velocity has some effects on the PWM signals generated.

Two ways to do this:
1. method add 'tool_probe_and.in1' to the line above like this:

2. Reuse the signal name assigned to the ...input-08-not.

beauxnez wrote:

has anyone made qtplasmac work with a NVEM card?

  File "/usr/share/qtvcp/screens/qtplasmac/qtplasmac_handler.py", line 220, in __init__
    float(self.iniFile.find('AXIS_Z', 'OFFSET_AV_RATIO')) * 60

  File "/usr/share/qtvcp/screens/qtplasmac/qtplasmac_handler.py", line 220, in __init__
    float(self.iniFile.find('AXIS_Z', 'OFFSET_AV_RATIO')) * 60

If anyone had a qtplasmac config for the NVEM, they would have ended our suffering 2 pages ago.
its probably this, i think the THC probably uses external offsets.
add this line and report back
github.com/rodw-au/showstopper/blob/master/my_Plasma.ini#L226

or the next time an error pops up, you can try and trace it out, using all those other plasmac examples I posted before, or by referring to rods config I just listed, otherwise this will be a very long process.

You could plot the velocity command to see why the PWM behaves that way

 The PWM average output voltage will simple follow the PWM value its given

Note that you also have to make sure you don't exceed the maximum PWM
values (+- PWM scale)
 

I know this has been discussed ad nauseam on this forum but no matter how many posts I read or years I've used LinuxCNC, I just cannot understand how to accomplish these simple tasks.

I want motion.probe-input to be triggered when hm2_5i25.0.7i84.0.0.input-08-not is True AND motion.digital-out-00 is True.
I also want and MDI command called when hm2_5i25.0.7i84.0.0.input-08-not is True AND pyvcp button is clicked.

When I try to use the hm2_5i25.0.7i84.0.0.input-08-not pin twice, I get an "already in use" error. How can this be accomplished?

Thanks.

LeslieTroyer wrote:

of the repositories that looked "hopeful"
Remora-main, and Remora-RT2052-cpp-Main had remora-the-3.0.c
both the same -- neither worked (forgot to incclude that)
and the one listed which also didn't work -- (same error)

I think maybe the 3.0 one I worried was specifically related to the EC500 (all the remora-??? directories under LinuxCNC appear from filenames to be ec500 based

If your board has the RT1052, refer to the page I linked to, and only install the components/firmware/configurations referred to in the documents. The linuxcnc .hal file configuration doesnt matter if its EC500 or NVEM. The config.txt is important to match with the board.

Note that

setp hm2_5i25.0.encoder.00.filter 0

only changes the X axis.

Plotting the velocity, commanded and feedback position
should give the information needed to diagnose the issue.
 

kcjengr.github.io/probe_basic/tool_length_setter.html

be sure to set the max z travel to just a few mm larger than the spindle_zero distance. this is the distance that is commanded for the z minus probe direction and will stop the probe event if no trigger event occurs at the end of travel.
 

Hello! Today I was working on a GUI and found what the problem was! Last time I didn't do it according to the instructions. I wrote Index with a capital letter, but it should have been with a small letter. It turns out that index is case sensitive. I did this today and it worked. This is much faster than typing commands manually. Thank you!

@Grotius

Question 1:
yes s0 and se are the end points. The first clothoid of the spline P(s) starts at s0 and the last (4th) clothoid of the spline ends at se.
P_traj.(s0) = P(0) and P(s4) = P_traj.(se)
P(s) is the clothoid spline and P_traj.(s) are the curves at the beginning and end of the spline.

Question 2:
That's correct. You can either calculate first all the derivatives and transform them afterwards or you can first transform v_a1 and v_a2 and then calculate the derivatives.

Question 3:
Exactly, this is one of the boundary conditions. it is the z component of the first derivative in the starting point s_0 in the transformed coordinate system.

Question 4:
Fresnel Integrals show only up in equation 44. Until now we did not need them.

I think you are getting things confused and did steps not in the instructions. If you load firmware.bin onto the SD card the first time, it will change to firmware.cur if it loaded correctly. Your config.txt file is stored on the sdcard, it needs to remain inside the board.

if you loaded the firmware using other methods, it is possible you overwrote the bootloader in which case the firmware will not load. you might need to reinstall flash the board with bootloader, then reload the firmware.

with the stock bootloader on the octopus, all you need to do is
- put the firmware.bin on the sd card
- put config.txt on the sd card
- put sd card in octopus and leave it there
- thats it

1x Universal Stepper Controller
1x Universal PWM Controller
4x PWM Servo Amplifier
1x Spindle DAC
1x PCI-e card + cable
For specs visit: picosystems.store/shop/

 

Price: 350eur + shipping in EU (from Slovenia).
tomaz_ti1(at)hotmail.com

Alles, was ich geschrieben habe weg. (nich schön, passiert hier öfter)

Z Achse erste Anfahrt 0.03 mm danach Messuhr wieder genullt und dann bekomme ich +0.01-0.00 mm (fährt fast wieder auf 0)

Y Achse erste Anfahrt 0.02 und danach ist das immer so im Bereich +0.02-0.00 mm gelandet.

X Achse ähnlich, wie Z-Achse.+0.01-0 mm wenn die Messuhr nach der ersten Anfahrt genullt wurde.

Umkehrspiel auf der X-Achse ist 0.04 mm.

Das schockiert mich etwas, weil es viel besser als erwartet ist.

Ich habe mehrfach einfach "home all" gedrückt, so dass die Achsen aus dem Schalter fahren und sofort wieder rein.
Aber auch einige Versuche mit "Anlauf" aus 60-150 mm Entfernung habe ich gemacht. Das hatte keinen Einflusss auf die Ergebnisse.

Fazit für mich: a) "gut genug" und  b) "besser, als erwartet".

Über Hersteller, Alter, Sorte der Sensoren weiß ich nix. (gebrauchte low budget Maschine, vermutlich so um 2006-2008 )

Gruß Timo

p.s. still not convinced. ... haha.... jedenfalls muss ich da nicht ran. 
pp.s. Die Endschalter hängen am Parallelport vom Rechner, die Schrittmotoren (open loop) laufen über 6i25 mit 7i76