Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #273913 > unrolled thread

battery tester

Back to article view | Back to linux.debian.user

Contents

  battery tester "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-10-20 20:00 +0200
    Re: battery tester David Christensen <dpchrist@holgerdanske.com> - 2024-10-21 03:10 +0200
    Re: battery tester Darac Marjal <lists-debian-user@bendel.debian.org> - 2024-10-21 13:50 +0200
      Re: battery tester "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-10-23 16:30 +0200
        Re: battery tester Max Nikulin <manikulin@gmail.com> - 2024-10-24 03:40 +0200
          Re: battery tester "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-10-24 21:30 +0200
            Re: battery tester <tomas@tuxteam.de> - 2024-10-24 21:30 +0200
              Re: battery tester "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-10-24 21:40 +0200
            Re: battery tester Jeffrey Walton <noloader@gmail.com> - 2024-10-24 22:10 +0200
            Re: battery tester Dan Ritter <dsr@randomstring.org> - 2024-10-24 22:30 +0200
              Re: battery tester Max Nikulin <manikulin@gmail.com> - 2024-10-25 03:30 +0200
            Re: battery tester Joe <joe@jretrading.com> - 2024-10-24 23:00 +0200
    Re: battery tester George at Clug <Clug@goproject.info> - 2024-10-22 08:50 +0200
      Re: battery tester "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-10-23 17:00 +0200
      Re: battery tester Jeffrey Walton <noloader@gmail.com> - 2024-10-23 17:20 +0200
        Re: battery tester <tomas@tuxteam.de> - 2024-10-23 20:20 +0200
        Re: battery tester Max Nikulin <manikulin@gmail.com> - 2024-10-24 04:10 +0200

#273913 — battery tester

I have here an Ancel BA101 battery tester,  discovered by way of a YT video,  and it's proved to be a handy gadget to have.  In the "user manual" for this device (available online) it talks about the ability to print the data.  Which requires you to connect it to a computer by way of a USB cable plugged into the tester's USB port.  The documentation further refers to inserting a CD into the computer (it didn't come with any CD),  making sure a driver was installed,  then "open the print software" and select the appropriate COM port.

I'm pretty sure that I don't need to install a driver,  since I can connect all sorts of USB stuff to this computer with no problems.  I'm not sure what print software they refer to here --  the illustration seems to refer to "PrintCOM v1.50421" which appears to have print, clear,  and COM port selection options but also appears to be some kind of windoze software.

How would I address accessing this device under linux and getting its info out to my printer?


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

[toc] | [next] | [standalone]

#273929

On 10/20/24 10:51, Roy J. Tellason, Sr. wrote:
> I have here an Ancel BA101 battery tester,  discovered by way of a YT video,  and it's proved to be a handy gadget to have.  In the "user manual" for this device (available online) it talks about the ability to print the data.  Which requires you to connect it to a computer by way of a USB cable plugged into the tester's USB port.  The documentation further refers to inserting a CD into the computer (it didn't come with any CD),  making sure a driver was installed,  then "open the print software" and select the appropriate COM port.
> 
> I'm pretty sure that I don't need to install a driver,  since I can connect all sorts of USB stuff to this computer with no problems.  I'm not sure what print software they refer to here --  the illustration seems to refer to "PrintCOM v1.50421" which appears to have print, clear,  and COM port selection options but also appears to be some kind of windoze software.
> 
> How would I address accessing this device under linux and getting its info out to my printer?


I suggest that you contact Ansel technical support and tell them the 
model and serial numbers of the tester, the make and model of your 
computer, and what operating system you are running.


David

[toc] | [prev] | [next] | [standalone]

#273946

[Multipart message — attachments visible in raw view] — view raw

On 20/10/2024 18:51, Roy J. Tellason, Sr. wrote:
> I have here an Ancel BA101 battery tester,  discovered by way of a YT video,  and it's proved to be a handy gadget to have.  In the "user manual" for this device (available online) it talks about the ability to print the data.  Which requires you to connect it to a computer by way of a USB cable plugged into the tester's USB port.  The documentation further refers to inserting a CD into the computer (it didn't come with any CD),  making sure a driver was installed,  then "open the print software" and select the appropriate COM port.
>
> I'm pretty sure that I don't need to install a driver,  since I can connect all sorts of USB stuff to this computer with no problems.  I'm not sure what print software they refer to here --  the illustration seems to refer to "PrintCOM v1.50421" which appears to have print, clear,  and COM port selection options but also appears to be some kind of windoze software.
>
> How would I address accessing this device under linux and getting its info out to my printer?

COM ports are serial ports and are a very basic method of communication. 
Linux supports COM ports (the ports themselves) really well. You can 
use, say, minicom or screen to communicate with a device on the COM 
port. However, there are a number of challenges to overcome before 
you'll be able to use the tester.

Firstly, the parameters of the communication are rather complex (what 
speed, do you need parity bits / stop bits, who controls the flow of 
data). If you can find this information, you can tell the computer how 
to communicate with the other device. As a start, though, you can try 
"9600 8n1" (9600 bits per second, 8 bits per byte, NO parity, 1 stop 
bit) as this is the most common setting.

Next, you need to find out what data to send/receive over the port. If 
you're lucky, the device will be really simple and will just print 
battery results in plain text when you communicate. But if you're 
unlucky, you'll need to send it commands to tell it to do things. This 
communication protocol could be plain text, there could be a menu, it 
could be binary.. there are even some protocols (APC UPSes, I'm looking 
at you) which just consist of sending a single character to activate a 
function - if you happen to send the wrong character, something untoward 
might happen (in this case, turning off the UPS).

As another poster advised, only Ancel /really/ know the right way to use 
their device.

[toc] | [prev] | [next] | [standalone]

#273980

On Monday 21 October 2024 07:47:39 am Darac Marjal wrote:
> 
> On 20/10/2024 18:51, Roy J. Tellason, Sr. wrote:
> > I have here an Ancel BA101 battery tester,  discovered by way of a YT video,  and it's proved to be a handy gadget to have.  In the "user manual" for this device (available online) it talks about the ability to print the data.  Which requires you to connect it to a computer by way of a USB cable plugged into the tester's USB port.  The documentation further refers to inserting a CD into the computer (it didn't come with any CD),  making sure a driver was installed,  then "open the print software" and select the appropriate COM port.
> >
> > I'm pretty sure that I don't need to install a driver,  since I can connect all sorts of USB stuff to this computer with no problems.  I'm not sure what print software they refer to here --  the illustration seems to refer to "PrintCOM v1.50421" which appears to have print, clear,  and COM port selection options but also appears to be some kind of windoze software.
> >
> > How would I address accessing this device under linux and getting its info out to my printer?
> 
> COM ports are serial ports and are a very basic method of communication. 
> Linux supports COM ports (the ports themselves) really well. 

Having had to configure modems and such back when,  I understand this...

> You can  use, say, minicom or screen to communicate with a device on the COM 
> port. 

For some reason neither of those seems to be installed on this machine.

> However, there are a number of challenges to overcome before  
> you'll be able to use the tester.
> 
> Firstly, the parameters of the communication are rather complex (what 
> speed, do you need parity bits / stop bits, who controls the flow of 
> data). 

Been there,  done that.

> If you can find this information, you can tell the computer how  
> to communicate with the other device. As a start, though, you can try 
> "9600 8n1" (9600 bits per second, 8 bits per byte, NO parity, 1 stop 
> bit) as this is the most common setting.

Yup.  Or sometimes faster.
 
> Next, you need to find out what data to send/receive over the port. If 
> you're lucky, the device will be really simple and will just print 
> battery results in plain text when you communicate. But if you're 
> unlucky, you'll need to send it commands to tell it to do things. This 
> communication protocol could be plain text, there could be a menu, it 
> could be binary.. there are even some protocols (APC UPSes, I'm looking 
> at you) which just consist of sending a single character to activate a 
> function - if you happen to send the wrong character, something untoward 
> might happen (in this case, turning off the UPS).

Connecting the device with a USB cable I see it wake up,  at which point there's a menu on its screen.  One selection there is to print,  so I'm guessing that it might be that simple.  What I need is to somehow redirect what's coming from the device to where I can use it.
 
> As another poster advised, only Ancel /really/ know the right way to use 
> their device.
 
Contacting them involved setting up an account,  a bit cumbersome.  I haven't seen any reply yet.


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

[toc] | [prev] | [next] | [standalone]

#273994

On 23/10/2024 21:25, Roy J. Tellason, Sr. wrote:
> Connecting the device with a USB cable I see it wake up,  at which point
> there's a menu on its screen.

Start "journalctl -f" as root before connecting the device. Logs may 
contain some hints how to communicate with it. Perhaps "udevadm monitor" 
with some options may provide more low level info.

[toc] | [prev] | [next] | [standalone]

#274005

On Wednesday 23 October 2024 09:38:04 pm Max Nikulin wrote:
> On 23/10/2024 21:25, Roy J. Tellason, Sr. wrote:
> > Connecting the device with a USB cable I see it wake up,  at which point
> > there's a menu on its screen.
> 
> Start "journalctl -f" as root before connecting the device. Logs may 
> contain some hints how to communicate with it. Perhaps "udevadm monitor" 
> with some options may provide more low level info.

I did find some info in one of the log files:

Oct 24 15:14:28 Workstation1 kernel: [1915052.140032] usb 7-1.4.4: new full-speed USB device number 13 using ehci-pci
Oct 24 15:14:28 Workstation1 kernel: [1915052.249009] usb 7-1.4.4: New USB device found, idVendor=1a86, idProduct=7523
Oct 24 15:14:28 Workstation1 kernel: [1915052.249012] usb 7-1.4.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Oct 24 15:14:28 Workstation1 kernel: [1915052.249014] usb 7-1.4.4: Product: USB Serial
Oct 24 15:14:28 Workstation1 kernel: [1915052.249308] ch341 7-1.4.4:1.0: ch341-uart converter detected
Oct 24 15:14:28 Workstation1 kernel: [1915052.251232] usb 7-1.4.4: ch341-uart converter now attached to ttyUSB0
Oct 24 15:14:28 Workstation1 mtp-probe: checking bus 7, device 13: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.4/7-1.4.4"
Oct 24 15:14:28 Workstation1 mtp-probe: bus: 7, device: 13 was not an MTP device
Oct 24 15:14:29 Workstation1 org.xfce.FileManager[1332]: thunar-volman: Unsupported USB device type "usb".
Oct 24 15:14:29 Workstation1 org.xfce.FileManager[1332]: thunar-volman: Unsupported USB device type "ch341".

I don't recognize that mtp stuff,  and don't know how thunar-volman gets into the picture...

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

[toc] | [prev] | [next] | [standalone]

#274006

[Multipart message — attachments visible in raw view] — view raw

On Thu, Oct 24, 2024 at 03:21:24PM -0400, Roy J. Tellason, Sr. wrote:
> On Wednesday 23 October 2024 09:38:04 pm Max Nikulin wrote:
> > On 23/10/2024 21:25, Roy J. Tellason, Sr. wrote:
> > > Connecting the device with a USB cable I see it wake up,  at which point
> > > there's a menu on its screen.
> > 
> > Start "journalctl -f" as root before connecting the device. Logs may 
> > contain some hints how to communicate with it. Perhaps "udevadm monitor" 
> > with some options may provide more low level info.
> 
> I did find some info in one of the log files:
> 
> Oct 24 15:14:28 Workstation1 kernel: [1915052.140032] usb 7-1.4.4: new full-speed USB device number 13 using ehci-pci
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249009] usb 7-1.4.4: New USB device found, idVendor=1a86, idProduct=7523
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249012] usb 7-1.4.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249014] usb 7-1.4.4: Product: USB Serial
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249308] ch341 7-1.4.4:1.0: ch341-uart converter detected
> Oct 24 15:14:28 Workstation1 kernel: [1915052.251232] usb 7-1.4.4: ch341-uart converter now attached to ttyUSB0
                                                                                                          ^^^^^^^

There it is. Now you can try "cat /dev/ttyUSB0" and wiggle your
tester. Perhaps it just dumps measurements out the serial?

(More involved tests might offer better success chances, of course :)

Cheers
-- 
t

[toc] | [prev] | [next] | [standalone]

#274008

On Thursday 24 October 2024 03:26:06 pm tomas@tuxteam.de wrote:
> On Thu, Oct 24, 2024 at 03:21:24PM -0400, Roy J. Tellason, Sr. wrote:
> > On Wednesday 23 October 2024 09:38:04 pm Max Nikulin wrote:
> > > On 23/10/2024 21:25, Roy J. Tellason, Sr. wrote:
> > > > Connecting the device with a USB cable I see it wake up,  at which point
> > > > there's a menu on its screen.
> > > 
> > > Start "journalctl -f" as root before connecting the device. Logs may 
> > > contain some hints how to communicate with it. Perhaps "udevadm monitor" 
> > > with some options may provide more low level info.
> > 
> > I did find some info in one of the log files:
> > 
> > Oct 24 15:14:28 Workstation1 kernel: [1915052.140032] usb 7-1.4.4: new full-speed USB device number 13 using ehci-pci
> > Oct 24 15:14:28 Workstation1 kernel: [1915052.249009] usb 7-1.4.4: New USB device found, idVendor=1a86, idProduct=7523
> > Oct 24 15:14:28 Workstation1 kernel: [1915052.249012] usb 7-1.4.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
> > Oct 24 15:14:28 Workstation1 kernel: [1915052.249014] usb 7-1.4.4: Product: USB Serial
> > Oct 24 15:14:28 Workstation1 kernel: [1915052.249308] ch341 7-1.4.4:1.0: ch341-uart converter detected
> > Oct 24 15:14:28 Workstation1 kernel: [1915052.251232] usb 7-1.4.4: ch341-uart converter now attached to ttyUSB0
>                                                                                                           ^^^^^^^
> 
> There it is. Now you can try "cat /dev/ttyUSB0" and wiggle your
> tester. Perhaps it just dumps measurements out the serial?

Tried that,  and when I plug the device in and it lights up,  I select the print option.  Then it displays "print wait" on the screen and after a few seconds goes back to the menu.  Nothing comes through on the terminal.  Perhaps a baud rate mismatch?  I'll have to fiddle with it some more...
 
> (More involved tests might offer better success chances, of course :)
> 
> Cheers



-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

[toc] | [prev] | [next] | [standalone]

#274009

On Thu, Oct 24, 2024 at 3:20 PM Roy J. Tellason, Sr. <roy@rtellason.com> wrote:
>
> On Wednesday 23 October 2024 09:38:04 pm Max Nikulin wrote:
> > On 23/10/2024 21:25, Roy J. Tellason, Sr. wrote:
> > > Connecting the device with a USB cable I see it wake up,  at which point
> > > there's a menu on its screen.
> >
> > Start "journalctl -f" as root before connecting the device. Logs may
> > contain some hints how to communicate with it. Perhaps "udevadm monitor"
> > with some options may provide more low level info.
>
> I did find some info in one of the log files:
>
> Oct 24 15:14:28 Workstation1 kernel: [1915052.140032] usb 7-1.4.4: new full-speed USB device number 13 using ehci-pci
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249009] usb 7-1.4.4: New USB device found, idVendor=1a86, idProduct=7523
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249012] usb 7-1.4.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249014] usb 7-1.4.4: Product: USB Serial
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249308] ch341 7-1.4.4:1.0: ch341-uart converter detected
> Oct 24 15:14:28 Workstation1 kernel: [1915052.251232] usb 7-1.4.4: ch341-uart converter now attached to ttyUSB0
> Oct 24 15:14:28 Workstation1 mtp-probe: checking bus 7, device 13: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.4/7-1.4.4"
> Oct 24 15:14:28 Workstation1 mtp-probe: bus: 7, device: 13 was not an MTP device
> Oct 24 15:14:29 Workstation1 org.xfce.FileManager[1332]: thunar-volman: Unsupported USB device type "usb".
> Oct 24 15:14:29 Workstation1 org.xfce.FileManager[1332]: thunar-volman: Unsupported USB device type "ch341".

It might be possible to update the PCI Id database, but I am not sure
if it will help you in this instance. You might give this a try:

    if [[ -n $(command -v update-pciids 2>/dev/null) ]]; then
        echo "Updating PCI Ids"
        update-pciids -q 1>/dev/null
    fi

> I don't recognize that mtp stuff,  and don't know how thunar-volman gets into the picture...

MTP is a file transfer protocol. I see it as an option on Android. I
don't recall it creeping into my Linux desktops.

You might try to look at how the ANCEL program communicates with the
device. For that, I recommend installing Windows into a VM, and then
installing a port monitoring program to sniff the traffic. I would
guess USB-OTG has something to do with it. You want the battery tester
in device or slave mode so it transfers data.

Jeff

[toc] | [prev] | [next] | [standalone]

#274010

Roy J. Tellason, Sr. wrote: 
> On Wednesday 23 October 2024 09:38:04 pm Max Nikulin wrote:
> > On 23/10/2024 21:25, Roy J. Tellason, Sr. wrote:
> > > Connecting the device with a USB cable I see it wake up,  at which point
> > > there's a menu on its screen.
> > 
> > Start "journalctl -f" as root before connecting the device. Logs may 
> > contain some hints how to communicate with it. Perhaps "udevadm monitor" 
> > with some options may provide more low level info.
> 
> I did find some info in one of the log files:
> 
> Oct 24 15:14:28 Workstation1 kernel: [1915052.140032] usb 7-1.4.4: new full-speed USB device number 13 using ehci-pci
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249009] usb 7-1.4.4: New USB device found, idVendor=1a86, idProduct=7523
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249012] usb 7-1.4.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249014] usb 7-1.4.4: Product: USB Serial
> Oct 24 15:14:28 Workstation1 kernel: [1915052.249308] ch341 7-1.4.4:1.0: ch341-uart converter detected
> Oct 24 15:14:28 Workstation1 kernel: [1915052.251232] usb 7-1.4.4: ch341-uart converter now attached to ttyUSB0
> Oct 24 15:14:28 Workstation1 mtp-probe: checking bus 7, device 13: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.4/7-1.4.4"
> Oct 24 15:14:28 Workstation1 mtp-probe: bus: 7, device: 13 was not an MTP device
> Oct 24 15:14:29 Workstation1 org.xfce.FileManager[1332]: thunar-volman: Unsupported USB device type "usb".
> Oct 24 15:14:29 Workstation1 org.xfce.FileManager[1332]: thunar-volman: Unsupported USB device type "ch341".
> 
> I don't recognize that mtp stuff,  and don't know how thunar-volman gets into the picture...

mtp is media transfer protocol, an alternative to USB Mass
Storage. Hence thunar volume manager.

Overall it looks like the mtp-probe is deluded and trying to
mount the unmountable.

-dsr-

[toc] | [prev] | [next] | [standalone]

#274022

On 25/10/2024 03:07, Dan Ritter wrote:
> Roy J. Tellason, Sr. wrote:
>> Oct 24 15:14:28 Workstation1 kernel: [1915052.251232] usb 7-1.4.4: ch341-uart converter now attached to ttyUSB0
>> Oct 24 15:14:28 Workstation1 mtp-probe: checking bus 7, device 13: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.4/7-1.4.4"
>> Oct 24 15:14:28 Workstation1 mtp-probe: bus: 7, device: 13 was not an MTP device
[...]
> mtp is media transfer protocol, an alternative to USB Mass
> Storage. Hence thunar volume manager.

MTP likely may be ignored. There is a little chance though that its udev 
rule sends something to the device. When installed, this rule executed 
for most of (or even for all) plugged USB devices.

Perhaps vendor software sends some commands to the serial port when 
print is requested.

[toc] | [prev] | [next] | [standalone]

#274018

On Thu, 24 Oct 2024 15:21:24 -0400
"Roy J. Tellason, Sr." <roy@rtellason.com> wrote:

> On Wednesday 23 October 2024 09:38:04 pm Max Nikulin wrote:
> > On 23/10/2024 21:25, Roy J. Tellason, Sr. wrote:  
> > > Connecting the device with a USB cable I see it wake up,  at
> > > which point there's a menu on its screen.  
> > 
> > Start "journalctl -f" as root before connecting the device. Logs
> > may contain some hints how to communicate with it. Perhaps "udevadm
> > monitor" with some options may provide more low level info.  
> 
> I did find some info in one of the log files:
> 
> Oct 24 15:14:28 Workstation1 kernel: [1915052.140032] usb 7-1.4.4:
> new full-speed USB device number 13 using ehci-pci Oct 24 15:14:28
> Workstation1 kernel: [1915052.249009] usb 7-1.4.4: New USB device
> found, idVendor=1a86, idProduct=7523 Oct 24 15:14:28 Workstation1
> kernel: [1915052.249012] usb 7-1.4.4: New USB device strings: Mfr=0,
> Product=2, SerialNumber=0 Oct 24 15:14:28 Workstation1 kernel:
> [1915052.249014] usb 7-1.4.4: Product: USB Serial Oct 24 15:14:28
> Workstation1 kernel: [1915052.249308] ch341 7-1.4.4:1.0: ch341-uart
> converter detected Oct 24 15:14:28 Workstation1 kernel:
> [1915052.251232] usb 7-1.4.4: ch341-uart converter now attached to
> ttyUSB0 Oct 24 15:14:28 Workstation1 mtp-probe: checking bus 7,
> device 13:
> "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.4/7-1.4.4" Oct 24
> 15:14:28 Workstation1 mtp-probe: bus: 7, device: 13 was not an MTP
> device Oct 24 15:14:29 Workstation1 org.xfce.FileManager[1332]:
> thunar-volman: Unsupported USB device type "usb". Oct 24 15:14:29
> Workstation1 org.xfce.FileManager[1332]: thunar-volman: Unsupported
> USB device type "ch341".
> 
> I don't recognize that mtp stuff,  and don't know how thunar-volman
> gets into the picture...
> 

It's just seeing what software you have installed that is likely to want
to talk to the device, and it didn't find any. It's mostly looking for
USB drives. But you can see it has assigned ttyUSB0 to the device. See
my other post, but once you have the right serial parameters set by
stty, you can just cat /dev/ttyUSB0 to see if your gadget is sending
anything by itself. Or any such text will appear in the CuteCom window,
if you run that. Other serial monitors are available...

-- 
Joe

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#273964

Hi,

I have been following the comments on this topic.  From what I can tell, the company does not provide Linux drivers or software. 

A friend of mine managed to access a heart rate monitor by using DOS emulation and the original DOS software.

Maybe you could use Wine to run the Windows "Printer_boxed.exe" software (see download page URL below) ?

Not having Ancel BA101 battery tester, I am not able to test.

https://www.anceltech.com/product/detail?id=1086074596467142656

https://www.anceltech.com/Public/Uploads/filetxt/20211007/6638733e-2053-4706-b775-e85cc12931ed.pdf

Here are a few words from the later (BA201) model's manual says:

https://www.anceltech.com/Public/Uploads/filetxt/20211007/8f5feaf1-3a4d-4090-89cd-d655de60c21d.pdf

This function allows you to update the tool software.
To update the tool, you need the following items.
1. ANCEL BA201 Battery tester tool
2. A windows PC or laptop with USB ports
3. A USB cable

1) downloading the applications from ANCEL website.
www.anceltech.com
2) run btlink.exe in your computer(Mac OS and linux does not compatible)

3.5 Print
The Print Data function allows printing out testing data recorded by the testing tool for or customized test reports.
To print out retrieved data, you need the following tools:
1.The tester tool
2.A windows PC or Iaptop with USB ports
3.A USB cable
1) download the applications from ANCEL website.
www.anceltech.com
2) connect the tester tool to computer with the USB cable supplied
3) run btlink.exe in your computer, as below

Hope this helps,

George.


On Monday, 21-10-2024 at 04:51 Roy J. Tellason, Sr. wrote:
> I have here an Ancel BA101 battery tester,  discovered by way of a YT video,  and it's proved to be a handy gadget to have.  In the "user manual" for this device (available online) it talks about the ability to print the data.  Which requires you to connect it to a computer by way of a USB cable plugged into the tester's USB port.  The documentation further refers to inserting a CD into the computer (it didn't come with any CD),  making sure a driver was installed,  then "open the print software" and select the appropriate COM port.
> 
> I'm pretty sure that I don't need to install a driver,  since I can connect all sorts of USB stuff to this computer with no problems.  I'm not sure what print software they refer to here --  the illustration seems to refer to "PrintCOM v1.50421" which appears to have print, clear,  and COM port selection options but also appears to be some kind of windoze software.
> 
> How would I address accessing this device under linux and getting its info out to my printer?
> 
> 
> -- 
> Member of the toughest, meanest, deadliest, most unrelenting -- and
> ablest -- form of life in this section of space,  a critter that can
> be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
> -
> Information is more dangerous than cannon to a society ruled by lies. --James 
> M Dakin
> 
> 

[toc] | [prev] | [next] | [standalone]

#273981

On Tuesday 22 October 2024 02:39:36 am George at Clug wrote:
> Hi,
> 
> I have been following the comments on this topic.  From what I can tell, the company does not provide Linux drivers or software. 
> 
> A friend of mine managed to access a heart rate monitor by using DOS emulation and the original DOS software.
> 
> Maybe you could use Wine to run the Windows "Printer_boxed.exe" software (see download page URL below) ?

That's way more complicated than I care to get here...
 
(...)
> Here are a few words from the later (BA201) model's manual says:
> 
> https://www.anceltech.com/Public/Uploads/filetxt/20211007/8f5feaf1-3a4d-4090-89cd-d655de60c21d.pdf

I did look that over,  and from what I can see it's a pretty similar device,  the major difference being that the display is very graphic,  where on the one I have it's all text.


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

[toc] | [prev] | [next] | [standalone]

#273982

On Tue, Oct 22, 2024 at 6:38 AM George at Clug <Clug@goproject.info> wrote:
>
> I have been following the comments on this topic.  From what I can tell, the company does not provide Linux drivers or software.
>
> A friend of mine managed to access a heart rate monitor by using DOS emulation and the original DOS software.
>
> Maybe you could use Wine to run the Windows "Printer_boxed.exe" software (see download page URL below) ?
>
> Not having Ancel BA101 battery tester, I am not able to test.
>
> https://www.anceltech.com/product/detail?id=1086074596467142656
>
> https://www.anceltech.com/Public/Uploads/filetxt/20211007/6638733e-2053-4706-b775-e85cc12931ed.pdf
>
> Here are a few words from the later (BA201) model's manual says:
>
> https://www.anceltech.com/Public/Uploads/filetxt/20211007/8f5feaf1-3a4d-4090-89cd-d655de60c21d.pdf
>
> This function allows you to update the tool software.
> To update the tool, you need the following items.
> 1. ANCEL BA201 Battery tester tool
> 2. A windows PC or laptop with USB ports
> 3. A USB cable
>
> 1) downloading the applications from ANCEL website.
> www.anceltech.com
> 2) run btlink.exe in your computer(Mac OS and linux does not compatible)
>
> 3.5 Print
> The Print Data function allows printing out testing data recorded by the testing tool for or customized test reports.
> To print out retrieved data, you need the following tools:
> 1.The tester tool
> 2.A windows PC or Iaptop with USB ports
> 3.A USB cable
> 1) download the applications from ANCEL website.
> www.anceltech.com
> 2) connect the tester tool to computer with the USB cable supplied
> 3) run btlink.exe in your computer, as below

Installing software from a Chinese vendor does not give me a warm and
fuzzy feeling.

Jeff

[toc] | [prev] | [next] | [standalone]

#273983

[Multipart message — attachments visible in raw view] — view raw

On Wed, Oct 23, 2024 at 11:14:52AM -0400, Jeffrey Walton wrote:

[...]

> Installing software from a Chinese vendor does not give me a warm and
> fuzzy feeling.

Yes, like
 - Cisco
 - Solarwinds
 - Microsoft
 - Crowdstrike

oh, wait...

Cheers
-- 
t

[toc] | [prev] | [next] | [standalone]

#273995

On 23/10/2024 22:14, Jeffrey Walton wrote:
> On Tue, Oct 22, 2024 at 6:38 AM George at Clug wrote:
>> 1) download the applications from ANCEL website.
>> www.anceltech.com
[...]
> Installing software from a Chinese vendor does not give me a warm and
> fuzzy feeling.

The question is whether there is an alternative device supporting a 
widely used or at least documented communication protocols and having 
price that is not prohibitively high. E.g. some lab equipment uses 
USB-TMC and text commands.

Otherwise a VM may be a rescue. There is a chance to determine protocol 
using a USB sniffing tool like WireShark, but it is off-topic on this 
mailing list.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web