PSA; ALC optiflex under AAR; very long download times.
Posted: Tue Apr 14, 2020 11:25 am
First of all this doesn't currently work unless you change system.properties file setting bacnet.segmentation.on = false. Doesn't seem to be recommended to leave it there either but it will allow the driver download to complete.
My conclusion is if you have one of these under an AAR and need to do significant driver updates do it locally via USB or network. Even Rnet is going to take too long if you have that available. Time to complete depends heavily on how much is different in the driver from the version it has to the one you want to go to. Could be as short as fifteen minutes or as long as three or four hours.
Remember you can update the driver near instantly over direct ethernet or USB. Ethernet will require reconfiguration of the modules router settings page to update the home network and network numbers, you don't have to have the exact right job file, just get the driver in it and fix the router setting page home network so you can reach it through the customer server again.
-----------------------------------------------------------------------------------------
---There are no programs in use, no other MAC address taking time on the token, and straight ethernet connection; these will represent best case results. Field times will be longer than these.
-----------------------------------------------------------------------------------------
---Testing between the two latest released drivers;
Results G5RE on Ethernet
unknown to drv_fwex_103-06-2055; 11:45
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 2:10
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 1:30
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 1:20
Results G5RE on ARCnet under LGR
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 5:26
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 5:25
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 5:26
Results G5RE on ARCnet under AAR and LGR
All downloads failed with default system.properties settings
results with; bacnet.segmentation.on = false
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 16:40
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 16:27
Results using Rnet cable
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 17:00
-----------------------------------------------------------------------------------------
---Second round add testing results for older drv_fwex_101-00-2056 - drv_fwex_103-06-2055
Results G5RE on Ethernet
drv_fwex_103-06-2045 -> drv_fwex_101-00-2056: 6:18
drv_fwex_101-00-2056 -> drv_fwex_103-06-2055: 6:26
Results G5RE on ARCnet under LGR
drv_fwex_103-06-2055 -> drv_fwex_101-00-2056: 54:12 (almost one hour under main ARCnet)
drv_fwex_101-00-2056 -> drv_fwex_103-06-2055: 56.15
Results G5RE on ARCnet under AAR and LGR
drv_fwex_103-06-2055 -> drv_fwex_101-00-2056: 3:02:25 (three hours two minutes)
drv_fwex_101-00-2056 -> drv_fwex_103-06-2055: Cancelled at 4:32:20, needed to go home. Was at 71% done.
Results using Rnet cable
Unable to test, drv_fwex_101-00-2056 not allowed for OFBBC
drv_fwex_104-00-2130 -> drv_fwex_103-06-2055: 2:14:00 (two hours, fourteen minutes)
-----------------------------------------------------------------------------------------
My conclusion is if you have one of these under an AAR and need to do significant driver updates do it locally via USB or network. Even Rnet is going to take too long if you have that available. Time to complete depends heavily on how much is different in the driver from the version it has to the one you want to go to. Could be as short as fifteen minutes or as long as three or four hours.
Remember you can update the driver near instantly over direct ethernet or USB. Ethernet will require reconfiguration of the modules router settings page to update the home network and network numbers, you don't have to have the exact right job file, just get the driver in it and fix the router setting page home network so you can reach it through the customer server again.
-----------------------------------------------------------------------------------------
---There are no programs in use, no other MAC address taking time on the token, and straight ethernet connection; these will represent best case results. Field times will be longer than these.
-----------------------------------------------------------------------------------------
---Testing between the two latest released drivers;
Results G5RE on Ethernet
unknown to drv_fwex_103-06-2055; 11:45
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 2:10
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 1:30
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 1:20
Results G5RE on ARCnet under LGR
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 5:26
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 5:25
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 5:26
Results G5RE on ARCnet under AAR and LGR
All downloads failed with default system.properties settings
results with; bacnet.segmentation.on = false
drv_fwex_103-06-2055 -> drv_fwex_103-06-2045: 16:40
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 16:27
Results using Rnet cable
drv_fwex_103-06-2045 -> drv_fwex_103-06-2055: 17:00
-----------------------------------------------------------------------------------------
---Second round add testing results for older drv_fwex_101-00-2056 - drv_fwex_103-06-2055
Results G5RE on Ethernet
drv_fwex_103-06-2045 -> drv_fwex_101-00-2056: 6:18
drv_fwex_101-00-2056 -> drv_fwex_103-06-2055: 6:26
Results G5RE on ARCnet under LGR
drv_fwex_103-06-2055 -> drv_fwex_101-00-2056: 54:12 (almost one hour under main ARCnet)
drv_fwex_101-00-2056 -> drv_fwex_103-06-2055: 56.15
Results G5RE on ARCnet under AAR and LGR
drv_fwex_103-06-2055 -> drv_fwex_101-00-2056: 3:02:25 (three hours two minutes)
drv_fwex_101-00-2056 -> drv_fwex_103-06-2055: Cancelled at 4:32:20, needed to go home. Was at 71% done.
Results using Rnet cable
Unable to test, drv_fwex_101-00-2056 not allowed for OFBBC
drv_fwex_104-00-2130 -> drv_fwex_103-06-2055: 2:14:00 (two hours, fourteen minutes)
-----------------------------------------------------------------------------------------