SinelaboreRT Header Logo

SinelaboreRT

As simple as possible, but not any simpler!

User Tools

Site Tools


wiki:news:11aug2015

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
wiki:news:11aug2015 [2018/09/11 22:10] pmuellerwiki:news:11aug2015 [2022/08/17 19:41] (current) – Discussion status changed pmueller
Line 69: Line 69:
 {{:wiki:news:modbus_client:modbus_master.png?nolink}} {{:wiki:news:modbus_client:modbus_master.png?nolink}}
  
-The timing of the final device is shown below. D0 shows the system clock generated by hardware timer A. It calls the timer tick function. If no timer events were detected the CPU enters low power mode again. D2 shows the receiving telegram. D1 the transmission telegram. The CPU replays within 14ms. This could be further optimized if needed. The RS485 line is shown in the bottom part as differential signal (CH1-CH2).+The timing of the final device is shown below. D0 shows the system clock generated by hardware timer A. It calls the timer tick function. If no timer events were detected the CPU enters low power mode again. D2 shows the receiving telegram. D1 the transmission telegram. The CPU replys within 14ms. This could be further optimized if needed. The RS485 line is shown in the bottom part as differential signal (CH1-CH2).
  
 {{:wiki:news:modbus_client:modbus_timing.png?nolink}}  {{:wiki:news:modbus_client:modbus_timing.png?nolink}} 
Line 101: Line 101:
 Peter Peter
  
-{(rater>id=11082015|name=How do you like this article?|type=rate)} +~~DISCUSSION:closed|Leave your comments~~
-~~DISCUSSION|Leave your comments~~+
  
 ---- ----
Line 110: Line 109:
  
 {{tag>[Modbus ModbusRTU Application_Example Activity MSP430]}} {{tag>[Modbus ModbusRTU Application_Example Activity MSP430]}}
 +
 +
wiki/news/11aug2015.1536696602.txt.gz · Last modified: 2018/09/11 22:10 by pmueller

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki