Announcement

Collapse
No announcement yet.

Let's made a PC-base metal detector with usb interface !!!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Aziz
    replied
    Hi AdrianM,

    Originally posted by AdrianM View Post
    I'm experimenting with cascoding right now. Maybe you should start a new topic on the subject and tell more about this huge power blast!
    You know, there are hanging a lot of patent trolls. I don't want to feed them right now.

    Aziz

    Leave a comment:


  • AdrianM
    replied
    Originally posted by Aziz View Post
    Hi all,

    did someone try to cascode mosfets to increase the breakdown voltage?

    Found a very tricky way to energize the targets with huge power blast (>100 mJ).
    This will stimulate the large deep targets a hell as the energizing time is large enough (> 40 µs).

    Aziz
    I'm experimenting with cascoding right now. Maybe you should start a new topic on the subject and tell more about this huge power blast!

    Leave a comment:


  • Aziz
    replied
    Hi all,

    did someone try to cascode mosfets to increase the breakdown voltage?

    Found a very tricky way to energize the targets with huge power blast (>100 mJ).
    This will stimulate the large deep targets a hell as the energizing time is large enough (> 40 µs).

    Aziz

    Leave a comment:


  • Aziz
    replied
    Iron Mineralization

    Hi all,

    I went to Chiemsee/Bavaria/Germany yesterday (BTW, a nice place). I know a place of high iron mineralization at the beach. Someone had an open fire at the beach last days. The place, where the ground was heated, all the mineralized rocks and sand turned to dark reddish (from ochre to dark red/brown color).

    Now guess, what happens to the rust I have made last time if I am heating it (>600 °C)? It also gets dark red/brown.

    It turned out to be a good idea to make naturally rusted iron oxide. I also made some more magnetite in the mean time. I am making highly mineralized hot rocks for the purpose of investigating the ground balancing.

    Objective: Detecting in the ultra-highly mineralized ground. Making detecting possible, where other detectors fail.

    Cheers,
    Aziz

    Leave a comment:


  • simonbaker
    replied
    Originally posted by Aziz View Post
    This is a task for the dongle (you need a key to drive the car).

    If you add more complexity to your dongle part code, then better.
    The best and efficient way is confusing the reverse engineer (or hacker).

    I can not give here tips how to do it of course.
    Aziz

    PS: The international copyright law protects it too. It's a free protection.
    I see - I was confused which code you were talking about.

    -SB

    Leave a comment:


  • Aziz
    replied
    Originally posted by simonbaker View Post
    But if they just copy your code and use it without modification, how are you protected? Or is that not possible?

    -SB
    This is a task for the dongle (you need a key to drive the car).

    If you add more complexity to your dongle part code, then better.
    The best and efficient way is confusing the reverse engineer (or hacker).

    I can not give here tips how to do it of course.
    Aziz

    PS: The international copyright law protects it too. It's a free protection.

    Leave a comment:


  • WM6
    replied
    Originally posted by simonbaker View Post
    But if they just copy your code and use it without modification, how are you protected? Or is that not possible?

    -SB
    The best protection is faulty non-working code.

    Leave a comment:


  • simonbaker
    replied
    Originally posted by Aziz View Post
    I hear someone complaining and putting an objection.

    This part is a linear combination of bull$hit!
    What a mess!

    Aziz
    But if they just copy your code and use it without modification, how are you protected? Or is that not possible?

    -SB

    Leave a comment:


  • Aziz
    replied
    Originally posted by Aziz View Post
    ((3.1414*a + b/3.1414)*3.1414 - b)/3.1414² = a
    I hear someone complaining and putting an objection.

    This part is a linear combination of bull$hit!
    What a mess!

    Aziz

    Leave a comment:


  • Aziz
    replied
    Originally posted by Mustafa View Post
    Hi Aziz,
    Believe me, cracking a dongle protected code doesn't require a huge investment or time.
    I don't want to start an off-topic discussion here. I just wanted to inform you that dongles can slow down some hackers but does not protect your intellectual property.
    On the other hand, most of the copy protected microcontrollers are still hackable but requires huge investment.
    Bull$hit.

    It's only a question of complexity. There are many many ways to blow up the complexity.

    Here is a simple example:
    Let's assume, a is part of an intermediate result. But I am adding further complexity to the code in this example.
    ((3.1414*a + b/3.1414)*3.1414 - b)/3.1414² = a

    The reverse engineer is questioning the following operations. Hence, it is causing a lot of confusion. Now add more bull$hitting code. He even gets more confused. Add more conditional execution branches.

    Let's consider, the reverse engineer has to debug a 100 MB of code. Well, we wish him good luck in doing this.

    One can hide an intellectual property with high complexity software design. It is much cheaper than lodging a patent.

    Don't try to debug my code. I have dozens of coding tricks to confuse you all.

    Aziz

    Leave a comment:


  • Mustafa
    replied
    Hi Aziz,
    Believe me, cracking a dongle protected code doesn't require a huge investment or time.
    I don't want to start an off-topic discussion here. I just wanted to inform you that dongles can slow down some hackers but does not protect your intellectual property.
    On the other hand, most of the copy protected microcontrollers are still hackable but requires huge investment.

    Leave a comment:


  • Aziz
    replied
    Originally posted by Mustafa View Post
    Hi,
    All dongle implementations can be broken.
    Full protection is impossible but the best way I know is you can store your rocket science routines in a copy protected micro or smartcard and communicate them using public-key cryptosystems. You should also take countermeasures to differential power analysis attacks.
    Yes, it can be broken. But it will cost an huge investment and time to do this.

    Aziz

    Leave a comment:


  • Mustafa
    replied
    Hi,
    All dongle implementations can be broken.
    Full protection is impossible but the best way I know is you can store your rocket science routines in a copy protected micro or smartcard and communicate them using public-key cryptosystems. You should also take countermeasures to differential power analysis attacks.

    Leave a comment:


  • Aziz
    replied
    Software Protection Dongle

    Hi all,

    check this out:
    Dinkey Pro protects software from illegal copying. This system locks your software to a dongle so that it can only run when that dongle is connected. Get Dinkey Pro today.


    Indeed, this makes it a lot cheaper to protect an invention. The dongle needs an extra USB interface and it can even be held in the controller box.

    I am pi$$ing on the patenting system. This is a very much cheaper solution.

    Good luck in debugging the rocket science code...

    Aziz

    Leave a comment:


  • Aziz
    replied
    Thanks

    Hi all,

    thanks for Geotech staff, mikebg and other friends for congratulating and remembering my birthday. I did forget it due to lots of work. I am getting really old (Alzheimer).

    During the last weeks, I have made lots of iron oxide/hydroxide. I have corroded 1.2 kg of fine steel wool for further mineral ground tests (type 00 and 0, 000 is the expensive but most fine mesh type, which I didn't use). It gives a good mixture of different iron oxides/minerals with some content of magnetic property too. The fine mesh steel wool corrodes quite fast after removing its oil film. I have sprayed it every day with water with a breeze of salt solved in it. It takes appoximately 3-4 weeks.

    I also have started a new PI controller hardware, which I hope makes everything simpler and cheaper. I am trying to reduce the number of sound cards for the application (from two into one). The objective is to use the internal sound card of the laptop and let the software synchronize to the PI controller. The PI controller will use a crystal controlled timer and the PC will get the timing information as well on the other channel. So external synchronisation of the PI controller is not necessary and the output channel of the sound card can be used for beeping. Note, this will save further battery power (no external sound card).

    The new PI controller is quite trivial, simple and flexible for different coil configurations too (mono, IB, anti-interference, two-box). Only minor changes will be required (mostly on front-end amplifier and transmitter stage). I am getting really sick of making a new platform every time.

    I hope, I can find an elegant and simple solution for the very accurate synchronisation without loosing much signal response spectral energy. The theory states, that it is possible. Well, I will see it.

    Cheers,

    Aziz

    Leave a comment:

Working...
X