Rockwell ControlFlash failures

[geniusintraining]

How about an older build of ControlFlash ?

 

[L33er]

There is glitch w 33.013. I could not flash to 33.013.

Down flash to 32.0
then up flash to 33.012
no go w 33.013

I am able to flash to 33.013 using CF and adding rockwell inc. as trusted one.

 

[TheWaterboy]

this might be obvious but is the PLC in the right state to flash ?

 

[Duranthas]

I mostly only deal with L6X processors so maybe Studio5000 can't do this, but in RSLogix 5000 I can click Communications / Who Active / and from the tree when I navigate to the PLC it will allow me to Update Firmware. Can you use this method?

 

[travispedley]

this might be obvious but is the PLC in the right state to flash ?

Yes, I can flash it with a different laptop.

 

[travispedley]

I mostly only deal with L6X processors so maybe Studio5000 can't do this, but in RSLogix 5000 I can click Communications / Who Active / and from the tree when I navigate to the PLC it will allow me to Update Firmware. Can you use this method?

That launches the OG ControlFlash, which has a different problem. I cannot update the library to use the 1756-L71 V33.013 firmware. I can import it, it says it is successful, but when I run the flash, it does not show up as an option when selecting the FW to flash. The whole thing reeks of Windows update taint. I'm not rolling anything back, in my experience that causes more problems than it solves. So I'm creating a new VM and loading all the rockwell software on it and see what happens.

 

[travispedley]

Flashing works in newly created Win10 VM. There has to be something that killed it. I did a full windows update cycle before I installed anything, so the OS is the same, other than absolutely clean install with Rockwell Software only. Any lesson in why we use VM's I guess, I've just never had any problems with Rockwell like this.