Replies: 21 comments 132 replies
-
|
Thanks Manual. |
Beta Was this translation helpful? Give feedback.
-
|
You are getting weir errors, because you run manually |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
|
You don‘t need to start the driver. The driver is running in the background. Please check the driver logs https://github.com/Louisvdw/dbus-serialbattery/wiki/Troubleshoot#check-the-log-files-on-your-gx-device |
Beta Was this translation helpful? Give feedback.
-
|
Just for your understanding. You get this error |
Beta Was this translation helpful? Give feedback.
-
|
thanks Manuel I understand. I have made some schemes and will try again later. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Manual root@raspberrypi4:/data/etc/dbus-serialbattery# bluetoothctl info "C8:47:8C:E9:13:FB"
Device C8:47:8C:E9:13:FB not available
root@raspberrypi4:/data/etc/dbus-serialbattery# bluetoothctl scan on
Discovery started
[CHG] Controller DC:A6:32:B5:7F:AC Discovering: yes
[NEW] Device 08:66:98:DD:30:53 08-66-98-DD-30-53
[NEW] Device 07:5C:53:7F:74:D8 07-5C-53-7F-74-D8
[NEW] Device 46:2C:93:95:22:FD 46-2C-93-95-22-FD
[NEW] Device C8:47:8C:E9:13:FB JK_B2A20S20P
[NEW] Device 4A:C0:6C:53:AC:4A 4A-C0-6C-53-AC-4A |
Beta Was this translation helpful? Give feedback.
-
|
Did you try |
Beta Was this translation helpful? Give feedback.
-
|
root@raspberrypi4:/data/etc/dbus-serialbattery# bluetoothctl pair C8:47:8C:E9:13:FB |
Beta Was this translation helpful? Give feedback.
-
|
In the |
Beta Was this translation helpful? Give feedback.
-
yes. I have made changes. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
This errors probably arise, because you changed names and so on. Delete the folder
Change the MAC address in |
Beta Was this translation helpful? Give feedback.
-
|
Will do. Much appreciated |
Beta Was this translation helpful? Give feedback.
-
|
:( 2023-03-09 15:50:58.807084500 INFO:SerialBattery:Testing Jkbms |
Beta Was this translation helpful? Give feedback.
-
|
Seems to be a problem with line endings. If you uploaded the files unpaacked, then better download the zip directly on Venus OS and unpack it there. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I saw this discussion for the new bluetooth version of the JKBMS-driver and I'm interested in trying out the new driver. I downloaded the tar.gz.-file, unrar, installlocal.sh and modified utils.py for MAC and performed reboot. I still have the USB-RS485-connection connected. Would it be possible to have the same JKBMS connected simultaniously via bluetooth and RS485? |
Beta Was this translation helpful? Give feedback.
-
|
Today I saw, that the battery is charged only with about 200-300W although there is plenty of PV available. At the moment charging with 229 but feeding 1200W into the grid... Temperature of battery is 17 degree... I checked all my limits in remote console, but everything setting is much higher... |
Beta Was this translation helpful? Give feedback.
-
|
Somehow there is a charge voltage maximum of 53.6V. This prevents charging with higher currents. SOC is 56%, so far from full. I don't find the setting, where the 53.6V are coming from... |
Beta Was this translation helpful? Give feedback.
-
|
After disabling "LINEAR_LIMITATION_ENABLE" the MaxChargeVoltage jumped back to 55.2 so charging is normal again. So it seems that either I configured something wrong or there is a bug in the LINEAR_LIMITATION feature... |
Beta Was this translation helpful? Give feedback.
-
|
Ok, found this line in battery.py(138): self.control_voltage = FLOAT_CELL_VOLTAGE * self.cell_count. So, if there is no high cell voltage, then the charge voltage will be set to 16*3.35=53.6V. This makes no sense to me, because that would mean, charge current will be limited and charging above float cell voltage. So I leave this feature deactivated for the moment. |
Beta Was this translation helpful? Give feedback.
-
|
For the long term there should be no difference in the provided data between wired and Bluetooth. For the charging problem I think there is already one or multiple issues open. Please check the existing issues and if you find nothing feel free to open a new one. At the moment Luis seems to be pretty bussy, therefore the development of this driver is a little bit stuck. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for the driver, it works well for my MultiPlus II GX. I added a cheap TP-Link Bluetooth Dongle to make it work. I noticed that allow to charge/discharge is set to No: Is that a problem? It is discharging fine, so I suppose it's not, but I also couldn't find out why it says that. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, and it also doesn't show the installed capacity:
|
Beta Was this translation helpful? Give feedback.
-
|
I got the "Allow to (dis)charge" to work by adding these lines in |
Beta Was this translation helpful? Give feedback.
-
|
This lines should be already there dbus-serialbattery/etc/dbus-serialbattery/jkbms_ble.py Lines 114 to 116 in 3f67884 Can you tell us which hardware version of the BMS you have? I'm not sure, if this provides the same data. Maybe @baranator know it? |
Beta Was this translation helpful? Give feedback.
-
|
I see, I used the released version 0.14.3ble. Maybe not all changes had made it in there. I'll try latest then. HW version says |
Beta Was this translation helpful? Give feedback.
-
|
Yep, sorry. Latest code now also reports the capacity correctly. 👍 |
Beta Was this translation helpful? Give feedback.
-
|
@baranator I was reading in #372 and I think starting it using the serial-starter is really not the best way. I attached two serial dongles and the whole thing went crazy, trying to access the same JKBMS twice etc. AFAICS, starting services is really easy. All that needs to be done is to create a symlink or file named /service/myservicename/run and it will automatically be started. I will try that today. If this works, then we can even make it work standalone with multiple BMS and no need for a serial dongle. |
Beta Was this translation helpful? Give feedback.
-
|
Created a PR: #502 - let me know any comments. |
Beta Was this translation helpful? Give feedback.
-
i totally agree. we already discussed that somewhere; abusing a serial-port as a dummy for bt was meant to be a provisionary solution for testing if this is doable at all without having to figure out how to combine it nicely with the true-serial-approach of other BMS in EDIT: Ah, i oversaw your PR...does it work properly also when other classical non-ble bms are present? I think one could somehow unify it somehow more nicely with the the way serial-bms are accessed, but that would require overhauling that whole mechanism - for now this is for sure already a much better solution than my pseudo-serial-stuff :D |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, I don't have multiple BMS to test. But the way I modified it makes the BLE part independent of the serial part, so both parts should work next to each other without problems. At least that's what I think. The BLE BMS get their own service each, whereas the serial BMS will be started as usual using the serial-starter. |
Beta Was this translation helpful? Give feedback.
-
|
I have observed the problem that the memory usage of |
Beta Was this translation helpful? Give feedback.
-
|
My system is up since |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that's quite a lot. The GX device in my MultiPlus only has 512MB of RAM, so it runs out regularly. |
Beta Was this translation helpful? Give feedback.
-
|
I have researched a lot now and also asked ChatGPT, but I still can't figure out why the memory leak is happening. The problem is that I can't really test going back to serial port because my JKBMS's RS485 port is hosed. Maybe I can get @pos-ei-don to help test that? That would be running only serial battery connection for about 1-2h and see if dbus-daemon memory usage increases, then run it with Bluetooth connection and check again. It seems to using about 20-30 MB more every hour for me. |
Beta Was this translation helpful? Give feedback.
-
|
How can I help? |
Beta Was this translation helpful? Give feedback.
-
Ah thanks. I would like to debug this memory issue. You can see the current free memory by using Here you can see in the second output line that dbus-daemon currently uses about 34.7 MB of memory (third column). Once it uses more than 100 is will actually show it as Now I would like to know - does this increase on a system where only the "normal" serial battery is running or is it specific to the Bluetooth implementation. I think if you are currently running the regular serial connection you can check every 2 hours and see how the available memory and the used memory by dbus-daemon develops. I have a strong suspicion that it will also use up the memory over time, because I have seen even more memory leaking when I run two processes that send data to dbus. |
Beta Was this translation helpful? Give feedback.
-
|
I cannot pair it i am getting Failed to pair: org.bluez.Error.AuthenticationCanceled [JK_B2A8S20P]# pair C8:47:8C:EC:8D:37 [JK_B2A8S20P]# info C8:47:8C:EC:8D:37 need help to change pairing code as i cannot change it on JK, can you point me where is it |
Beta Was this translation helpful? Give feedback.
-
|
Please try the latest commit. See top how to install it |
Beta Was this translation helpful? Give feedback.
-
|
@crafty911 I don't think you have to pair. Just try to "trust". |
Beta Was this translation helpful? Give feedback.
-
|
You cannot start the driver like this. If you trusted the device then reboot and it should connect. It's important that no other device is connected to the BMS. |
Beta Was this translation helpful? Give feedback.
-
|
i reboot it from GUI and from SSH till nothing, maybe i miss something, let me tell you what i have raspberry pi 3 with bluetooth stick what i did just flashed Venus and installed your image via USB this all |
Beta Was this translation helpful? Give feedback.
-
|
Just for understanding. Did you changed the default PIN for connecting to the JKBMS in the JKBMS app? Default is |
Beta Was this translation helpful? Give feedback.
-
|
Yes I did change the default PIN. Is it possible to make it work with a non-default PIN? |
Beta Was this translation helpful? Give feedback.
-
|
I used |
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
Just to say: I thought about automatic adding of all found BMS and it's probably quite easy. Since we already scan for all devices and then only filter out the one with the given MAC, it seems even better to just detect all, check if they are 'JK-' or 'JK_' devices and then add each one as a separate device. I think I can try this out some time. Alternatively, we could also just try to connect to any Bluetooth device in range and use the current |
Beta Was this translation helpful? Give feedback.
-
|
Since there are already PR for other BMS the last one would be a great idea. If scanning is enabled or not should be configurable via the config file. It has to obviously to be tested, since this can impact seriously the performance. If I scan for Bluetooth devices in our office I get over 20 devices. Today I changed a lot of code to use ble and normal better in one driver. Later this day I will merge the last changes which resolve also the code checks. |
Beta Was this translation helpful? Give feedback.
-
|
The PR #533 is now merged. |
Beta Was this translation helpful? Give feedback.
-
|
I actually checked yesterday and the scanning that is done right now is completely unnecessary 😄 There is a method in bleak to connect to a device by it's MAC address and it works just fine. Maybe I will implement it so that the scanning happens in the general code and then the found devices are tested and any found one is added as a new battery. I'll see if I have time this week to test that. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I have successfully installed the driver on my RPI3b with VenusOS 2.94 and DVCC enabled. The BMS is an JK BMS B2A8S20P. Everything is functioning also together with 2 Ruuvi Bluetooth temperature meters. The only thing I now run into is in the VRM portal there is an alarm. |
Beta Was this translation helpful? Give feedback.
-
|
Gracia Manuel for the quick reply. I tried and did 2x a reboot but the alarm remains in VRM portal.
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, then try with DRIVER_SUBVERSION = ".0"
I have two Venus OS and on none of them I have this error. |
Beta Was this translation helpful? Give feedback.
-
|
I tried and set the driver subversion to .0 still the same result I run Venus OS 2.94 Build date 20230412212730. I updated this weekend to the latest just before I integrated the JK BMS. Here is a screenshot of the device list. All other hardware is from Victron except the Ruuvi temperature sensors but this doesn't interact with DVCC. I will try this evening to remove/disable the JK BMS driver and see if the issue disappears and if it not linked to the multiplus which has also old firmware and is not updateable. |
Beta Was this translation helpful? Give feedback.
-
|
Try to check all fimwares in this portal by opening every device. Maybe you find something strange. Anyway there is another issue/discussion here where another user has also a problem with DVCC and the battery monitor. You can also try to boot Venus OS v2.93. If this does not help you can boot again v2.94. See #525 (reply in thread) |
Beta Was this translation helpful? Give feedback.
-
|
Manuel, Thanks for your support. I found the issue. I then started the multiplus and the issue came back. So it is related to the old firmware on the multiplus in combination with the DVCC function in Venus OS which is causing the alarm. I will search to upgrade the multiplus. Thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, today i tried your Bluetooth-Version, but I get the following error message: @400000006443c9f50d5ae06c INFO:SerialBattery:Starting dbus-serialbattery
@400000006443c9f50d65c194 INFO:SerialBattery:dbus-serialbattery v1.0.0-jkbms_ble (20230420)
@400000006443c9f50d792a54 INFO:SerialBattery:init of jkbmsble at C8:47:8C:E5:18:3D
@400000006443c9f50d7f3534 INFO:SerialBattery:test of jkbmsble at C8:47:8C:E5:18:3D
@400000006443c9fc117a76e4 ERROR:root:A message handler raised an exception: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte.
@400000006443c9fc117a8e54 Traceback (most recent call last):
@400000006443c9fc117a9a0c File "/usr/lib/python3.8/site-packages/dbus_fast/message_bus.py", line 811, in _process_message
@400000006443c9fc117aad94 result = user_handler(msg)
@400000006443c9fc117ab564 File "/usr/lib/python3.8/site-packages/bleak/backends/bluezdbus/manager.py", line 874, in _parse_msg
@400000006443c9fc117c1cc4 on_value_changed(message.path, self_interface["Value"])
@400000006443c9fc117c2c64 File "/usr/lib/python3.8/site-packages/bleak/backends/bluezdbus/client.py", line 172, in on_value_changed
@400000006443c9fc117c3c04 callback(bytearray(value))
@400000006443c9fc117c47bc File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 260, in ncallback
@400000006443c9fc117c5374 self.assemble_frame(data)
@400000006443c9fc117cc0d4 File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 255, in assemble_frame
@400000006443c9fc117cd074 self.decode()
@400000006443c9fc117cd844 File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 229, in decode
@400000006443c9fc117ce7e4 self.decode_device_info_jk02()
@400000006443c9fc117cefb4 File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 177, in decode_device_info_jk02
@400000006443c9fc117cff54 self.translate(fb, t, self.bms_status)
@400000006443c9fc117de5cc File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 152, in translate
@400000006443c9fc117df56c self.translate(fb, translation, o[translation[0][i]], f32s=f32s, i=i + 1)
@400000006443c9fc117e050c File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 139, in translate
@400000006443c9fc117e10c4 val = val.decode("utf-8").rstrip(" \t\n\r\0")
@400000006443c9fc117e1c7c UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte
@400000006443c9fc117e85f4
@400000006443c9fc13a2f84c ERROR:root:A message handler raised an exception: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte.
@400000006443c9fc13a313a4 Traceback (most recent call last):
@400000006443c9fc13a31f5c File "/usr/lib/python3.8/site-packages/dbus_fast/message_bus.py", line 811, in _process_message
@400000006443c9fc13a32efc result = user_handler(msg)
@400000006443c9fc13a336cc File "/usr/lib/python3.8/site-packages/bleak/backends/bluezdbus/manager.py", line 874, in _parse_msg
@400000006443c9fc13a434b4 on_value_changed(message.path, self_interface["Value"])
@400000006443c9fc13a44454 File "/usr/lib/python3.8/site-packages/bleak/backends/bluezdbus/client.py", line 172, in on_value_changed
@400000006443c9fc13a453f4 callback(bytearray(value))
@400000006443c9fc13a45fac File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 260, in ncallback
@400000006443c9fc13a46b64 self.assemble_frame(data)
@400000006443c9fc13a4d4dc File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 255, in assemble_frame
@400000006443c9fc13a4e47c self.decode()
@400000006443c9fc13a4ec4c File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 229, in decode
@400000006443c9fc13a4fbec self.decode_device_info_jk02()
@400000006443c9fc13a503bc File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 177, in decode_device_info_jk02
@400000006443c9fc13a5135c self.translate(fb, t, self.bms_status)
@400000006443c9fc13a5f5ec File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 152, in translate
@400000006443c9fc13a601a4 self.translate(fb, translation, o[translation[0][i]], f32s=f32s, i=i + 1)
@400000006443c9fc13a61144 File "/data/etc/dbus-serialbattery/jkbms_brn.py", line 139, in translate
@400000006443c9fc13a61cfc val = val.decode("utf-8").rstrip(" \t\n\r\0")
@400000006443c9fc13a628b4 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byteI have a JKBMS JK-B2A24S15P.
My System is VenusOS 3.00 on a Raspberry 4. |
Beta Was this translation helpful? Give feedback.
-
|
I merged it into the |
Beta Was this translation helpful? Give feedback.
-
And i mysel took very big parts from https://github.com/syssi/esphome-jk-bms - that's how it should be, global collaboration for a common goal :) btt: i really would prefer to keep the manufacturing date in (allthough not used by |
Beta Was this translation helpful? Give feedback.
-
|
@mirko3107 could you try it with this file and see if it's also working? https://raw.githubusercontent.com/mr-manuel/venus-os_dbus-serialbattery/jkbms_ble/etc/dbus-serialbattery/jkbms_brn.py |
Beta Was this translation helpful? Give feedback.
-
@400000006448457416d6e6a4 INFO:SerialBattery:Starting dbus-serialbattery
@400000006448457416e23cfc INFO:SerialBattery:dbus-serialbattery v1.0.0-jkbms_ble (20230420)
@400000006448457416f5e43c INFO:SerialBattery:init of jkbmsble at C8:47:8C:E5:18:3D
@400000006448457416fbeb34 INFO:SerialBattery:test of jkbmsble at C8:47:8C:E5:18:3D
@400000006448457d2f07d544 INFO:SerialBattery:JK BMS found!
@400000006448457d2f07e8cc INFO:SerialBattery:Connection established to Jkbms_Ble
@400000006448457d2f07f86c INFO:SerialBattery:Battery Jkbms BLE connected to dbus from c8478ce5183d
@400000006448457d2f080424 INFO:SerialBattery:========== Settings ==========
@400000006448457d2f34a204 INFO:SerialBattery:> Connection voltage: NoneV | Current: NoneA | SoC: None%
@400000006448457d2f34b974 INFO:SerialBattery:> Cell count: None | Cells populated: 0
@400000006448457d2f34c52c INFO:SerialBattery:> LINEAR LIMITATION ENABLE: False
@400000006448457d2f34d0e4 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 35.0V | MAX BATTERY DISCHARGE CURRENT: {utils.MAX_BATTERY_DISCHARGE_CURRENT}V
@400000006448457d2f34e46c INFO:SerialBattery:> CVCM: False
@400000006448457d2f34f024 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
@400000006448457d2f35aba4 INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
@400000006448457d2f35b75c INFO:SerialBattery:> CCCM T: True | DCCM T: True
@400000006448457d2f35c6fc INFO:SerialBattery:> CCCM SOC: True | DCCM SOC: True
@400000006448457d30c4cb6c INFO:SerialBattery:DeviceInstance = 2
@400000006448457d30caa76c INFO:SerialBattery:com.victronenergy.battery.c8478ce5183d
@400000006448457d30d18d0c INFO:SerialBattery:BAT: JKBMS 10.XW 16 cells
@400000006448457d31b760fc INFO:SerialBattery:publish config values = 1Works very well. |
Beta Was this translation helpful? Give feedback.
-
|
Perfect. It's merged with the |
Beta Was this translation helpful? Give feedback.
-
|
I have some nice new features for you :-D See #581
|
Beta Was this translation helpful? Give feedback.
-
|
Looks good! I think I also have a breakthrough in fixing the memory leak, I'll open a PR and a new discussion about it. |
Beta Was this translation helpful? Give feedback.
-
|
Nice, I'm curious what you found! |
Beta Was this translation helpful? Give feedback.
-
|
Installed the nightly version, and it just work with BT 👍 Only thing that I discovered, is the a wrong MOS Temperature. |
Beta Was this translation helpful? Give feedback.
-
|
What BMS version do you have? |
Beta Was this translation helpful? Give feedback.
-
|
Please try again with the version of today. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Changes 2023.05.01
|
Beta Was this translation helpful? Give feedback.
-
|
Which BMS are you using with the serial connection? |
Beta Was this translation helpful? Give feedback.
-
|
JKBMS |
Beta Was this translation helpful? Give feedback.
-
|
You installed with I have also a JKBMS and I'm not able to reproduce it. Did you also reboot? |
Beta Was this translation helpful? Give feedback.
-
|
I rebooted several times and i used your install script. |
Beta Was this translation helpful? Give feedback.
-
|
The problem was fixed with fce00b9 |
Beta Was this translation helpful? Give feedback.
-
BREAKING Changes 2023.05.03
The
|
Beta Was this translation helpful? Give feedback.
-
Changes 2023.05.04
|
Beta Was this translation helpful? Give feedback.
-
Changes 2023.05.05
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Manuel, is it possible to deactivate the charge and discharge limits reading and limiting from the BMS? I currently have two 280A battery packs with 150A JK BMS. With low consumption I´m was charging with up to 200A. I had never a problem with the distribution to the two battery packs. |
Beta Was this translation helpful? Give feedback.
-
|
Are you using a battery aggregator? If not please see the FAQ. |
Beta Was this translation helpful? Give feedback.
-
Changes 2023.05.06
|
Beta Was this translation helpful? Give feedback.
-
|
I Have a Xiaoxiang BMS with Bluetooth. Bluetoothctl pairs and connects very well, but the driver (obviously) won't connect. Since I think the Xiaoxiang BMS is a rebranded JBD I hope it is not so difficult to alter the code. dbuslog: |
Beta Was this translation helpful? Give feedback.
-
|
Looks like you're using the JkBms driver but you said it's similar to JBD, so you should try that. |
Beta Was this translation helpful? Give feedback.
-
|
ok, that worked instantly. So now I have a connection to my jkbms.. Now only to find out why it only works for an hour or so and then stops (only reinstall seems to work). currently on nightly dev build. |
Beta Was this translation helpful? Give feedback.
-
jkbms_ble was merged into master
I opened a discussion here, so we can collect and discuss all here
Until now there are informations here:
Install latest version
If you want to try the latest driver run this line to download and install it.
wget -O /tmp/install.sh https://raw.githubusercontent.com/Louisvdw/dbus-serialbattery/dev/etc/dbus-serialbattery/install.sh && bash /tmp/install.shThen modify the
installble.shat the bottom. Uncomment (remove the#) and insert the MAC address of your Bluetooth device. You can edit the file by executingnano /data/etc/dbus-serialbattery/installble.sh. After saved the file run the filebash /data/etc/dbus-serialbattery/installble.shYou can check the logs with
tail -n 100 -f /data/log/dbus-blebattery*/current | tai64nlocalBeta Was this translation helpful? Give feedback.
All reactions