| Products > Test Equipment |
| Rigol DP832 - Firmware list and bugs |
| << < (108/153) > >> |
| rgarito:
I have a DP832-A which I was attempting to control via LXI/Network. When doing so, the power supply would randomly become unreachable on the network (would not even respond to pings). Recovery meant either power cycling or re-initializing the network interface via the Utility menu. I spoke to Rigol and they said a beta firmware (1.16) resolves it. I have tested and confirm that the beta does resolve it (at least so far). The beta isn't available for download from their site but they replied with a copy of it within about 30 minutes of me sending their tech support an email. |
| ornea:
That has been my exact problem and driving me nuts since day dot. Is it possible to share the file or perhaps the rigol contact. |
| nicolasg:
I never understood why they keep such a tight leash on firmwares. Its been at least a year since 1.16 has been mentioned, and its still not "public". Anyways, i had the same lan problem and i just emailed rigol and in less than a day they replied. Should maybe edit the main post to includee the known lan issue and the fix is 1.16 |
| Macbeth:
Just 2 days ago I had the simplest of setups possible, some 6x AD587LQ to test - no external components just Vin and Vout. 15V supply from CH1 of DP832, current limit a generous 50mA. Output switched off and back on between each AD587LQ change. No heat as the PSU had been on for at most 3 minutes. All but one of the IC's measured a perfect 9.9995 - 10.0005 but the DP832 decided to reboot on the second good device of the six. During the reboot it held the output on, it was only when it finally came back up to full Rigol operating system that it actually decided to switch the output off - and I had to manually switch it back on. No rhyme or reason, but completely shit for a bench supply that should be trusted to be left alone to do it's job, data logging and all. |O |
| Sparky:
--- Quote from: nicolasg on November 13, 2018, 09:53:48 pm ---I never understood why they keep such a tight leash on firmwares. Its been at least a year since 1.16 has been mentioned, and its still not "public". Anyways, i had the same lan problem and i just emailed rigol and in less than a day they replied. Should maybe edit the main post to includee the known lan issue and the fix is 1.16 --- End quote --- Thanks for your note! I am the OP and have not tracked this thread for sometime. I will update the first post to include information about the non-public v1.16 firmware, and that it resolves some LAN-related issues (the IP lease timeout/renew?). Would you be willing to post the firmware here? Sparky |
| Navigation |
| Message Index |
| Next page |
| Previous page |