Summary of International Technical Exhibition on Image Technology and Equipment

The exhibition is over. According to the organizer's announcement, the number of visitors decreased by about 5%.
In our booth, the number of visitors was "the same as the previous show + α".
Thank you very much for stopping by our booth.
The following are some of the things that stood out in the discussions we had this time.
(1) "We are looking for a better way because we can't get it to work" from an image manufacturer.
(2) Proposals for technical cooperation.
3) Requests for consulting services.
And so on. New inquiries are moderate.
Our stance is
(1) It is impossible to provide a part of the FI-loaded technology. We do not have any outrageous technology that "users" would not understand.
2) There is no technology from other companies that I "want". I only use technologies that I have tested and verified myself.
(3) We cannot undertake consulting work whose output is unclear because it does not lead to the benefit of the user. We can't undertake consulting work unless the output is "implemented and effective".
(4) Anywhere where "FI is adopted as it is" is acceptable. We cannot undertake customization because we do not have enough man-hours and it would be difficult to manage future version upgrades.
(5) If I am convinced with the improvement suggestions from users who have adopted FI, I will incorporate them into the "standard" system free of charge.
This is how I feel about it.
There is still a mountain of technical details that I would like to include, so I don't think the situation will change for a while.
For the time being, I would like to make the following changes by the end of this month
(1) Implementation of I/O control function by socket communication.
→2) Paving the way for a "notebook PC base" by eliminating the need for a DIO board.
→2) Inter-application communication to link with other applications.
(2) Support for MATROX board
We are planning to support MATROX board (or rather, it is essential to support replacement of old users).
In addition, next year we plan to
(1) Enable additional functionality through HALCON's DevEngine. (Planned)
(2) Implement a character recognition function (based on HALCON).
etc.
If we don't declare a #deadline, we will be cheating, so for now, "character recognition" by June.
# We will put it in.

Leave a comment

Your e-mail address will not be made public. Fields marked with * are required.