Gallery, Projects and General > Neat Stuff

DRO..... PC based

<< < (4/8) > >>

AR1911:
Good to know Yuriy.
Now that i think of it, I have an unused Mini-TV stick that runs 4.1, so I guess I could use my 40" shop tv for a DRO  :thumbup:display   

vtsteam:
These just arrived today. Very reasonably priced, and the daughter card is actually all that is needed for a DRO once it's programmed. Looks like a very nicely made set of packages -- USB cables included!

My problem is probably going to be displaying the output from these with old Windows or old Android, or even DOS. I do have a very old 486 laptop running win95 with a serial port that is nice and compact, and otherwise useless. And the aforementioned tablet running an early Android with a USB port. Either would be great to re-purpose :coffee:



Bigbadbugga:

--- Quote from: sigt on August 27, 2013, 12:17:30 AM ---Saw this on another site, Android based dro using the igaging scales and an Arduino board.

http://www.yuriystoys.com/p/android-dro.html

Simon

--- End quote ---

This really interests me. I've been reading the 'arduino for dummies' book as a result of this post and I've decided to build one of these for the lathe. And possibly a second one for my mill when I get it.

It's been 20 yrs since I've dabbled in electronics and things have changed a little since, but I'm looking forward to catching up a bit :)

BillTodd:
Glad to see you here Yuriy:-)

I plan on adapting my PIC code (see:  www.cnczone.com/forums/pic_programing_design/62704-pic_based_dro.html ) to drive your app, and i might need some guidance regarding the interface.

My pic code can read most of the older Chinese scales both binary and bcd formats, using a single 8pin pic per axis.

Regards

Bill

ycroosh:
Bill,
As long as the output is in the expected format, you should be fine.
The main requirements are:
has to start with an axis name
there has to be at most one "-" (minus) sign
there has to be at least one digit
the string needs to be terminated by a semicolon ";"

The order or frequency doesn't matter. The state machine resets after each axis (terminator), so you can send something like this:
X1234;x1234;x1234;y234;x1234;z0; etc.

The application expects at least one reading per second or it will be switch to the "Connection Lost" state. In five second it will drop the connection and stop listening.

Another consideration is that the app averages the last three readings (to reduce jitter). If you do the same on your end the readout will be pretty slow.
In the next version I will add a switch that will allow turning the "antialiasing" off...

Hope this helps
Thank you
Yuriy

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version