current:beta
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
current:beta [2021/04/25 17:09] – James Sentman | current:beta [2022/01/28 17:32] – James Sentman | ||
---|---|---|---|
Line 1: | Line 1: | ||
=====Beta Versions===== | =====Beta Versions===== | ||
- | A notarized beta of XTension 9.4.40 is available as of 4/25/2021 | ||
+ | ====XTension Beta 9.4.45 BETA 2 for ARM and X86==== | ||
+ | Released: 1/28/2022 | ||
- | [[https:// | + | Download: |
+ | This version continues the transition to being fully M1 native. There are many change to the overall code to support this and so both the X86 and M1 versions will require a longer Beta cycle. | ||
- | This version includes a beta plugin | + | This beta updates the embedded python version used for most plugins to 3.10 from 3.7 which has made a lot of re-testing necessary. This python build is fully universal however so should |
- | NOTE that rtl_sdr supported radios are tested. The software is present for the soapy_sdr supported radios but as I don’t have any of those I have not tested | + | All the binary plugins except the original legacy ones from Michael |
- | In addition to the rtl_433 | + | As of Beta 2 the only plugin |
+ | One of the major changes in this version is the inclusion of an entirely different Home Kit plugin. In my testing it appears to be working fine, but I do not have test case for every kind of shared device that you may be using. This new code will support many more features and functions than the previous but I have not begun to implement any of that yet, just concentrating on getting what worked before working again. As of this Beta it should be a drop in replacement and you should not see any issues or problems. If you do find something that isn’t working with it that worked before please capture any log output when starting the interface and when trying to control the unit in question. | ||
- | There is not yet a wiki page devoted | + | ===Errors and Log Lines you may see:=== |
+ | When you first startup the app the OS will ask for permission | ||
- | ====XTension Settings: | + | Many plugins are still using the python 2 version |
- | Setting up the SDR should be very straightforward assuming | + | |
- | {{: | + | Several of the plugins generate deprecated warnings in the log about changes to the asyncio libraries in python 3.10. These can be ignored as long as the plugin is otherwise working normally. |
- | For any radio connected | + | Note that no changes |
- | If you are using a supported SDR on the Mac itself then none of the following about the raspberry pi is needed. This is only needed if you wish to use a pi as a remote host for an SDR. If you wish to run a remote connection to a host pi then select “remote via ssh” from the popup menu labeled “connection type" | ||
- | ====Raspberry Pi Remotes: | ||
- | **Note that this section | + | In addition to that discussed above the following items have changed or been added: |
+ | | ||
+ | | ||
- | Running SDR software on the Pi takes a considerable amount of resources. I would not recommend running this on a Pi Zero or a very old device. It runs just fine on a previous | + | Changes that were in the previous |
- | If you wish to have many radios installed away from the XTension mac you can install | + | * The Manage Global Scripts window now displays |
+ | * Plugins | ||
+ | * Fixed a potential problem in the XTension kit receiver plugin if a device sent invalid JSON characters. It no longer causes the listening thread | ||
+ | * Added support to the XTension kit plugin for new and upcoming devices. | ||
+ | * For the M1 build an error is no longer created at startup due to Apple no longer supporting some of the default icons that I was pulling from the system. | ||
+ | * The Genmon plugin will update the label of the Engine State unit even if the state of the engine has not changed. | ||
+ | * Genmon: Added many new error and status units so that it is simpler to get specific information than to parse the label of the engine status unit. New units created include: | ||
+ | * Error: Engine Speed High or Low | ||
+ | * Error: Governor failure | ||
+ | * Error: Low Oil | ||
+ | * Error: Overcrank | ||
+ | * Error: Overheat | ||
+ | * Error: Overload | ||
+ | * Error: RPM Sensor | ||
+ | * Error: Voltage High or Low | ||
+ | * Error: Warning (generator is sending a warning that is not yet an error or alarm condition) | ||
+ | * Generator Is In Alarm | ||
+ | * Generator Is Running | ||
+ | * Generator Is Ready | ||
+ | * Generator Is Exercising | ||
+ | * Generator Is Ready | ||
+ | * Generator Service Is Due | ||
- | The connection to the raspberry pi is via an ssh session. There is no way to save the password into the interface so you must configure your mac and the pi to connect via ssh without a password. If you have never done this on your mac you must first create an ssh key that you can share with the pi. Start the terminal and enter this command: | ||
- | |||
- | < | ||
- | ssh-keygen -t rsa | ||
- | </ | ||
- | |||
- | The switch for -t rsa may not be needed depending on the OS version. Use the default key name and do not set an encryption password for the key. | ||
- | |||
- | now you need to send that to the raspberry pi so that you can connect from your mac to the pi without having to send the password each time. This is also done via the command line on the Mac to the pi. (make sure you have changed the default password on the pi and set it’s hostname to something other than the default of raspberrypi.local or you’ll run into trouble later) | ||
- | |||
- | the command to register your ssh key with the pi is: | ||
- | |||
- | < | ||
- | ssh-copy-id pi@thePiAddressOrName.local | ||
- | </ | ||
- | |||
- | if your user is other than the default pi make sure to change that. You can connect via the IP address of the pi if you have assigned it a static IP or via it’s hostname.local as long as you have changed it from the default of raspberrypi.local or you’ll not be able to setup more than a single pi on the network. | ||
- | |||
- | You may have to answer several questions about are you sure if you have setup other pi’s as the keys will have changed and ssh will warn you that it can’t verify that you’re connecting to the right machine. If you have setup other pi’s in the past it may refuse to connect at all because it’s in your known host file with a different machines key. If thats the case you need to edit your known hosts file to remove it. If you haven’t ever done this you can do it at the command line via something like: | ||
- | |||
- | < | ||
- | nano ~/ | ||
- | </ | ||
- | then use the control-w to find “raspberrypi.local” and delete that whole line. Then save by doing a control-o and then exit with a control-x. There are many many other resources for more info on doing this on the web if you need more info. | ||
- | |||
- | Once that is done and you have copied the key via the above please do test that you can ssh in without a password. It may require that you do it once manually and OK the fact that it can’t verify the key if you have every connected to another one and you need to do that before the software can connect without your attention so once that has completed test it via ssh’ing in via a regular command like: | ||
- | |||
- | < | ||
- | ssh pi@yourPiAddress.local | ||
- | </ | ||
- | |||
- | it may ask you “are you sure” because something cannot be verified. Please answer yes and if you end up at the ssh prompt for the pi then all is well. You can then move on to compiling the rtl_433 software on the pi. | ||
- | |||
- | ====Installing rtl_433 on the pi==== | ||
- | There are 2 steps to installing the software on the pi. You need both the low level SDR radio software and the rtl_433 software. They are very easy to install. | ||
- | |||
- | ===Load Up The Pi:=== | ||
- | If you haven’t already load up the most recent pi software and do any updates available. I wont post instructions for this here, if you can’t do this and can’t find instructions on the internet for it you probably shouldn’t be trying this ;) The program will work with the “lite” versions of the raspian images or the desktop and full installs but those are not necessary and if you’re not using the pi for desktop work you will only be wasting space by using those. | ||
- | |||
- | ===Make Sure GIT is installed: | ||
- | try this command to see if git is installed on your device or not: | ||
- | < | ||
- | git --version | ||
- | </ | ||
- | |||
- | if you get a “command not found” error then you need to install git. That command is: | ||
- | < | ||
- | sudo apt install git | ||
- | </ | ||
- | it will tell you that another 33meg of disk space or other is needed and you need to say Yes so that it will install | ||
- | |||
- | Once that is finshed you can retry the git --version command. As of this writing the version installed is 2.20.1 | ||
- | |||
- | ===Install Pre-Requisites: | ||
- | The following packets are required to finish the rest of the install. If you already have any of them then the installer will just skip that part: | ||
- | |||
- | < | ||
- | sudo apt install cmake libusb-1.0-0-dev build-essential autoconf libtool pkg-config | ||
- | </ | ||
- | |||
- | ===Install rtl-sdr:=== | ||
- | < | ||
- | git clone git:// | ||
- | cd rtl-sdr | ||
- | mkdir build | ||
- | cd build | ||
- | cmake -DINSTALL_UDEV_RULES=ON .. | ||
- | make | ||
- | sudo make install | ||
- | sudo ldconfig | ||
- | </ | ||
- | |||
- | ===Install rtl_433:=== | ||
- | < | ||
- | git clone https:// | ||
- | cd rtl_433 | ||
- | mkdir build | ||
- | cd build | ||
- | cmake .. | ||
- | make | ||
- | sudo make install | ||
- | </ | ||
- | |||
- | ===Setup For Remote:=== | ||
- | |||
- | Once you’ve done all that you can select “Remote via SSH” from the Connection Type popup as shown above and unless you changed the install locations on purpose the defaults should all work just fine and you can connect an interface to a device connected via USB to a remote raspberry pi. If you need to have more than one radio connected to the same mac or raspberry pi that is also possible, but read on for even more configuration: | ||
- | |||
- | ===Multiple SDR’s:=== | ||
- | XTension will support multiple SDR radios on the same machine via the serial number of the device. Unfortunately all the devices I have seen come with the serial number set to “0000001” or something similar. So you have to use the rtl_eeprom tool to set the serial number before filling it into the XTension interface as shown above. This will work for both local SDR’s as well as those connected to remote Raspberry Pi hosts. I will not include instructions for how to use the rtl_eeprom tool here, please look those up on the wiki page for the rtl_433 page linked to above. You’ll find the app compiled for the Mac inside the plugin folder which is inside the XTension app. If you control click on XTension in the finder and select “show package contents” and then open the Contents folder, and then the Resources folder and then the Plugins folder and finally the “rtl_433.isf” folder you’ll find the supporting applications such as rtl_eeprom. You can take a terminal session in there and then use the app to write a specific serial number or id string to the radio which you can then use in the **SDR Serial Number** field of the XTension settings window as shown above. | ||
- | |||
- | ===What it doesn’t do:=== | ||
- | Currently temperature, |
current/beta.txt · Last modified: 2024/02/05 17:51 by James Sentman