#jmri — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jmri, aggregated by home.social.
-
#Tech post! #Today I finally found time to remove #Fedora from my #Linux laptop. I had intended to replace it with #MXLinux - in fact for a couple of hours I did - but in the end I had so many problems customising #KDE #Plasma that I actually stopped and had a rethink.
I had always liked Plasma for its customisability, but wrestling with panel configuration seems to be getting harder - or I'm getting older - and I just couldn't get the desktop how I wanted it. After 2 hours I realised life was too short for such nonsense.
I needed a polished distro with fractional scaling on #HiDPI displays, and after some research to get me up to date, I plumped for #Pop_OS with its #COSMIC desktop.
Pop_OS is great - it has a solid #Ubuntu base and the UI feels far more consistent and robust than either KDE or #Gnome - but my essential #Java app, the #JMRI #ModelRailway control software, looked awful at any scale. Jagged fonts, boxes overflowing, etc.
After a lot of searching I found a shell command to force font anti-aliasing for old Java apps (comment if you need a link to the Gist), and with a few more tweaks finally all was well.
Pop_OS, like MX Linux, seems to be AI-neutral rather than overtly AI-positive like Fedora, so I've achieved my original goal, even if it took me in an unexpected direction.
-
#Tech post! #Today I finally found time to remove #Fedora from my #Linux laptop. I had intended to replace it with #MXLinux - in fact for a couple of hours I did - but in the end I had so many problems customising #KDE #Plasma that I actually stopped and had a rethink.
I had always liked Plasma for its customisability, but wrestling with panel configuration seems to be getting harder - or I'm getting older - and I just couldn't get the desktop how I wanted it. After 2 hours I realised life was too short for such nonsense.
I needed a polished distro with fractional scaling on #HiDPI displays, and after some research to get me up to date, I plumped for #Pop_OS with its #COSMIC desktop.
Pop_OS is great - it has a solid #Ubuntu base and the UI feels far more consistent and robust than either KDE or #Gnome - but my essential #Java app, the #JMRI #ModelRailway control software, looked awful at any scale. Jagged fonts, boxes overflowing, etc.
After a lot of searching I found a shell command to force font anti-aliasing for old Java apps (comment if you need a link to the Gist), and with a few more tweaks finally all was well.
Pop_OS, like MX Linux, seems to be AI-neutral rather than overtly AI-positive like Fedora, so I've achieved my original goal, even if it took me in an unexpected direction.
-
#Tech post! #Today I finally found time to remove #Fedora from my #Linux laptop. I had intended to replace it with #MXLinux - in fact for a couple of hours I did - but in the end I had so many problems customising #KDE #Plasma that I actually stopped and had a rethink.
I had always liked Plasma for its customisability, but wrestling with panel configuration seems to be getting harder - or I'm getting older - and I just couldn't get the desktop how I wanted it. After 2 hours I realised life was too short for such nonsense.
I needed a polished distro with fractional scaling on #HiDPI displays, and after some research to get me up to date, I plumped for #Pop_OS with its #COSMIC desktop.
Pop_OS is great - it has a solid #Ubuntu base and the UI feels far more consistent and robust than either KDE or #Gnome - but my essential #Java app, the #JMRI #ModelRailway control software, looked awful at any scale. Jagged fonts, boxes overflowing, etc.
After a lot of searching I found a shell command to force font anti-aliasing for old Java apps (comment if you need a link to the Gist), and with a few more tweaks finally all was well.
Pop_OS, like MX Linux, seems to be AI-neutral rather than overtly AI-positive like Fedora, so I've achieved my original goal, even if it took me in an unexpected direction.
-
#Tech post! #Today I finally found time to remove #Fedora from my #Linux laptop. I had intended to replace it with #MXLinux - in fact for a couple of hours I did - but in the end I had so many problems customising #KDE #Plasma that I actually stopped and had a rethink.
I had always liked Plasma for its customisability, but wrestling with panel configuration seems to be getting harder - or I'm getting older - and I just couldn't get the desktop how I wanted it. After 2 hours I realised life was too short for such nonsense.
I needed a polished distro with fractional scaling on #HiDPI displays, and after some research to get me up to date, I plumped for #Pop_OS with its #COSMIC desktop.
Pop_OS is great - it has a solid #Ubuntu base and the UI feels far more consistent and robust than either KDE or #Gnome - but my essential #Java app, the #JMRI #ModelRailway control software, looked awful at any scale. Jagged fonts, boxes overflowing, etc.
After a lot of searching I found a shell command to force font anti-aliasing for old Java apps (comment if you need a link to the Gist), and with a few more tweaks finally all was well.
Pop_OS, like MX Linux, seems to be AI-neutral rather than overtly AI-positive like Fedora, so I've achieved my original goal, even if it took me in an unexpected direction.
-
#Tech post! #Today I finally found time to remove #Fedora from my #Linux laptop. I had intended to replace it with #MXLinux - in fact for a couple of hours I did - but in the end I had so many problems customising #KDE #Plasma that I actually stopped and had a rethink.
I had always liked Plasma for its customisability, but wrestling with panel configuration seems to be getting harder - or I'm getting older - and I just couldn't get the desktop how I wanted it. After 2 hours I realised life was too short for such nonsense.
I needed a polished distro with fractional scaling on #HiDPI displays, and after some research to get me up to date, I plumped for #Pop_OS with its #COSMIC desktop.
Pop_OS is great - it has a solid #Ubuntu base and the UI feels far more consistent and robust than either KDE or #Gnome - but my essential #Java app, the #JMRI #ModelRailway control software, looked awful at any scale. Jagged fonts, boxes overflowing, etc.
After a lot of searching I found a shell command to force font anti-aliasing for old Java apps (comment if you need a link to the Gist), and with a few more tweaks finally all was well.
Pop_OS, like MX Linux, seems to be AI-neutral rather than overtly AI-positive like Fedora, so I've achieved my original goal, even if it took me in an unexpected direction.
-
This evening I finished re-numbering, and labelling, all my accessory controllers (points, lights) and point feedback sensors. And documenting everything in a spreadsheet. This included moving some point wiring around on the accessory controllers so that the numbering is more logical than it was.
The second step is to now go through and update everything in JMRI. Every point has a different accessory address and a different sensor address. That’s 60 addresses to update.
I can already see that block occupancy has stopped playing up 💪 hoping to update all the points tomorrow lunchtime and then update the sensors in the evening.
And then… I can re-wire and program the signals 😬
-
This evening I finished re-numbering, and labelling, all my accessory controllers (points, lights) and point feedback sensors. And documenting everything in a spreadsheet. This included moving some point wiring around on the accessory controllers so that the numbering is more logical than it was.
The second step is to now go through and update everything in JMRI. Every point has a different accessory address and a different sensor address. That’s 60 addresses to update.
I can already see that block occupancy has stopped playing up 💪 hoping to update all the points tomorrow lunchtime and then update the sensors in the evening.
And then… I can re-wire and program the signals 😬
-
This evening I finished re-numbering, and labelling, all my accessory controllers (points, lights) and point feedback sensors. And documenting everything in a spreadsheet. This included moving some point wiring around on the accessory controllers so that the numbering is more logical than it was.
The second step is to now go through and update everything in JMRI. Every point has a different accessory address and a different sensor address. That’s 60 addresses to update.
I can already see that block occupancy has stopped playing up 💪 hoping to update all the points tomorrow lunchtime and then update the sensors in the evening.
And then… I can re-wire and program the signals 😬
-
This evening I finished re-numbering, and labelling, all my accessory controllers (points, lights) and point feedback sensors. And documenting everything in a spreadsheet. This included moving some point wiring around on the accessory controllers so that the numbering is more logical than it was.
The second step is to now go through and update everything in JMRI. Every point has a different accessory address and a different sensor address. That’s 60 addresses to update.
I can already see that block occupancy has stopped playing up 💪 hoping to update all the points tomorrow lunchtime and then update the sensors in the evening.
And then… I can re-wire and program the signals 😬
-
This evening I finished re-numbering, and labelling, all my accessory controllers (points, lights) and point feedback sensors. And documenting everything in a spreadsheet. This included moving some point wiring around on the accessory controllers so that the numbering is more logical than it was.
The second step is to now go through and update everything in JMRI. Every point has a different accessory address and a different sensor address. That’s 60 addresses to update.
I can already see that block occupancy has stopped playing up 💪 hoping to update all the points tomorrow lunchtime and then update the sensors in the evening.
And then… I can re-wire and program the signals 😬
-
Lightning quick update, I now have JMRI set up enough that it is useful. I can even change points using the touchscreen (keyboard and mouse are out of sight).
-
Lightning quick update, I now have JMRI set up enough that it is useful. I can even change points using the touchscreen (keyboard and mouse are out of sight).
-
Lightning quick update, I now have JMRI set up enough that it is useful. I can even change points using the touchscreen (keyboard and mouse are out of sight).
-
Lightning quick update, I now have JMRI set up enough that it is useful. I can even change points using the touchscreen (keyboard and mouse are out of sight).
-
Lightning quick update, I now have JMRI set up enough that it is useful. I can even change points using the touchscreen (keyboard and mouse are out of sight).
-
Finally started setting up the current railway layout in JMRI. It has some good points, like automatically registering points when they are set, and all the Digitrax block detection sensors when the track is turned on. Had to register the reverse polarity blocks manually.
However even on a Raspberry Pi 5 the UI is terribly unresponsive - laggy, to the point of almost being unusable. Which makes actually creating and labelling the layout a very painful and error-prone process. I can reduce the problem by reducing the size of the panel editor window but it’s not great.
I can see the GPU getting hammered. Wondering how much is having a large display (27” 4k) and how much is the probably quite old Java GUI code. Oh, and I can’t seem to choose a resolution for the Pi to use, it just defaults to the panel’s native resolution.
-
Finally started setting up the current railway layout in JMRI. It has some good points, like automatically registering points when they are set, and all the Digitrax block detection sensors when the track is turned on. Had to register the reverse polarity blocks manually.
However even on a Raspberry Pi 5 the UI is terribly unresponsive - laggy, to the point of almost being unusable. Which makes actually creating and labelling the layout a very painful and error-prone process. I can reduce the problem by reducing the size of the panel editor window but it’s not great.
I can see the GPU getting hammered. Wondering how much is having a large display (27” 4k) and how much is the probably quite old Java GUI code. Oh, and I can’t seem to choose a resolution for the Pi to use, it just defaults to the panel’s native resolution.
-
Finally started setting up the current railway layout in JMRI. It has some good points, like automatically registering points when they are set, and all the Digitrax block detection sensors when the track is turned on. Had to register the reverse polarity blocks manually.
However even on a Raspberry Pi 5 the UI is terribly unresponsive - laggy, to the point of almost being unusable. Which makes actually creating and labelling the layout a very painful and error-prone process. I can reduce the problem by reducing the size of the panel editor window but it’s not great.
I can see the GPU getting hammered. Wondering how much is having a large display (27” 4k) and how much is the probably quite old Java GUI code. Oh, and I can’t seem to choose a resolution for the Pi to use, it just defaults to the panel’s native resolution.
-
Finally started setting up the current railway layout in JMRI. It has some good points, like automatically registering points when they are set, and all the Digitrax block detection sensors when the track is turned on. Had to register the reverse polarity blocks manually.
However even on a Raspberry Pi 5 the UI is terribly unresponsive - laggy, to the point of almost being unusable. Which makes actually creating and labelling the layout a very painful and error-prone process. I can reduce the problem by reducing the size of the panel editor window but it’s not great.
I can see the GPU getting hammered. Wondering how much is having a large display (27” 4k) and how much is the probably quite old Java GUI code. Oh, and I can’t seem to choose a resolution for the Pi to use, it just defaults to the panel’s native resolution.
-
Finally started setting up the current railway layout in JMRI. It has some good points, like automatically registering points when they are set, and all the Digitrax block detection sensors when the track is turned on. Had to register the reverse polarity blocks manually.
However even on a Raspberry Pi 5 the UI is terribly unresponsive - laggy, to the point of almost being unusable. Which makes actually creating and labelling the layout a very painful and error-prone process. I can reduce the problem by reducing the size of the panel editor window but it’s not great.
I can see the GPU getting hammered. Wondering how much is having a large display (27” 4k) and how much is the probably quite old Java GUI code. Oh, and I can’t seem to choose a resolution for the Pi to use, it just defaults to the panel’s native resolution.
-
Over the last week I’ve been thinking about what to run JMRI on, and after looking at the rather high prices of NUCs I’ve taken a cheaper and more novel approach (and will just have to borrow my partner’s laptop from time to time).
I’ve ordered a 15” touchscreen, a Raspberry Pi 5 and an NVMe daughter board. The touchscreen has a VESA mount so I can 3D print an adapter to hold the Pi and a mount/stand to make it reasonably portable. I’ll put some pics up when I’m done.
-
Over the last week I’ve been thinking about what to run JMRI on, and after looking at the rather high prices of NUCs I’ve taken a cheaper and more novel approach (and will just have to borrow my partner’s laptop from time to time).
I’ve ordered a 15” touchscreen, a Raspberry Pi 5 and an NVMe daughter board. The touchscreen has a VESA mount so I can 3D print an adapter to hold the Pi and a mount/stand to make it reasonably portable. I’ll put some pics up when I’m done.
-
Over the last week I’ve been thinking about what to run JMRI on, and after looking at the rather high prices of NUCs I’ve taken a cheaper and more novel approach (and will just have to borrow my partner’s laptop from time to time).
I’ve ordered a 15” touchscreen, a Raspberry Pi 5 and an NVMe daughter board. The touchscreen has a VESA mount so I can 3D print an adapter to hold the Pi and a mount/stand to make it reasonably portable. I’ll put some pics up when I’m done.
-
Over the last week I’ve been thinking about what to run JMRI on, and after looking at the rather high prices of NUCs I’ve taken a cheaper and more novel approach (and will just have to borrow my partner’s laptop from time to time).
I’ve ordered a 15” touchscreen, a Raspberry Pi 5 and an NVMe daughter board. The touchscreen has a VESA mount so I can 3D print an adapter to hold the Pi and a mount/stand to make it reasonably portable. I’ll put some pics up when I’m done.
-
Over the last week I’ve been thinking about what to run JMRI on, and after looking at the rather high prices of NUCs I’ve taken a cheaper and more novel approach (and will just have to borrow my partner’s laptop from time to time).
I’ve ordered a 15” touchscreen, a Raspberry Pi 5 and an NVMe daughter board. The touchscreen has a VESA mount so I can 3D print an adapter to hold the Pi and a mount/stand to make it reasonably portable. I’ll put some pics up when I’m done.
-
I’m trying to decide what I’m going to use to run my railway automation (which will be JMRI). I also need to be able to program Digitrax and other DCC hardware that seem only to have Windows support.
I don’t want to run Windows all the time, only when I need to. Maybe a VM? But I’m guessing I’ll need to pay for a licence too.
Anyone else solved this conundrum? #ModelRailway #JMRI #Windows #VM
-
I’m trying to decide what I’m going to use to run my railway automation (which will be JMRI). I also need to be able to program Digitrax and other DCC hardware that seem only to have Windows support.
I don’t want to run Windows all the time, only when I need to. Maybe a VM? But I’m guessing I’ll need to pay for a licence too.
Anyone else solved this conundrum? #ModelRailway #JMRI #Windows #VM
-
I’m trying to decide what I’m going to use to run my railway automation (which will be JMRI). I also need to be able to program Digitrax and other DCC hardware that seem only to have Windows support.
I don’t want to run Windows all the time, only when I need to. Maybe a VM? But I’m guessing I’ll need to pay for a licence too.
Anyone else solved this conundrum? #ModelRailway #JMRI #Windows #VM
-
I’m trying to decide what I’m going to use to run my railway automation (which will be JMRI). I also need to be able to program Digitrax and other DCC hardware that seem only to have Windows support.
I don’t want to run Windows all the time, only when I need to. Maybe a VM? But I’m guessing I’ll need to pay for a licence too.
Anyone else solved this conundrum? #ModelRailway #JMRI #Windows #VM
-
I’m trying to decide what I’m going to use to run my railway automation (which will be JMRI). I also need to be able to program Digitrax and other DCC hardware that seem only to have Windows support.
I don’t want to run Windows all the time, only when I need to. Maybe a VM? But I’m guessing I’ll need to pay for a licence too.
Anyone else solved this conundrum? #ModelRailway #JMRI #Windows #VM
-
Made some new connections today! I received some 20ga wire in the mail and immediately went to work. I believe Kato used 22ga but this works too. Seems to work just fine. I also added a screenshot of the JMRI web interface and my (crappy) webcam solution. I need a better cam with a higher FOV.😅
And before anyone comments; YES, I know I need to clean my 3d printer workspace! 😂
#modeltrain #train #trains #raspberrypi #arduino #JMRI #3dprinting
-
Made some new connections today! I received some 20ga wire in the mail and immediately went to work. I believe Kato used 22ga but this works too. Seems to work just fine. I also added a screenshot of the JMRI web interface and my (crappy) webcam solution. I need a better cam with a higher FOV.😅
And before anyone comments; YES, I know I need to clean my 3d printer workspace! 😂
#modeltrain #train #trains #raspberrypi #arduino #JMRI #3dprinting
-
Made some new connections today! I received some 20ga wire in the mail and immediately went to work. I believe Kato used 22ga but this works too. Seems to work just fine. I also added a screenshot of the JMRI web interface and my (crappy) webcam solution. I need a better cam with a higher FOV.😅
And before anyone comments; YES, I know I need to clean my 3d printer workspace! 😂
#modeltrain #train #trains #raspberrypi #arduino #JMRI #3dprinting
-
Made some new connections today! I received some 20ga wire in the mail and immediately went to work. I believe Kato used 22ga but this works too. Seems to work just fine. I also added a screenshot of the JMRI web interface and my (crappy) webcam solution. I need a better cam with a higher FOV.😅
And before anyone comments; YES, I know I need to clean my 3d printer workspace! 😂
#modeltrain #train #trains #raspberrypi #arduino #JMRI #3dprinting
-
Got the webcam hooked up to the Pi! I'm able to see my layout anywhere in the house. Still have some tweaking to do because the video is on a 3 - 4 second delay. :ablobblewobble:
-
Got the webcam hooked up to the Pi! I'm able to see my layout anywhere in the house. Still have some tweaking to do because the video is on a 3 - 4 second delay. :ablobblewobble:
-
Got the webcam hooked up to the Pi! I'm able to see my layout anywhere in the house. Still have some tweaking to do because the video is on a 3 - 4 second delay. :ablobblewobble:
-
Got the webcam hooked up to the Pi! I'm able to see my layout anywhere in the house. Still have some tweaking to do because the video is on a 3 - 4 second delay. :ablobblewobble:
-
Temporary setup but I wanted to show it off. I finally got around to converting my loco to DCC. So, the Raspberry Pi is running JMRI and the Arduino Mega is running DCC-EX. I have some Kato turnouts coming in tomorrow that are DCC ready. Cant wait to set them up and control them remotely! Once I get that set up, I'll hook up a webcam to the Pi so I can watch/control it anywhere in the house!
-
Temporary setup but I wanted to show it off. I finally got around to converting my loco to DCC. So, the Raspberry Pi is running JMRI and the Arduino Mega is running DCC-EX. I have some Kato turnouts coming in tomorrow that are DCC ready. Cant wait to set them up and control them remotely! Once I get that set up, I'll hook up a webcam to the Pi so I can watch/control it anywhere in the house!
-
Temporary setup but I wanted to show it off. I finally got around to converting my loco to DCC. So, the Raspberry Pi is running JMRI and the Arduino Mega is running DCC-EX. I have some Kato turnouts coming in tomorrow that are DCC ready. Cant wait to set them up and control them remotely! Once I get that set up, I'll hook up a webcam to the Pi so I can watch/control it anywhere in the house!
-
Temporary setup but I wanted to show it off. I finally got around to converting my loco to DCC. So, the Raspberry Pi is running JMRI and the Arduino Mega is running DCC-EX. I have some Kato turnouts coming in tomorrow that are DCC ready. Cant wait to set them up and control them remotely! Once I get that set up, I'll hook up a webcam to the Pi so I can watch/control it anywhere in the house!
-
Hmm.. I wonder what I'm going to do with these parts...
-
Hmm.. I wonder what I'm going to do with these parts...
-
Hmm.. I wonder what I'm going to do with these parts...
-
Hmm.. I wonder what I'm going to do with these parts...