Advanced Search

Habe ich das richtig gelesen wenn alle Relais aus sind und die Spindel läuft leer aus dann hast du noch die Störung der Maus ?
Wenn ja ist das ein Ooooh….
Hast du eine Kabel Maus oder eine Funk Maus ?
Es könnte auch die Maus sein…

Jürgen

Right now I'm just looking at how Arduino-connector handles connection states. It seems that even the normal outputs don't reset when LinuxCNC is closed so things that were previously on (like LEDs) stay on. The same happens with the I2C outputs so I suppose it's expected.  Not sure if that's the intended behavior but I've trying to figure out how to reset all outputs (pull low) on disconnect. It's a bit hard to debug since there's only 1 serial connection referenced and it's taken over when LinuxCNC connects, but I have another serial port I can direct debug prints to.

Yes, I figure it is dangerous if the Arduino changes States by itself, at least if People decide to connect other things than LED Lights in Buttons to the Output pins. I implemented new settings in the new version that allows to define behaviour if the connection is lost.

Other than that it all seems to work pretty good, I found a blocking delay in the comalive function that was creating a bit of delay. I replaced that with a timer and it works much better. That plus the tweaks mentioned in the git issues, it's pretty responsive now.

Once I get done putzing around, I'll clean up my code a bit and upload it somewhere.

You can create a pull request if you want and I will merge it into the project.
 

Ich denke die Spindel. Denn wenn ich über den Maschinenzeitigen (zweiten) Start Stop Schalter die Spindel ausschalte, dann geht die Mouse. Das Relais ist dabei aber noch geschaltet, weil der Kontakt über die Mesa ja noch aktiv ist.

Man merkt auch, dass der Auslauf der Spindel weiterhin die Mouse beeinträchtigt, obwohl das Relais bspw bereits inaktiv ist. Also tippe ich stark auf die Drehbewegung der Spindel

It is crazy having such an out of date package still being the default.

Try using the buildbot at <buildbot2.highlab.com> 

Es ist die Frage erzeug das Relais das die Spindel einschaltet ( Hauptrelais ) die Störung oder ist es der Spindelmotor
Oder ist es das 12 V Relais.
Da muss man sich Stück für Stück durch hangeln.
Ich hatte auch letztens ein Problem mit ein Monitorkabel an mein Plasmatisch in der Testphase war alles gut jetzt musste das Kabel länger sein ein neues gekauft bein zünden des Brenners Monitor Schwarz zurück getauscht alles gut andres Kabel diesmal vom Hersteller des  zu kurzen Kabel gekauft alles gut.
Das mit den N kommt nur in einigen Teillen von Europa vor wo die L Position an der Steckdose nicht definiert ist zb ein. US Stecker geht nur in der eine Richtung das ist auch einer der Punkte warum in Caravan Sektor der Cee Stecker Blau 240 Vorgeschrieben ist der L und N ist definiert das mal
zur Info.

Juergen

Thanks Phil,

I'm using the latest version from Synaptic Package Manager

I have tried to get 2.9.2 & 2.9.3 to load from usb, but i'm not having any luck with this.

About to enter the build bot rabbit hole.

Cheers

As much as we had a difference of opinion our work flow seems to be on similar lines.

Now that the RPI5 has a driver suitable for the 7c81, it’s time to see if this BSPI thing works on the clone I put together.
I’ll use your thread as a reference, print out some of the man pages, 7i65 code, some data sheets and get the highlighters out. I guess a I’ll have to build the bit file as well.

Has anyone been able to get the position of the servo motor via modbus and then do the homing operation?

But I get the error

What error?

Test

I installed via USB:
www.linuxcnc.org/iso/linuxcnc_2.9.3-amd64.hybrid.iso
linux distribution Debian 12

Following errors:
qttools5-dev-tools not available
qttools5-dev can`t be found
libpython3-dev can`t be found

Cant do this anymore bye all wrote:

Nice setup old chap, puts my merger efforts at PCB design to shame.

I remember there was a thread about the BSPI thing, tried searching but couldn't find it.
 

Yeah I make plenty of PCBs, I tend to make one or two revisions, get everything working, and then stuff it on the shelf because I stop working on whatever it was mean for.

That one was for a pick and place machine I made that I wanted to get working with OpenPnP on top of LinuxCNC. I did get it moving around but I was having too much trouble getting both OpenPnP and LinuxCNC to play nice......so on the shelf it went. I don't really have the attention span to try to get LinuxCNC fully integrated for a PnP by itself but I'm sure it can be done, the guy who does the Mitsubishi servo cards managed to do it.

These break out boards intended for Arduino Connector have probably been sitting around for like a year now. Had to bodge out a couple of mistakes on both the Mega and Teensy 4.1 versions but it'll be good enough to get my control panel finally working. Then I'll go back and make a (hopefully) final revision.

AlexMagToast wrote:

I like the I2C IO expansion Idea. I don't have these chips here yet. As I am working on the next Version of Arduino Connector I would implement it in the newer version as it will improve on all the Issues learned from the current version, as it will also get rid of the #defines etc for the user.
Also I forgot to mention that the new Version already supports the connection to multiple Arduinos simultaneously.

If you would like to peek into it you can see it on Github in the dev branch, but keep in mind currently it doesn't work.
Here is a preview of how the new Yaml configuration looks like: github.com/AlexmagToast/LinuxCNC_Arduino...lob/dev/config2.yaml


 

Yeah I've seen the v2 but never tried it because it's mentioned in the repo that it doesn't currently work.

I got my Teensy 4.1 break out board working and that handles the encoders much better than the Arduino Mega. The Teensy doesn't have that many IO pins so I have an I2C expander right on the break out board in addition to the 4 expanders on the keypad, I've got that working too.

I'm using MCP23017 expanders on these but I've used PCF857x on other boards, they aren't pin compatible but the libraries are similar.

Right now I'm just looking at how Arduino-connector handles connection states. It seems that even the normal outputs don't reset when LinuxCNC is closed so things that were previously on (like LEDs) stay on. The same happens with the I2C outputs so I suppose it's expected.  Not sure if that's the intended behavior but I've trying to figure out how to reset all outputs (pull low) on disconnect. It's a bit hard to debug since there's only 1 serial connection referenced and it's taken over when LinuxCNC connects, but I have another serial port I can direct debug prints to.

Other than that it all seems to work pretty good, I found a blocking delay in the comalive function that was creating a bit of delay. I replaced that with a timer and it works much better. That plus the tweaks mentioned in the git issues, it's pretty responsive now.

Once I get done putzing around, I'll clean up my code a bit and upload it somewhere.