Hey Dave (or the rest of the volttron team),
I have a question about the platform driver / modbus-tk in volttron: I have 4 devices that are being polled each second, are these 4 different device reads happening concurrently or sequentially?
From:
"Thompson, Joe" <jthompson@xxxxxxxx>
Date: Wednesday, December 18, 2024 at 3:28 PM
To: "Raker, David M" <david.raker@xxxxxxxx>, "volttron-dev@xxxxxxxxxxx" <volttron-dev@xxxxxxxxxxx>
Cc: "Smith, Morgan" <mdsmith@xxxxxxxx>
Subject: Re: [EXTERNAL] RE: Platform Driver: Device scrape interval below 1 second
Thanks David!
For some background the volttron testing I am doing is out at a site where the volttron instance does not have internet access, so it is unable to pull down other repos or switch branched right now
☹
However, I am doing the initial setup of a new volttron box that will soon be sent out to the same site, but right now this new box does have internet, so I’ve got your repo / interval_and_pad branch on this new box and can hopefully try
it out in the next few days out at the site. I just will not be able to pull down any subsequent changes you make through git very easily, but we can cross that bridge when we get there..
With this custom branch you shared would I need to do any extra configuration of my devices to try the sub-second interval and padding things out? Or should it just work with the configs I’ve already got working with standard volttron?
From:
"Raker, David M" <david.raker@xxxxxxxx>
Date: Monday, December 16, 2024 at 5:30 PM
To: "Thompson, Joe" <jthompson@xxxxxxxx>, "volttron-dev@xxxxxxxxxxx" <volttron-dev@xxxxxxxxxxx>
Cc: "Smith, Morgan" <mdsmith@xxxxxxxx>
Subject: [EXTERNAL] RE: Platform Driver: Device scrape interval below 1 second
Hi Joe, I do recall personally testing intervals of less than one second, but that was a long time ago, and it is entirely possible that I am forgetting custom
changes I made for it to work. Looking at the code which is generating the warning,
Hi Joe,
I do recall personally testing intervals of less than one second, but that was a long time ago, and it is entirely possible that I am forgetting custom changes I made for it to work. Looking
at the code which is generating the warning, though, it appears to explicitly disallow intervals of less than one second. I don’t see a definitive reason why this would have been necessary, but the code to do it has been there for a long time. I will work
on testing a change to remove this restriction, but If you are OK being a guinea pig, check out and try this branch on my fork:
https://github.com/davidraker/volttron/tree/interval_and_pad
[github.com]
This branch removes the restriction on polling intervals. It also merges an old fix I made (which we discussed previously) to add pad registers to the ModbusTK driver. I have not yet had a
chance to test either of these. I will do so shortly, though, and will let you know when I have. Meanwhile, if you do try this branch out, let me know how it goes.
Dave
From: Thompson, Joe <jthompson@xxxxxxxx>
Sent: Monday, December 16, 2024 11:25 AM
To: volttron-dev@xxxxxxxxxxx; Raker, David M <david.raker@xxxxxxxx>
Cc: Smith, Morgan <mdsmith@xxxxxxxx>
Subject: Platform Driver: Device scrape interval below 1 second
Check twice before you click! This email originated from outside PNNL.
Hi Volttron Team,
I was doing some speed testing with volttron reading from some modbus devices with the modbus-tk driver. I was hoping to try out polling rates under 1 second (500ms or even 100ms), but got this error in my logs:

Is there any way to enable these faster polling rates within volttron (im using volttron 8.1.3)?
Thanks!
Joe Thompson
Technical Leader
Electric Power Research Institute
Energy Storage and Distributed Generation
(912) 663-3407
*** This email message is for the sole use of the intended recipient(s) and may contain information that is confidential, privileged or exempt from disclosure under applicable
law. Unless otherwise expressed in this message by the sender or except as may be allowed by separate written agreement between EPRI and recipient or recipient’s employer, any review, use, distribution or disclosure by others of this message is prohibited
and this message is not intended to be an electronic signature, instrument or anything that may form a legally binding agreement with EPRI. If you are not the intended recipient, please contact the sender by reply email and permanently delete all copies of
this message. Please be advised that the message and its contents may be disclosed, accessed and reviewed by the sender's email system administrator and/or provider. ***