|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Tracking down a stuttering JAG/CAM drive.
Quote:
Our status is being sent to an LED on the Cypress module. That's done by the DS (not the dashboard... right?) Can I just speed up that item through the DS, or do I need to send custom data to a custom dashboard and then get it to the Cypress..... I'm so confused...! Quote:
Pulling breakers...... excuse me !!!!! |
|
#2
|
|||||
|
|||||
|
Re: Tracking down a stuttering JAG/CAM drive.
Yea, the Cypress outputs are directed by the DS app.
I was thinking of Dashboard lights. I haven't looked at the latency of Cypress outputs. It all comes across in the same packets, but I don't know if they are sliced into every packet or only every nth packet. |
|
#3
|
|||
|
|||
|
Re: Tracking down a stuttering JAG/CAM drive.
DS data that includes Cypress info is sent eery packet. The latency could be off by a packet depending on when you are updating things. Also, the high and low priority data really isn't that different. The names refer to what is done when there isn't room for all of the data to fit. The normal case is for all data to be sent each packet. The slow dashboard is due more to the Build Data method of metering out the reads and reporting data twice a second.
Greg McKaskle |
|
#4
|
|||||
|
|||||
|
Re: Tracking down a stuttering JAG/CAM drive.
I forgot how you split up the IO data for the default Dashboard to spread the impact of reading it all out a bit .
|
|
#5
|
|||||
|
|||||
|
Re: Tracking down a stuttering JAG/CAM drive.
Phil,
Does TU #19 address your issues? |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|