> > Please do have a look at a sample header attached. If you find any fields
> > that may give any hints about the calibration or post processing that the
> > vendor software applies, please do highlight.
>
> E.g. this (undocumented aka Private) tag's value seems to be varying
> across images:
>
Am Samstag, 2. Januar 2021, 19:02:59 CET schrieb Sebastian Hilbert:
> The company being acquired is correct. The license stuff is a different
> story. The license check might entirely happen in their commercial
> software. In other words talking to the device might be possible without
> any
draw four lines touching the circle, each pair at 90°
draw a line splitting each 90° in half (at 45° that is) going through the circle
the intersection of those two midlines should be the centre of the circle :-)
better: fit a square around the circle ...
Karsten
> Gesendet: Dienstag, 05.
On Mon, Jan 04, 2021 at 09:42:08AM +0100, Sebastian Hilbert wrote:
> There is some info on the licensing stuff in this document
> http://hsc.myvnc.com/last/good/upload/faq/pdf/CS3000_Dental_Imaging_IG.pdf[2]
This version of procedure is much newer than the one I bought in 2015.
Both node locked
On Sun, Jan 03, 2021 at 02:48:58PM +0100, Karsten Hilbert wrote:
>
> https://forums.anandtech.com/threads/advice-on-sizing-a-server-for-25-users-dental-office.2171855/
Feel for them.
Just to contrast it, the whole activity I did started with a desire to use
a Raspbery Pi 4 (now that it
Am Sun, Jan 03, 2021 at 10:42:23AM +0530 schrieb Sonali Warunjikar:
> > Test his code with another RGV5200 sensor. I would try to find
> > dental office IT user groups and ask if anyone owns that sensor
> > and would be willing to test ...
>
> The problem is: it limits the universe to those whom
On Sat, Jan 02, 2021 at 07:11:16PM +0100, Karsten Hilbert wrote:
> Mayuresh (Ganesha? ;-)
Good grasp and patience to search!
> Test his code with another RGV5200 sensor. I would try to find
> dental office IT user groups and ask if anyone owns that sensor
> and would be willing to test ...
Yes.
On Sat, Jan 02, 2021 at 07:02:59PM +0100, Sebastian Hilbert wrote:
>This theory would have to be checked with a 3rd party software that
>officially supports the device - if such a thing exists.
We saw at least one third party software on this thread which insists that
the carestream
As for the "best" post-processing settings for the raw image could the
following scenario help ?
- setup a passthrough, logging, usb monitor
- capture an x-ray image with the Windows software
- simultaneously capture the raw image within the monitor
Then, manually with, say, GIMP, adjust
> If someone else had a sensor and could make the current code work as is, this
> would exclude a license in unique to the sensor
That's exactly what was proposed.
Next step would be to identify another user of said
sensor who'd be willing to have the code run.
Karsten
> The company being acquired is correct. The license stuff is a different
> story. The license check might entirely happen in their
> commercial software. In other words talking to the device might be possible
> without any license check. If one knows how to talk to the device.
>
> This theory
> Given this (page 5)
>
>
> https://www.atlasresell.com/sites/default/files/KodakTrophyWindowsGuide.pdf
and this
http://www.unident.ru/en/news/Carestream-120-years-in-the-service-of-dentistry-13633.phtml
:-o
Karsten
If someone else had a sensor and could make the current code work as is, this would exclude a license in unique to the sensor--Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 02.01.21, 18:55 schrieb Karsten Hilbert :
Given this (page 5)
The company being acquired is correct. The license stuff is a different story. The license check might entirely happen in their commercial software. In other words talking to the device might be possible without any license check. If one knows how to talk to the device.This theory would have
Given this (page 5)
https://www.atlasresell.com/sites/default/files/KodakTrophyWindowsGuide.pdf
I've got a theory on the two devices:
Once upon a time an x-ray sensor was developed and
certified by Trophy.
Later, Trophy was acquired by Kodak.
Eventually, Kodak started marketing its
> The latter is coming closer to the reality, but not sure it's accurate
> enough as yet. May be there was a gap between the finger and the sensor
> when trial x ray was taken as our attention was on usb interface rather
> than lengths (getting computed length smaller than the actual one of the
>
> [1] confirms the pixel size to be 19 micro. pypng does have a way to
> supply it. Now it's reporting sensible distances, but have to check and
> see if there are calibration issues.
>
> BTW any idea, what "True (measured) resolution = 16lp/mm" means in [1]? It
> seems it's called line pairs per
> It is showing the length of index finger distal phalanx close to 1ft! (I
> assure that's not the reality!)
:-)
> Can anyone suggest which field it is? (Another point in favor of DICOM,
> but let me sort out the issue with a generic image first.)
Sure, I would first get one image format
> > Install a freshly downloaded version (say, a trial version) of your
> > imaging software (or of another software documented to support your
> > sensor). Plug in the sensor and monitor the USB flow.
>
> Or, since the sensor offers a TWAIN driver, you might try to install that
> and access the
> Another idea: get an entirely fresh machine (laptop/VM) that never knew
> anything of your clinic/sensor before. A Windows machine, that is.
>
> Install a freshly downloaded version (say, a trial version) of your
> imaging software (or of another software documented to support your
> sensor).
> I'll refine the code a bit and open it up. But the unfortunate nature of
> such exercise is where I have a driver but I do not 'know' the protocol. I
> am merely playing back the traces and those traces could be tied to my
> license key.
Another idea: get an entirely fresh machine (laptop/VM)
> I'll refine the code a bit and open it up. But the unfortunate nature of
> such exercise is where I have a driver but I do not 'know' the protocol. I
> am merely playing back the traces and those traces could be tied to my
> license key.
You don't, by any chance, happen to be able to access
> would give much more credit to ... your own persistence.
Very true. Pulling this off is quite a feat unless one is
a fairly experienced hard/soft tinkerer.
Karsten
> Yes, it's now closer to a real X ray. The Dr still sees some problems, but
> I think it will need some experiments with exposure, brightness and
> contrast.
Typically, there's presets for those but as a doctor one always plays
with them such settings during the diagnostics process.
So, I
> On Thu, Dec 31, 2020 at 02:15:33PM +0530, Sonali Warunjikar wrote:
> > Now the USB layer is as such over. The challenge now shifts to the format
> > of the data gathered.
I would also try the following:
- create a small loopback filesystem
- mount it
- fill it with a nulls-only file (cp from
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
26 matches
Mail list logo
