$@M's dashboard

Please contact the technical support at Tibbo for schematic diagrams, as far as I know this info is not posted publicly.

Why the subject stays without the answer by Official Rep / Employee or maybe this secret ?

thanks

http://depositfiles.com/files/7010119 - datasheet for YCL-PTC1111-01G

What is the flash block write time and write cycle? is there a difference in EEPROM byte write time?

I see... the answer is no, doesnt it ? no datasheet and no schematic, what a waste...

Re EM1000-TEV, what about this:

http://docs.tibbo.com/phm/development...

? Might have something useful there. I think it doesn't have a full schematic, but a lot of data.

And how would a schematic help you make it faster?

I think you should build it yourself, because tibbo only support its own registered hardware (there is only three LCD type you can use : LB0-LB2), there is no way tibbo can support HD44780 compatible LCD, except you make it's own library using basic languange, same as the ps2 barcode.

Thanks Mike! :) – ezuk, on July 30, 2008 06:19

Thanks :) – vovkos, on July 30, 2008 05:40

We also plan to include WinPCap into Ninja installer package for convenience. But you are right, error message should not be there even if no wincpap is installed (for users that are not interested in network sniffing) We will fix that in future revisions. – vovkos, on July 30, 2008 05:38

Let me add some clarification regarding this topic.

For the time being, we are not planning to charge for our TIDE software, even when we take it out of beta (which is to happen soon). We will do our best (but do not undertake) to keep this policy in the future. We can afford to do so because we also sell related hardware.
Ninja is a different story. It simply has no related hardware, and we at least need to cover the the process of turning a set of separated internal utilities into a finished product, right?

Now to rather confusing topic of relations between Ninja and existing packet sniffers.

Originally Ninja (which was not called Ninja at that time ;) was meant to be an advanced terminal emulation program with support of multiple transports (TCP/UDP/PIPE/Serial), client & server modes, UDP broadcasts and ability to handle binary data.
But the resulting modular and asynchronous I/O architecture and -- more importantly -- the beautiful logging engine were simply too good to stop just here :)
So we decided to add monitoring capabilities as well (serial sniffer is definitely coming in the future releases) -- to turn advanced terminal emulation program into a well-rounded communication debugging tool.

The difference between Ninja Network Sniffer plug-in and existing packet sniffers such as WireShark -- is in the representation of captured packets.
For example, WireShark simply cannot show the contents of 2 packets at once -- you have to switch from packet to packet to see the contents.
Our log engine lets us show all the packet contents side-by-side in a single view, making it much easier to follow the actual data flow.
Of course current protocol parsing capabilities of Ninja Network Sniffer plug-in could not match those of WireShark -- which has been in development for over a decade.
Currently we only have support for basic internet protocols such as TCP and UDP, but if there is demand from customers we will work to improve that.

BTW Ninja has another approach to sniffing TCP/UDP/PIPE connections, and that is Socket Proxy plug-in.
Being proxy, it redirects the connection between 2 endpoint and all the data they exchange -- logging it in the process.
That means you also get the contents of data flow, but this time you get it in an even clearer representation, avoiding "packet" notation.
Not to mention that regular network sniffers (WireShark included) simply do not fit into certain scenarios.

Wrapping up, Ninja is not trying to replicate functionality of WireShark and other packet sniffers.
Instead, it introduces a different approach to viewing captured data.
But even if you decide to stick with your favorite tried-and-true packet sniffer, other Ninja plug-ins still can offer functionality useful in the fight against issues in communication area.

I'm hopeTibbo is making lots of money, their tools are terrific!

I'm not quite sure I'm following... There are no plans to charge for TIDE... This is a different product. You have nothing to worry about re TIDE. :) And I do apologize if anyone was offended - that was not my intent! – ezuk, on July 29, 2008 10:59

Please be not offend, but he seems me that this is the bad politics of the firm, such tools guilty free. I'm worries a fact that Tide has the postscript "This software can be used free of charge for as long as it remains in BETA".

This marks that he will be paid in the future (Tide), and stops then to be worth while from solutions Tibbo.
He stays us to have hopes only that he will not happen so and tide is in the version beta eternally ;]

Right -- it only means the sniffer won't work (other plug-ins work). To try the sniffir, get WinPCap - http://www.winpcap.org/ – ezuk, on July 29, 2008 10:44