Advanced Search

Yeah, I was already doing that with the other NC contact from the estop to the Mesa input and tied into the estop-latch logic in hal.

Thanks a lot. 
Cheers,
Mark

I don't need them, this post was a continuation of a previous post on the subject of adding a second Y axis to my machine. But PCW has answered my question so finding the previous post is a not necessary.

Thx,

#1 to #30 are used to send variables to a called subroutine, so them are not writeable in the sub. If names given from #31 up, it should work

I can't advise on whether there are Mesa cards which can work directly with the Heidenhain scales. EXE610C units are cheap on eBay here, so I purchased 3 for my FP2NC conversion. Meridian Measurement Systems has a newer converter product, which I suspect is based on the iC-Haus iC-NV chip:

meridianmeasurement.com/sa/
www.ichaus.de/product/iC-NV/

I plan to use a 6i25 and 7i77 Mesa Plug-N-Go kit, which I already had on hand. The conversion isn't finished yet.

Sorry got distracted over the holidays.

So I made your recommended change to the glade file and it did not work. see screenshot

any more suggestions?

thank you as always
 

If you wish to test the inputs, disconnect all external devices from the inputs
and test each input by connecting it to field power (+24V in your case)
Note the touching the screw on the connector is not reliable unless the screw is tight

If the NPN limit switch outputs are not very close to ground in one state,
you still have a wiring error.

Hi Guys,

I must have an endless loop in this program, as LCNC hangs as soon as I load it. 
I have been through it twice, and can't see my error.

The first loop starts at X-4, and loops as it increments up in 8mm steps across to X52, while the second loop starts at Z30, and increments down in 6mm steps, until reaching Z0.

Without LCNC calling the error, may I please request you check this and let me know what I have screwed up, as I can't see it?
Thanks.
Mark
 

scsmith1451 wrote:

Also, what happened to my previous topics? Are they automatically purged with a new year? 

No they are not.
Do you recall the tittle or some exact part of the content or section of the forum or anything that might help find it?
Usually they can be restored, if not permanently deleted.

I rewired my psu input from psu > wagos > mesa input > field to psu > mesa > field > wagos but no change sadly.

Oddly enough, I can jump between gnd and input pins 13 and 12 and get a change of state using showpin, but nothing down to pin 8. And thats without a resistor on any input except for 8.

AFAIK, in pncconf a tandem axis simply duplicates the the primary axis
(with a different stepgen and joint position command) so any differences
(like a reversed direction) would need to be done by editing
the hal or ini file.

Cant try anything at the moment, but thats sweet. you have any examples of it in use? (even sims)

Hi All;

I finally have the second Y Axis installed on my machine and was trying to configure it.  I'm using a MESA i76u board. When I started pncconf, I selected to modify my existing single Y axis configuration since it worked beautifully. I increased the number of Step/Dir channels to 5 as my machine was currently configured for a 4th rotary axis.

On the Axis configuration page I set the 5th Step/Dir configuration to Y2 Tandem, and on the P3 pin configuration page I added the input for the Y2 Tandem Both Limit & Home. I moved through the X Motor config as it was already working correctly to the Y Motor configuration which I verified till worked as expected. I expected the Y2 Motor to be the next configuration page, however pncconf proceeded to the Z, then A axes with no page to configure Y2.

Did I miss something earlier in the config process that would generate a configuration for Y2? Perhaps I needed to set the machine configuration to xyyza or xyy2za or something akin to it? 

A little help would be greatly appreciated.

Also, what happened to my previous topics? Are they automatically purged with a new year? 

Regards and happy New Year

rodw wrote:

JT wrote:

Also note that there is no /etc/apt/sources.list.d/debian.sources in my Debian 13 after doing a full upgrade.

JT
yes the old format is retained on a full upgrade from Bookworm but it will nag you on an apt update to run sudo apt modernize-sources if I got the spelling right...

Debian says the old format will be removed in time.
 

This was an upgrade of Debian 13 not 12.

JT

Those voltage values indicate a wiring issue.

With NPN sensors, one state should be very close to GND  (<1V)
How high the voltage is in the other state depends on the pullup resistance
which may be infinite (no pullup) or some intermediate voltage depending on the
pullup resistance (some NPN proximity switches have built in weak pullups)

Because the low levels are not close to GND, it sounds like the the NPN proximity
switch common is not connected to the field power common.