Am Samstag, 12. Dezember 2020, 06:54:29 CET schrieb Sonali Warunjikar:
> On Fri, Dec 11, 2020 at 10:42:23PM +0530, Sonali Warunjikar wrote:
> > What is unclear is e.g. '57856 = ' is supposed to indicate length of the
> > data that follows but it's not exactly 57856 bytes following it on that
> >
On Fri, Dec 11, 2020 at 07:22:21PM +0100, Karsten Hilbert wrote:
> http://vusb-analyzer.sourceforge.net/
Due to pygtk requirement not being met on my ubuntu 20.04 above doesn't
work. Yes there are quirks to get it to work. But for now I am comfortable
looking at usbmon also and do some
On Fri, Dec 11, 2020 at 10:42:23PM +0530, Sonali Warunjikar wrote:
> What is unclear is e.g. '57856 = ' is supposed to indicate length of the
> data that follows but it's not exactly 57856 bytes following it on that
> event (line).
It seems, no matter the data length, usbmon truncates it to 32
Ping? I would like to upload sigviewer but the repository is broken.
Could you please clarify the situation?
Thank you, Andreas.
On Mon, Dec 07, 2020 at 07:14:59PM +0100, Andreas Tille wrote:
> Hi Alois,
>
> I realised that several upstream commits are pushed to the salsa
> repository. While
Hi Steffen,
Steffen Möller, on 2020-12-11 15:54:46 +0100:
> I invite for a peer review of
> https://salsa.debian.org/med-team/q2-fragment-insertion .
When looking up that package, I found out one test chokes on a
call to the command run-sepp.sh, located there:
$ rgrep run-sepp.sh
Am Fri, Dec 11, 2020 at 07:22:21PM +0100 schrieb Karsten Hilbert:
> > I can try and write code using python libusb to try and read the end point
> > 2 as seen. Any other hints?
If you do try and get some useful interfacing going in Python
you might be interested in integrating that with GNUmed
Am Fri, Dec 11, 2020 at 10:42:23PM +0530 schrieb Sonali Warunjikar:
> On Fri, Dec 11, 2020 at 11:06:06AM +0100, Karsten Hilbert wrote:
> > usbmon
>
> Attaching a usbmon trace. 2 snaps (x rays) were taken and that reflects in
> the trace. I am trying to understand the format using [1].
Well
On Fri, Dec 11, 2020 at 11:06:06AM +0100, Karsten Hilbert wrote:
> usbmon
Attaching a usbmon trace. 2 snaps (x rays) were taken and that reflects in
the trace. I am trying to understand the format using [1].
I think the lines C Bi:1:014:2 are the ones showing returned data.
What is
Am 09.12.20 um 11:51 schrieb Andreas Tille:
On Tue, Dec 08, 2020 at 02:47:57PM +0100, Steffen Möller wrote:
a series of packages on
https://docs.google.com/spreadsheets/d/1tApLhVqxRZ2VOuMH_aPUgFENQJfbLlB_PFH_Ah_q7hM/edit#gid=1251251902
somehow does not seem to have gone anywhere. I just
Am Fri, Dec 11, 2020 at 11:06:06AM +0100 schrieb Karsten Hilbert:
> > Basically when the proprietary application is open on Windows, the device
> > is connected to USB port and x-ray is shot, the image appears in that
> > software and it can be saved as a .rvg file.
>
> My next step would be to
Am Fri, Dec 11, 2020 at 03:19:26PM +0530 schrieb Sonali Warunjikar:
> >What are the resulting files you get on disk with the Windows software or
> >is it stored in a database ?
>
> It is .RVG file which is a DICOM file (as reported by file command).
> Those open fine in open source
On Fri, Dec 11, 2020 at 10:13:19AM +0100, Sebastian Hilbert wrote:
>How is the machine connected ? USB ? Network ?
To the imaging device - USB.
>What are the resulting files you get on disk with the Windows software or
>is it stored in a database ?
It is .RVG file which is a DICOM
How is the machine connected ? USB ? Network ?
What are the resulting files you get on disk with the Windows software or is it stored in a database ?
I might be worth looking into how the software actually finds out the hardware has changed. They might check the MAC address of the network
On Fri, Dec 11, 2020 at 08:48:21AM +0100, Karsten Hilbert wrote:
> The windows imaging application might work under Wine, or be
> put into a VM, and might possibly store the imaging results
> in a somehow accessible format, which you might be able to
> further process on the Linux side.
Yes, my
14 matches
Mail list logo
