tag:blogger.com,1999:blog-3258590603195449959.post3260493402628960644..comments2024-02-07T07:29:04.892-05:00Comments on The Splatter: WSJT-X - Filling in the missing piecesVE3NRThttp://www.blogger.com/profile/03495664566826092253noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-3258590603195449959.post-26976770491313476212017-02-05T17:35:30.276-05:002017-02-05T17:35:30.276-05:00Would be interested in your progress. I managed to...Would be interested in your progress. I managed to get WSJT-X working in Ubuntu on the RPI 3Anonymoushttps://www.blogger.com/profile/17759170248846874507noreply@blogger.comtag:blogger.com,1999:blog-3258590603195449959.post-39739087652475342962015-09-05T22:26:24.872-04:002015-09-05T22:26:24.872-04:00I'd definitely run Linux as a client system if...I'd definitely run Linux as a client system if the application software I used was available, but most ham radio software is Windows so I still run it on the desktop and both laptops. I think the first thing that Linux needs to start encroaching on Windows in the ham radio world is to provide a remote (i.e. over an IP connection) interface to rig audio and CAT control. That would at least allow a R-Pi to be used for the connection while the apps still run on Windows, and then permit more and more functionality to be migrated to Linux, and maybe eventually on the client side most applications would be browser based. Dream on.<br /><br />Now that I've used JT-Alert for a while I find it even more useful. The best part is when I'm working at home I can have the rig on all day and on occasions where it says "CQ" then "DX" I can turn my attention to the station without having to compromise my working day - well not too much anyway.<br /><br />Thanks for stopping by Chris,<br /><br />73,<br />ChrisVE3NRThttps://www.blogger.com/profile/03495664566826092253noreply@blogger.comtag:blogger.com,1999:blog-3258590603195449959.post-19643219282401048092015-09-05T16:38:31.973-04:002015-09-05T16:38:31.973-04:00Nice write-up Chris. I sure wish I could use JT-Al...Nice write-up Chris. I sure wish I could use JT-Alert but it just won't run on Linux, along with HRD, N1MM+ and a few others. I switched to Linux earlier this year and have been pretty disappointed in the lack of quality ham radio program options. CQRLog is a pretty good daily logger and WSJT-X works well for JT65/9 but without something like JT-Alert I'm missing all of those useful features you mentioned, which makes operating digital a lot more work and a lot less fun. I suspect that at some point Microsloth is going to end up with my money again.<br /><br />Cheers & 73<br />Chris - KC3DIGAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3258590603195449959.post-9274191904905031722015-08-03T10:48:45.097-04:002015-08-03T10:48:45.097-04:00After spending more time with JT-Alert (especially...After spending more time with JT-Alert (especially after enabling the alert that sounds a tone when someone calls) allows me to use it more productively (log-wise) and multi-task better (like writing this blog while operating).<br /><br />Building large software packages from source can be frustrating on any platform, especially when it doesn't come with appropriate makefiles. There is a developer mailing list for WSJT where you can ask questions. When WSJT-X V1.6 comes out I think there'll be interest in building an R-Pi version because of the support for WSPR. As WSPR stations often run 24 hours a day I doubt people will want to dedicate their computers drawing 100-200 watts to the task.<br /><br />Right now I'm looking at two applications for my R-Pi collection. I'm already using one as a phone switch, mail server and general purpose server for network support like DHCP, NTP, DNS and so forth, but also want to rebuild our repeater system's Echolink/IRLP gateway to run with minimum power, and also as a programming environment for Atmel processors including the ability to program the chip directly through the GPIO pins.<br /><br />Thanks for stopping by Brian!<br />ChrisVE3NRThttps://www.blogger.com/profile/03495664566826092253noreply@blogger.comtag:blogger.com,1999:blog-3258590603195449959.post-52060153244231162572015-08-03T09:38:17.354-04:002015-08-03T09:38:17.354-04:00I didn't know about JT_Alert. I will have to ...I didn't know about JT_Alert. I will have to try that one out.<br /><br />On another note, I have been trying to compile from source WSJT-X on the RPi2. Very difficult endeavour unfortunately. The designer of WSJT-X also doesn't know enough about the implementation details at the compilation level to help. Apparently, because it is open source, there is a developer community (still need to reach out to them) that manitains and extends the code base. <br /><br />The biggest obstacle to getting the "Latest - v1.5" WSJT-X compiled on the RPi2 is QT5. This took me almost 30 hours to download all the source, dependencies, and then compile and link. Wow !! And the RPi2 is no slouch. <br /><br />The problem now is the actual compilation of the WSJT-X program. One of the C++ files fails on compilation. My C++ is very very rusty and and the error code is likely pointing to something wrong with the QT5 compilation and installation. Oh Joy !! Not looking forward to wasting too much time on QT5 anymore. I think I will find a cheap netbook and install Ubuntu and foresake WSJT-X on the RPi2. Perhaps the Raspbian and WSJT-X folks will update their application repos to have the most recent versions of QT and WSJT-X and I won't have to waste my precious time on figuring out a compilation error.<br /><br />I love the RPi2 and what it can do; especially what can be done with HamRadio applications. It has been a lot of fun. But, head banging on compilation errors of other people's code is where it stops being fun.<br /><br />I post this comment because WSJT-X can be fun. But choose the right platform to ensure it is fun.Anonymoushttps://www.blogger.com/profile/04989646329258492991noreply@blogger.com