Slow upload to NI700 from NS
syslock
Posts: 45
When I'm uploading code to an NI700, the file transfer window shows that 122000 bytes are uploaded then it pauses for about a second then another 122000 Bytes are uploaded.
Is this normal I have 4 NI700 in this system and they all have the same behaviour Firmware Version 3.60.453.
I also have an NI3100 in the same system Firmware Version 3.60.453. and code uploads fine.
I checked the set Ethernet mode setting and all are set 100Mb Full
Is there any way to correct this as it is quite time consuming when you have 3/4 Duet modules to upload each time you load code and the transfers often fail with error Transfer Aborted Busy sending
Any help and comments welcome.
Is this normal I have 4 NI700 in this system and they all have the same behaviour Firmware Version 3.60.453.
I also have an NI3100 in the same system Firmware Version 3.60.453. and code uploads fine.
I checked the set Ethernet mode setting and all are set 100Mb Full
Is there any way to correct this as it is quite time consuming when you have 3/4 Duet modules to upload each time you load code and the transfers often fail with error Transfer Aborted Busy sending
Any help and comments welcome.
0
Comments
If you suspect it's your code and you can't even get the fix uploaded, you can right click the master file in the transfer box, choose options, and turn off sending the Duet support files every time (this is a per-project, per-transfer setting, you have to do it every time you "add" that project to the transfer list). I've also found that if you reboot the master, and send files as soon as it comes online but before the code is fully running, you can often get it in.
Its definitely not the code because I have the same behaviour after a clean disk.
Its seems to be something to do with the NI700/NI900 because if I use the same network cable and switch port as my NI3100 which loads code fine I still see the same behaviour.
Its frustrating I can handle a delay when I'm working with just 1 NI700 but I have 4 in the system which amounts to around 5 minutes of waiting each time I upload code.
Looking at how many people are experiencing the same issue I think it should be noted as a firmware bug.
I would bet this is a memory handler issue and not the firmware. And that it's by design.
Spurts, yes, but I've not seen them being anything more than momentary periodic pauses. Not transfer-crippling slowdowns. I still say the OP has another factor making it take so long.