OkiePC
Lifetime Supporting Member
Just downloaded the latest build (469)
I opened my latest project and hit verify...just to see what would happen...normally I would expect it to say there was a difference. My G310 is sitting on a chair in the office running the same app created with build 459.
However, the actual G310 went to the G3 boot logo and stayed there. I did get the prompt to update it, to which I answered no for now. After 2 minutes it was still on that screen, touching the screen I got the beep, but the logo screen remained.
It recovered after a power cycle, but this was unexpected. I did not think there was any risk of halting the HMI just by using the "verify" command to check for application match between offline and running programs.
This behavior is repeatable.
Just an FYI for those who may do this on running equipment.
On the positive note, as far as I can tell there was no issue when I did let it go ahead and update...
now to see if they fixed my other issue in this build...
EDIT: Nope. Spanning reads are still boogered with my particular SLC and cd3 file.
Paul
I opened my latest project and hit verify...just to see what would happen...normally I would expect it to say there was a difference. My G310 is sitting on a chair in the office running the same app created with build 459.
However, the actual G310 went to the G3 boot logo and stayed there. I did get the prompt to update it, to which I answered no for now. After 2 minutes it was still on that screen, touching the screen I got the beep, but the logo screen remained.
It recovered after a power cycle, but this was unexpected. I did not think there was any risk of halting the HMI just by using the "verify" command to check for application match between offline and running programs.
This behavior is repeatable.
Just an FYI for those who may do this on running equipment.
On the positive note, as far as I can tell there was no issue when I did let it go ahead and update...
now to see if they fixed my other issue in this build...
EDIT: Nope. Spanning reads are still boogered with my particular SLC and cd3 file.
Paul
Last edited: