Results 1 to 5 of 5

Thread: Communication with OMA tracer

  1. #1
    OptiBoard Apprentice gsmahesh's Avatar
    Join Date
    Jul 2010
    Location
    Kuwait City, Kuwait
    Occupation
    Lens Manufacturer
    Posts
    33

    Confused Communication with OMA tracer

    I am trying to develope a program to get the shape data from the tracer via RS232. I am using Visual Basic as the language.After sending the shape at first I am getting like below
    Click image for larger version. 

Name:	20180610_161905.jpg 
Views:	6 
Size:	86.9 KB 
ID:	13930
    Then I send the request like Click image for larger version. 

Name:	20180610_161744.jpg 
Views:	6 
Size:	28.5 KB 
ID:	13931
    Second time I received the following information;
    Click image for larger version. 

Name:	20180610_161944.jpg 
Views:	9 
Size:	67.1 KB 
ID:	13932
    But still the shape data is not there. What request I have to send to the tracer for the shape. I am getting the information except the shape :)

    Tracer : Nidek ICE1000

  2. #2
    OptiBoard Apprentice
    Join Date
    Jun 2005
    Location
    Manchester, CT
    Occupation
    Other Optical Manufacturer or Vendor
    Posts
    17
    TRCFMT=3 is a binary differential format. The values sent will not appear as readable characters. The garbage characters immediately after the "R=" are probably the start of the trace data. If the routine that is reading the input characters is expecting printable ASCII characters, the binary data will probably cause problems. I don't know what formats the Nidek is capable of providing, but I would recommend starting with format 1. That one is a human readable ASCII format that will be a lot easier to get working. Once you have that, moving on to a binary format should be a bit easier.

    Dave
    Dave Finegan

  3. #3
    OptiBoard Apprentice gsmahesh's Avatar
    Join Date
    Jul 2010
    Location
    Kuwait City, Kuwait
    Occupation
    Lens Manufacturer
    Posts
    33
    Dave,
    What I know is this tracer provides only binary differential format. It is fine if I can get the data in the same(3). It just need a decoding. But as you said, I am getting incomplete information. The information is getting stopped when the right eye starts. I doubt that I need to modify/correct my request to the tracer.

  4. #4
    OptiBoard Apprentice
    Join Date
    Jun 2005
    Location
    Manchester, CT
    Occupation
    Other Optical Manufacturer or Vendor
    Posts
    17
    I haven't used Visual Basic much, but as I recall there are different input mode configurations for handling text (ASCII) and binary data. That may be worth exploring.
    Dave Finegan

  5. #5
    OptiBoard Apprentice gsmahesh's Avatar
    Join Date
    Jul 2010
    Location
    Kuwait City, Kuwait
    Occupation
    Lens Manufacturer
    Posts
    33
    Beside from the programming side, I think my VCA request is not correct. I am expecting that if someone can suggest the right request.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Equipment Communication Help
    By peyes in forum General Optics and Eyecare Discussion Forum
    Replies: 2
    Last Post: 06-02-2018, 11:15 AM
  2. Converting a Hoya tracer to OMA
    By discostu in forum General Optics and Eyecare Discussion Forum
    Replies: 0
    Last Post: 04-04-2016, 04:57 PM
  3. OMA Communication Error in V75
    By gsmahesh in forum General Optics and Eyecare Discussion Forum
    Replies: 6
    Last Post: 02-14-2015, 07:40 AM
  4. Neksia/Essibox/edger tracer communication
    By becc971 in forum General Optics and Eyecare Discussion Forum
    Replies: 7
    Last Post: 10-06-2014, 06:14 PM
  5. National Optronics 4T Tracer S/N 4T-7068 2 Serial Ports OMA Compatible
    By Ocular Dexter in forum Optical Marketplace
    Replies: 8
    Last Post: 03-22-2012, 02:34 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
OptiBoard is proudly sponsored by:
BC College of Optics, Younger Optics, Vision Equipment and Optitech USA