Java UI for linuxcnc
10 Aug 2021 13:48 #217398
by Reinhard
I compiled the java stuff with v8 compatibility, so any jre available in decent os will do the job.
My app worked on jessie, buster and it works on bullseye as well. It worked with linuxcnc before 2.8 was released and it works with current master-gtk3 (python3).
.
That's the nature of open source. You can do what you want, as long as you mention me as original author.
But - I won't accept any push request regarding kotlin, gradle, maven or whatever tools that will bloat my harddisk. I did not use gradle by intention and don't wonna use it at all.
I'm fine with the stuff I created and the tools I used.
If you like my work, you can use it - if you don't like it, you don't have to use it.
Its a free world
I would have appreciated a little feedback about whether you got your copy working - after all that struggling. But you're free not to give any feedback at all.
Replied by Reinhard on topic Java UI for linuxcnc
my app has no os dependencies at all. As soon as you have a working copy of linuxcnc, my app will be working. You only need a jre - nothing more.What Debian version do you have installed?
I compiled the java stuff with v8 compatibility, so any jre available in decent os will do the job.
My app worked on jessie, buster and it works on bullseye as well. It worked with linuxcnc before 2.8 was released and it works with current master-gtk3 (python3).
.
Why should I?I hope you have not felt offended by the fact that I said that I wanna take your project into another direction by using kotlin.
That's the nature of open source. You can do what you want, as long as you mention me as original author.
But - I won't accept any push request regarding kotlin, gradle, maven or whatever tools that will bloat my harddisk. I did not use gradle by intention and don't wonna use it at all.
I'm fine with the stuff I created and the tools I used.
If you like my work, you can use it - if you don't like it, you don't have to use it.
Its a free world
I would have appreciated a little feedback about whether you got your copy working - after all that struggling. But you're free not to give any feedback at all.
Please Log in or Create an account to join the conversation.
10 Aug 2021 15:28 #217406
by Reinhard
Replied by Reinhard on topic Java UI for linuxcnc
Hi Vasi,
well, first of all try to get your linuxcnc working.
When you compiled a rip-installation successfully, the rest should be a bit of nothing
Just to clarify: hal means hardware abstraction layer - I have no plans to directly access any hardware. linuxcnc does it good enuf. Anything is possible. Shortcomings of linuxcnc are NOT hardware related. All the bad is in software
cheers Reinhard
well, first of all try to get your linuxcnc working.
When you compiled a rip-installation successfully, the rest should be a bit of nothing
No, all halapps run natively from linux commandline. I don't see any need or benefit in calling those apps from java environment. I did some tests with accessing hal from java - it was possible, but I abandoned that idea, as I have no need for direct hal access.I have a question: from your app can you open the already existent utility apps like halscope, hal configuration, etc that the Axis or Gmoccapy are opening for setting up the linuxcnc machine configuration?
Just to clarify: hal means hardware abstraction layer - I have no plans to directly access any hardware. linuxcnc does it good enuf. Anything is possible. Shortcomings of linuxcnc are NOT hardware related. All the bad is in software
cheers Reinhard
Please Log in or Create an account to join the conversation.
16 Aug 2021 14:10 #217886
by Reinhard
Finally you got it
you had a binary from a former installation.
This can't work.
So if you (re)compile linuxcnc, you should run a "make clean" first of all.
Then - if you issue a "make TestNML" only the test-app will be build.
That means, you can't start the java app without having built the library (just "make").
TestNML is an app to test the NML communication. So it serves to check your build environment, as well as to check NML-connection.
So start linuxcnc with axis (without any UI-action in axis) and then start TestNML.
Axis should turn on and home all axis.
If that works, you can continue with the library.
Cheers Reinhard
Replied by Reinhard on topic Java UI for linuxcnc
Congratulation!and just to make sure, I ran the linuxcnc tests witch ran fine.
Finally you got it
Oh man!make TestNML
make: 'TestNML' is up to date.
you had a binary from a former installation.
This can't work.
So if you (re)compile linuxcnc, you should run a "make clean" first of all.
Then - if you issue a "make TestNML" only the test-app will be build.
That means, you can't start the java app without having built the library (just "make").
TestNML is an app to test the NML communication. So it serves to check your build environment, as well as to check NML-connection.
So start linuxcnc with axis (without any UI-action in axis) and then start TestNML.
Axis should turn on and home all axis.
If that works, you can continue with the library.
Cheers Reinhard
Please Log in or Create an account to join the conversation.
16 Aug 2021 19:55 #217913
by vmihalca
Replied by vmihalca on topic Java UI for linuxcnc
That message with was because I previously ran make TestNML
This installation was a clean debian, without any version of linuxcnc installed. So the only install that I have is the one built from master-gtk3 branch.
After reading your last message I was more enlightened a bit so I did the following:
1. in JCNCScreen folder -> ant clean, then ant dist
2. in another terminal window, opened linuxcnc, with a default configuration (axis UI window estopped)
3. switched to native folder then ran ./TestNML which took the Axis UI out of estop, powered on the machine, then homed the machine.
4. Then I navigated into the runtime folder and tried to run the app:cnc@mindovercnc:~/Work/JCNCScreen$ cd runtime/
cnc@mindovercnc:~/Work/JCNCScreen/runtime$ java -Djava.library.path=.:./lc/lib -splash:lc/linuxcnc.gif -jar JCNCScreen.jar -base ./exHdr
local check: AppTitle == > JCNCScreen - frontend for linuxCNC <
current directory: /home/cnc/Work/JCNCScreen/runtime/.
populateTree ...
read ToolTable ...
Exception in thread "main" java.lang.UnsatisfiedLinkError: no nml in java.library.path: [., ./lc/lib]
at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2670)
at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:830)
at java.base/java.lang.System.loadLibrary(System.java:1873)
at de.schwarzrot.system.ErrorReader.<clinit>(Unknown Source)
at de.schwarzrot.app.LinuxCNCClient.<init>(Unknown Source)
at de.schwarzrot.app.LinuxCNCClient.main(Unknown Source)
Its kinda wierd that TestNML can interact with linuxcnc properly, but this one cannot.
If you notice something that I might be missing, please let me know!
Thanks for your help!
make: 'TestNML' is up to date.This installation was a clean debian, without any version of linuxcnc installed. So the only install that I have is the one built from master-gtk3 branch.
After reading your last message I was more enlightened a bit so I did the following:
1. in JCNCScreen folder -> ant clean, then ant dist
2. in another terminal window, opened linuxcnc, with a default configuration (axis UI window estopped)
3. switched to native folder then ran ./TestNML which took the Axis UI out of estop, powered on the machine, then homed the machine.
4. Then I navigated into the runtime folder and tried to run the app:cnc@mindovercnc:~/Work/JCNCScreen$ cd runtime/
cnc@mindovercnc:~/Work/JCNCScreen/runtime$ java -Djava.library.path=.:./lc/lib -splash:lc/linuxcnc.gif -jar JCNCScreen.jar -base ./exHdr
local check: AppTitle == > JCNCScreen - frontend for linuxCNC <
current directory: /home/cnc/Work/JCNCScreen/runtime/.
populateTree ...
read ToolTable ...
Exception in thread "main" java.lang.UnsatisfiedLinkError: no nml in java.library.path: [., ./lc/lib]
at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2670)
at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:830)
at java.base/java.lang.System.loadLibrary(System.java:1873)
at de.schwarzrot.system.ErrorReader.<clinit>(Unknown Source)
at de.schwarzrot.app.LinuxCNCClient.<init>(Unknown Source)
at de.schwarzrot.app.LinuxCNCClient.main(Unknown Source)
Its kinda wierd that TestNML can interact with linuxcnc properly, but this one cannot.
If you notice something that I might be missing, please let me know!
Thanks for your help!
Please Log in or Create an account to join the conversation.
17 Aug 2021 02:14 #217942
by Reinhard
Replied by Reinhard on topic Java UI for linuxcnc
@phillc54
Thank you very much for that info
.
You can check it with "ls -l ./lc/lib/libnml.so"
May be you forgot to create the link lc to linuxcnc installation?
Thank you very much for that info
.
That's a different error from the ones before and it tells, that libnml.so is not found in library path.java.lang.UnsatisfiedLinkError: no nml in java.library.path
You can check it with "ls -l ./lc/lib/libnml.so"
May be you forgot to create the link lc to linuxcnc installation?
Please Log in or Create an account to join the conversation.
Time to create page: 0.092 seconds