Hi! During development of RTcfg layer on uP, a several questions have arisen because of lack of my understanding of the some RTcfg protocol parts.
1. What exactly client should do with content of Active Station field in stage 2 Initial frame? All the necessary information can be obtained through a announcement and a ready frames. 2. What should happen when a client detect a inconsistent state 2 data between ack? It should wait for a number of frames given by burst rate or do something else? 3. What happen when the flag 0 (request available stage 2 configuration data from the server) in Flags field in New Announcement frame is not set and the server has stage 2 data for given client (set in server RTnet configuration file) 4. Why Physical Client Address field in Dead Station Frame is 32bytes long? And other questions from standard PC implementation (Xenomai): 1. Where stage 2 data are stored on client side? How client can get to these data. 2. If some station stop responding (stop sending a heartbeats), is there a way to inform a application that some station is down? Or that the station is up? That's all what bothering me at the moment. Best regards, Mariusz Janiak ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
