Complete Help Docs

Laser Show Technology for Lighting Professionals

User Tools

Site Tools


beyond:turbo_streaming

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
beyond:turbo_streaming [2023/11/16 10:59]
Bob Varkevisser [Turbo mode]
beyond:turbo_streaming [2023/11/16 18:26] (current)
Bob Varkevisser
Line 8: Line 8:
  
  
-| Turbo button | Activity state |+**Turbo button** **Activity state** |
 | {{:beyond:turbo2-disabled.png?nolink|}} | Disabled | | {{:beyond:turbo2-disabled.png?nolink|}} | Disabled |
 | {{:beyond:turbo3-enabled.png?nolink|}} | Enabled | | {{:beyond:turbo3-enabled.png?nolink|}} | Enabled |
Line 17: Line 17:
 The classic streaming model is the default communication mode.The Classic model is exclusively based on TCP/IP communication. The TCP protocol takes care about data delivery. TCP waits for confirmation to make sure that the data is delivered. TCP communication is recognized as reliable because it will always deliver data but this also has its downsides. TCP does not consider that data might be outdated and will use high segmentation and multiple internal messages for delivery confirmation. In a less ideal situation, this can cause for delays in laser output as it can increase delivery time. Time is a critical thing! The classic streaming model is the default communication mode.The Classic model is exclusively based on TCP/IP communication. The TCP protocol takes care about data delivery. TCP waits for confirmation to make sure that the data is delivered. TCP communication is recognized as reliable because it will always deliver data but this also has its downsides. TCP does not consider that data might be outdated and will use high segmentation and multiple internal messages for delivery confirmation. In a less ideal situation, this can cause for delays in laser output as it can increase delivery time. Time is a critical thing!
  
-===== Turbo mode ===== +===== The Turbo mode model ===== 
-It is not a secret that ArNET and ANN are based on UDP (User Datagram Protocol) communication. UDP is les depended on delivery notifications. What we did in turbo mode is use the best of both worlds. The turbo mode protocol is based on both TCP and UDP.+It is not a secret that ArNET and ANN are based on UDP (User Datagram Protocol) communication. UDP is less depended on delivery notifications. What we did in turbo mode is use the best of both worlds. The turbo mode protocol is based on both TCP and UDP.
  
-Monitoring of communication between FB4 and BEYOND can be done through the FB4 data transmission monitor Diagrams. The FB4 data transmission monitor has been expanded with the following graphs. which you can access by right clicking on the graphs.+===== FB4 data transmission monitordiagrams ===== 
 +Monitoring of communication between FB4 and BEYOND can be done through the FB4 data transmission monitor diagrams. The FB4 data transmission monitor has been expanded with the following graphs. which you can access by right clicking on the graphs.
  
-{{ :beyond:turbo4.png?nolink&600 |}}+{{ :beyond:turbo4.png?nolink&800 |}}
  
-| Menu option | Function | Comments |+**Menu option** **Function** **Comments** |
 | Turbo packet count | displays the number of UDP packets per output frame | |  | Turbo packet count | displays the number of UDP packets per output frame | | 
 | Turbo frame size | displays size of laser frame in bytes |  | | Turbo frame size | displays size of laser frame in bytes |  |
Line 35: Line 36:
 | Turbo delivery | displays the time between 1st and last segment of laser frame | With good network conditions, time should be up to 3ms for big laser frames. | | Turbo delivery | displays the time between 1st and last segment of laser frame | With good network conditions, time should be up to 3ms for big laser frames. |
 | Turbo feedback drop | displays the number of laser frames where feedback did not arrive.| | | Turbo feedback drop | displays the number of laser frames where feedback did not arrive.| |
-| Turbo segmentation | displays the graph of packets per laser frame | One pixel is one packet. Normally you should see green dots. If all green – data flows well. If some red – signal of lost packet +| Turbo segmentation | displays the graph of packets per laser frame | One pixel is one packet. Normally you should see green dots. If all green – data flows well. If some red – signal of lost packetMost of parameters are statistics. Keep an eye on the main parameters in case if problems |
-Most of parameters are statistics. Keep an eye on the main parameters in case if problems |+
 | Turbo Core reaction | displays the core reaction time. | Normally this should be around 1ms | | Turbo Core reaction | displays the core reaction time. | Normally this should be around 1ms |
 | Turbo Retransmission requests | displays the retransmission requests. | If all is well, then should be zero | | Turbo Retransmission requests | displays the retransmission requests. | If all is well, then should be zero |
beyond/turbo_streaming.1700128778.txt · Last modified: 2023/11/16 10:59 by Bob Varkevisser