#linuxcnc-devel Logs
Nov 27 2022
#linuxcnc-devel Calendar
12:49 AM linuxcnc-build2: Worker `checkin` is missing. It was seen last on Sat Nov 26 22:47:22 2022.
01:28 AM pere: btw, why do people like classicladder? it is like a visual and slow way to do what can more easily be done using logic operations with HAL instructions.
03:29 AM Tom_L: pere, they use ladder logic on alot of industrial equipment
03:32 AM Tom_L: https://www.watelectronics.com/how-to-program-the-programmable-logic-controllers/
03:32 AM pere: yes, but why?
03:33 AM Tom_L: if i had to guess, years ago things were done with relays & switches
03:34 AM Tom_L: Ladder logic began as a method to document the design and construction of relay racks as used in manufacturing and process control. Relay racks are storage systems that are used for networking and communications equipment, and were popularly used prior to the 2000s.
03:36 AM pere: Tom_L: perhaps you can have a look at the test branch I created and let me know if it actually is testing the ladder code?
03:36 AM pere: I can help you run the test if you want to.
03:36 AM Tom_L: jt is the ladder logic expert
03:37 AM Tom_L: he'll be awake in a couple hrs
03:37 AM Tom_L: i shouldn't be awake yet either :)
03:45 AM Tom_L: pere, some old relays removed from elevator equipment: http://tom-itx.no-ip.biz:81/~webpage/rue/electronics/Relay1.jpg
05:09 AM pere: :)
06:20 AM pere: Tom_L: I hope jt can help review the test, to get the classicladder upgrade moving.
06:22 AM pere: JT-Cave: do you have time to review <URL: https://github.com/LinuxCNC/linuxcnc/pull/2156 >?
06:37 AM -!- #linuxcnc-devel mode set to +v by ChanServ
06:44 AM pere: I JT-Cave are you the ladder logic expert?
06:45 AM JT-Cave: I am good at ladder yes
06:46 AM pere: JT-Cave: I am trying to write a test script to ensure the classicladder stuff work in linuxcnc, in preparation to applying the upgraded classicladder implementation, but do not really know much about classicladder. I got a somewhat working test, but is unsure if it is testing what I want, ie some classicladder functionallity, and not just generic linuxcnc stuff.
06:46 AM pere: The code in question is in <URL: https://github.com/LinuxCNC/linuxcnc/pull/2156 >.
06:47 AM pere: I tried to modify the ladder setup, changing an active when closed unit to an active when open, expecting it to break the test, but the test still was successful. I thus do not quite know if I am testing the wrong thing.
06:47 AM JT-Cave: what am I looking at?
06:48 AM JT-Cave: what are you trying to test?
06:48 AM JT-Cave: yuck in 30 seconds I have to go out in the cold rain and open the chicken doors...
06:49 AM pere: the test is triggered by running test.sh. It will start linuxcnc with a simple (copied) setup and a estop setup in classicladder. the classicladder-ui.py script try to flip a pin and see the effect.
06:49 AM pere: JT-Cave: the chicks probably want to stay out of the rain too. :)
06:52 AM JT-Cave: I checked out your branch but I'm running into an endless amount of errors and dependencies trying to run configure even though linuxcnc is installed on this pc
06:54 AM pere: you do not have to configure it, just cd tests/classicladder/estop && ./test.sh
06:55 AM JT-Cave: john@cave:~/git/emc/tests/classicladder/estop$ ./test.sh
06:55 AM JT-Cave: LINUXCNC - 2.9.0~pre0+git20221105.ffb6bda926
06:55 AM JT-Cave: Machine configuration directory is '/home/john/git/emc/tests/classicladder/estop/.'
06:55 AM JT-Cave: Machine configuration file is 'classicladder-estop.ini'
06:55 AM JT-Cave: Starting LinuxCNC...
06:55 AM JT-Cave: linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
06:55 AM JT-Cave: Note: Using POSIX realtime
06:55 AM JT-Cave: Found file(lib): /usr/share/linuxcnc/hallib/core_sim.hal
06:55 AM JT-Cave: Found file(REL): ./classicladder-estop.hal
06:55 AM JT-Cave: creating ladder-state
06:55 AM JT-Cave: INFO CLASSICLADDER- No ladder GUI requested-Realtime runs till HAL closes.
06:55 AM JT-Cave: Found file(lib): /usr/share/linuxcnc/hallib/simulated_home.hal
06:55 AM JT-Cave: link (updating variable file): No such file or directory
06:55 AM JT-Cave: task: main loop took 0.125298 seconds
06:56 AM JT-Cave: task: main loop took 0.121222 seconds
06:56 AM JT-Cave: task: main loop took 0.182261 seconds
06:56 AM JT-Cave: exiting linuxcnc
06:56 AM JT-Cave: Shutting down and cleaning up LinuxCNC...
06:56 AM JT-Cave: task: 63 cycles, min=0.000005, max=0.182261, avg=0.015834, 3 latency excursions (> 10x expected cycle time of 0.010000s)
06:56 AM JT-Cave: Note: Using POSIX realtime
06:56 AM pere: look good.
06:56 AM pere: if echo $? show 0, the test succeeded.
06:56 AM JT-Cave: I have no idea what I'm looking at
06:57 AM pere: it is just random strings printed by linuxcnc components. nothing relevant, except perhaps 'exiting linuxcnc' which is from the end of classicladder-estop-ui.py when it completed the test.
06:57 AM JT-Cave: john@cave:~/git/emc/tests/classicladder/estop$ echo $?
06:57 AM JT-Cave: 0
06:57 AM JT-Cave: so what does this have to do with me and using classicladder?
06:58 AM pere: test.sh starts linuxcnc with the ini file, the ini file load HAL stuff and run classicladder-estop-ui.py, which flip some hal pins to try to exercise the classicladder setup hooked up into hal.
06:58 AM pere: I do not know if this code actually exercise the classicladder setup, in other words, if the test is testing what I hope it is testing.
06:59 AM pere: any idea how I can verify this?
07:00 AM JT-Cave: nope, not a clue... I've never messed with tests
07:00 AM pere: I got the test part under control, it is the plc stuff I do not understand.
07:02 AM pere: if you look at classicladder-estop-ui.py, the h['ext-estop-button'] = 1 statement set the ext-estop-button high in HAL. I hope and believe this should tell the classicladder setup to enter estop, and that this will cause the estop-all-ok pin to go low. But am not sure if it can go low even if classicladder is broken.
07:02 AM JT-Cave: damn debian 12 is so screwed up atm with gtk and jumbled up fonts I'm ready to ditch it and try something else
07:03 AM pere: I believe I use lxde with my debian 12 linuxcnc host. never been a gnome fan.
07:05 AM JT-Cave: this is mate]
07:07 AM pere: isn't that gnome forked when some gnome users were unhappy with the main project direction?
07:07 AM JT-Cave: no clue
07:09 AM pere: sadly I do not know enough plc to understand what is going on, and when I try to modify the plc setup the test still work, but I do not know if I modify some vital part or just some irrelevant and redundant part.
07:20 AM JT-Cave: I have no clue what's going on it that test
07:21 AM pere: do you understand the clp and hal file?
07:27 AM pere: ah, by removing wires instead of modifying the inputs, I managed to get the test failing by changing the plc setup.
07:30 AM JT-Cave: I don't modify classicladder by editing a clp file]
07:31 AM pere: me neither. I edit the hal file and remove the --nogui option.
07:32 AM JT-Cave: right now I can't even open a configuration with the configuration selector there is no open button
09:57 AM JT-Shop22 is now known as JT-Shop2
10:09 AM pere: seb_kuzminsky: any idea what more I should to do verify the test is ok?
10:09 AM pere: cutting "wires" in the plc program broke the test, making me believe it is actually testing classicladder.
11:13 AM -!- #linuxcnc-devel mode set to +v by ChanServ
11:35 AM JT-Shop is now known as JT-Cave
11:46 AM linuxcnc-build2: Build [#6](http://buildmaster-2.local:8010/#builders/12/builds/6) of `03-dsc-uspace.debian-11-bullseye` 8completed with warnings.
12:25 PM linuxcnc-build2: Build [#15](http://buildmaster-2.local:8010/#builders/3/builds/15) of `01-rip.debian-10-buster-rtpreempt-amd64` 4failed.
01:01 PM linuxcnc-build2: Build [#16](http://buildmaster-2.local:8010/#builders/3/builds/16) of `01-rip.debian-10-buster-rtpreempt-amd64` 8completed with warnings.
01:04 PM linuxcnc-build2: Build [#2](http://buildmaster-2.local:8010/#builders/15/builds/2) of `03-dsc-uspace.debian-10-buster` 8completed with warnings.
01:12 PM linuxcnc-build2: Build [#16](http://buildmaster-2.local:8010/#builders/6/builds/16) of `00-checkin` 3completed successfully.
04:35 PM pere: Is there a chance to fix <URL: https://github.com/LinuxCNC/linuxcnc/issues/1146 > in 2.9?
04:55 PM linuxcnc-build: build #2784 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/2784 blamelist: Petter Reinholdtsen <pere@hungry.com>, andypugh <andy@bodgesoc.org>
04:55 PM linuxcnc-build: build #9427 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9427 blamelist: Petter Reinholdtsen <pere@hungry.com>, andypugh <andy@bodgesoc.org>
05:03 PM pere: hm, the runtest log from <URL: http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/2784 > show the new test failing, but I have no idea what is going on.
05:04 PM pere: andypugh: any clue to spare?
05:04 PM pere: look like this build require more .ini settings than the uspace one?
05:06 PM JT-Cave: pere, is the new classicladder in master now?
05:09 PM andypugh: Hmm, Hard to say what is going on there. Might need to be tested with an actual Pi4
05:13 PM pere: JT-Cave: no. only my test.
06:37 PM linuxcnc-build: build #2625 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/2625 blamelist: CMorley <chrisinnanaimo@hotmail.com>, Petter Reinholdtsen <pere@hungry.com>, Hans Unzner <hansunzner@gmail.com>, andypugh <andy@bodgesoc.org>
06:54 PM seb_kuzminsky: the new classicladder test fails on rpi4, and leaves behind ipc objects that cause subsequent invocations of linuxcnc to fail
06:54 PM seb_kuzminsky: i've disabled it until someone debugs it
06:55 PM andypugh: I blame me for trusint pere :-)
06:55 PM andypugh: (er, that should say “trusting”. I was sat at a funny angle to the keyboard)
07:00 PM seb_kuzminsky: i wish the buildbot would build PRs, even though if the source is not in the main linuxcnc git repo
07:01 PM Tom_L: can't seem to get my test buildbot to push a deb
07:01 PM Tom_L: taking a break from it a while i think
07:46 PM seb_kuzminsky: ugh and the qtvcp docs broke
08:22 PM -!- #linuxcnc-devel mode set to +v by ChanServ
08:23 PM linuxcnc-build: build #3027 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3027 blamelist: CMorley <chrisinnanaimo@hotmail.com>, Petter Reinholdtsen <pere@hungry.com>, Hans Unzner <hansunzner@gmail.com>, andypugh <andy@bodgesoc.org>
09:28 PM linuxcnc-build2: Worker `checkin` is missing. It was seen last on Sun Nov 27 19:26:24 2022.
10:01 PM linuxcnc-build: build #2786 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/2786 blamelist: CMorley <chrisinnanaimo@hotmail.com>, Petter Reinholdtsen <pere@hungry.com>, Hans Unzner <hansunzner@gmail.com>, andypugh <andy@bodgesoc.org>
10:01 PM linuxcnc-build: build #9429 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9429 blamelist: CMorley <chrisinnanaimo@hotmail.com>, Petter Reinholdtsen <pere@hungry.com>, Hans Unzner <hansunzner@gmail.com>, andypugh <andy@bodgesoc.org>
10:17 PM linuxcnc-build: build #2626 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/2626 blamelist: Sebastian Kuzminsky <seb@highlab.com>, Peter Wallace <pcw@mesanet.com>
10:30 PM linuxcnc-build: build #3028 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3028 blamelist: Sebastian Kuzminsky <seb@highlab.com>, Peter Wallace <pcw@mesanet.com>
10:32 PM -!- #linuxcnc-devel mode set to +v by ChanServ
10:49 PM linuxcnc-build: build #2787 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/2787 blamelist: Sebastian Kuzminsky <seb@highlab.com>, Peter Wallace <pcw@mesanet.com>
10:49 PM linuxcnc-build: build #9430 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9430 blamelist: Sebastian Kuzminsky <seb@highlab.com>, Peter Wallace <pcw@mesanet.com>