Advanced Search

hahaha Kam

It's intriguing how people will try to point the finger at the hardware or software rather than themselves......Yes I've been guilty of that myself, but I'm less likely to do that now, at least I hope.

I did some additional testing yesterday and found that I could never get the last hole to be a full circle unless I turned smoothing off. MergeCircles or changing tolerances did not seem to influence the end result. The sketched geometry was identical for all 4 holes. I did find a thread over on the Autodesk forum that seemed to be related to the development of this post processor.
forums.autodesk.com/t5/fusion-manufactur...le-arcs/td-p/9326368

I may reach out there if this keeps happening on other parts, but for now, I think I'll just use as is and test with other parts. If anyone else would like to use the post processor, I could remove the debug statements I added and repost it here.

I'm basing the following on the 2.9.4 image. either Rpi4 or Rpi5

If you read the man page for hal_gpio you will notice there is an issue with the way the module is loaded.

Other info:
forum.linuxcnc.org/9-installing-linuxcnc...sberry-pi-4-5#320852

In the config below you will have to change the GPIO assignments to match the Byte2Bot board.
forum.linuxcnc.org/9-installing-linuxcnc...-4-5?start=10#321296

Finally it also helps if you stated the type of Pi you are using and the image.

A word of warning if you are using a RPi5 I would pay very close attention to the temperatures, as the Byte2Bot board would inhibit the cooling. I've never run my RPi5 without the cooler.

If you are using an RPi4 you may not get the stepper speeds you want.In either case it looks like they have used a very slow base period of 100000ns. Most parallel port setups on a PC aim for around 25000ns.

For a read & write to occur the hal_gpio read & write functions need to be connected to a thread.
linuxcnc.org/docs/devel/html/drivers/hal_gpio.html#_functions

What I would do is run a basic config for your machine, then use halshow from axis or whatever you are using to monitor the input you need to.

Those Serial connectors are for Mesa's SmartSerial cards, which is different to ModBus.

There are some remote smart serial I\O cards that will be just plug and play, ie all the messy voltage translation stuff is on the board. Depends on how much you want to pay eg 7i84 which will give an extra 32 inputs & 16 outputs. Maybe over kill.
store.mesanet.com/index.php?route=produc...69_70&product_id=123

As mentioned before a chinese bob will work but then you'll have to deal with 5v > 24v stuff.

As far as I understand you can hook up one of those DB25 daughter cards to the P1 expansion connector.
Just look if something is suitable? I guess the bitfile needs to be changed. I was not able to figure that out. (so far pre-configured ones that were provided by Mesa worked for me)

store.mesanet.com/index.php?route=product/category&path=69_71

Some people used Modbus I/O expansion, I think that goes on the RS485 pins of the card. No idea how it works.

Hey chaps,

So I'm running out of outputs on my mesa 7i95t I have loads of inputs free. 

So my question is can the input pins be used as outputs?  If so how.

I have 6 ssr outputs on the card all are used for loads such as solenoids and relays.

I now need outputs (24v) for my drivers enable/alarm clearing functions.

I have ordered a 5 axis bob but it seems they are all inputs not outputs.

Any suggestions on how to get more 24v outputs? 

Thanks. Yes. This is what I have. Thank you.

Version Linux:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="www.debian.org/"
SUPPORT_URL="www.debian.org/support"
BUG_REPORT_URL="bugs.debian.org/"

Probe_Basic Version:
Stable Install: 1.1
2024-12-24 13:27:40,363 - qtpyvcp - INFO - QtPyVCP Version: 0+unknown
2024-12-24 13:27:40,390 - qtpyvcp - DEBUG - Qt Version: 5.15.8
2024-12-24 13:27:40,391 - qtpyvcp - DEBUG - Qt API: QT_API
2024-12-24 13:27:40,391 - qtpyvcp - DEBUG - QtPy Version: 2.3.0

Is this enough?