Advanced Search

Basic homing and CW/CW rotation indexing working fine now!
Altough it responds with a small delay (due to the stepgen PCB)

Some vids:






Next step is mapping and wiring the other sensors!
 

tommylight wrote:

No, not yet.
Now is that point where you upload your configuration files here so we can have a look, joint errors are usually miss configuration on stepper systems.
What board are you using?

Hi tommylight, have you seen my configuration? is a default conf.

Hi everyone,I'm using QtDragon and a joystick (via) to jog my machine. Jogging works fine with a costant speed, but I’d like to adjust the jog speed using two buttons — one to increase and one to decrease the speed. (like the slider in the Qtdragon gui)
 

bigmactx wrote:

Sorry so slow but massive interruptions and a few train wrecks to clean up...

I have the 7i95t working completly now and would like to share what I've learned about getting this board to work with linuxcnc 2.10pre. MesaCT tool 2.1.7 doesn't currently support the 7i95t
 

I just ran MesaCT 2.1.7 and pressed two buttons and created a working configuration for a 7i95T.





JT

Pcw,

Thanks again for your effort.

What do you advise at this moment?
You can tune the planner with scurve jerk value in the hal section. This changes the accelation profile.
This jerk value is not integrated to the .ini file so far.

I assume you could tune your ini config to run without following error? Or is this not the case?

Indeed if you set acceleration to 200, the scurve max acceleration will be 400 at inflection point.
Exceeding your max acc off 240.

I don't use remote desktop. I did a test with three working youtube videos

Thanks for your quick reply.

I haven't changed any drive parameters.

Since i am new to Servo tuning, its quite confusing to conclude, whatever i am doing is correct or not. Now i have a fundamental question,

With the above setup is it possible to achieve 15,000 mm/min feedrate within 20 micron positional accuracy and +- 20 micron repeatability? I doubt whether the control loop is fast enough to reach this speed and accuracy ?

I think this will solve the issue:
Will try today!
 

 

Looks like it is missing a value for the OFFSET_AV_RATIO variable, doesn't it? Should be 0.5 I think but check the QtPlasmaC docs.

Thank you for the quick reply.

The log you shared is from the Python script, but the important part happens on the EC300 board side.
Could you connect an RS232 interface and check the board's response when receiving the new configuration?

Thanks

I think the last time I tried to update to GTK+3, a bunch of the components no longer existed, like HAL_HideTable. Where do those come from?

Anyways, the basic functionality is working.
I still have to wire up and map the ATC spindle PNP sensors to detect clamping / unclamping and the sensors for the out position of the Carousel cylinder, before I can try to run a toolchange. But that should work out fine.
Once everything is working, I'll do a writeup how it's configured.

Allright!!!! Got the carousel working! Or atleast I can control and home it from the Probe Basic Gui and index it as well, altough I had to struggle a bit.

It's setup with the step generator PCB + 2 relays and two optical sensors.

- Had to figure out how to wire the relays in a way that both carousel directions were switching the "ON/OFF" circuit on the small stepgen PCB, but only 1 direction / relay would close the DIR circuit.
- Had to change 1 parameter in the M13 homing subroutine (P4 to P3), seems to be a typo.
- Had to configure the Index signal with AND2 logic for the M13 homing subroutine, so it looks for both the Index and the Pulse sensors during homing.
- Had some trouble with my NPN optical sensors, because I thought my Mesa 7i84 daughtercard was using NPN, while in reality I needed PNP.  

One problem, the drive wheel sensor flag overshoots the sensor by about 25 degrees during homing and index steps.
So when you home or index the carousel, the flag is passing the sensor completely due to deceleration it seems.
The result is if the follow up index movement is in the opposite direction, the flag gets detected after turning back only 25 degrees, with the physical carousel not stepping an index position, while the software does register +1 index pocket.
Not sure I can change decel with the stepgen PCB setup.

Two options to solve I think:
1- Create a longer flag on the drivewheel, so more like a lobe, which allows some more margin
2- Replace the drive wheel index sensor for a pulse flag on each pocket. The decel timing will give the geneva drive pin enough time to move out of the slot and properly engage.

Will try option 1 first, as I can just print a new disc with a longer flag.

 

Are you sure the probe_basic config folder doesn't get updated when you run those commands?

I was looking at the wrong machine folder initially, because I made a copy of probe_basic base folder when I first installed it.

Python gives very unhelpful errors and traceback.

+1 for Java!

Did ya try the wizard?