Re: [time-nuts] Prologix VRBOOT error
I just wanted to let everyone know that with the help of a firmware upgrade and some great support from Abdul, we no longer have any problems with the Prologix GPIB interface. Not having to rebuild GPIB drivers every time the kernel gets upgraded is a huge win for us. Thanks, Matt On Wed, Jun 4, 2008 at 6:50 AM, Prologix [EMAIL PROTECTED] wrote: Matt, We are testing a fix. I'll be in touch soon. Regards, Abdul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Ettus Sent: Wednesday, June 04, 2008 12:40 AM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] Prologix VRBOOT error On Tue, Jun 3, 2008 at 5:31 PM, Prologix [EMAIL PROTECTED] wrote: Short version: Connect USB cable before connecting GPIB, and leave USB connected and powered. That isn't realistic for my setup. Long version: On startup, if one of the MCU I/O lines is pulled low, the controller will enter firmware update mode. As it happens, this I/O line is also one of the GPIB bus signals. Some instruments seem to have stronger pull-down on the bus lines than others. The controller may enter firmware update mode, if the USB cable is plugged in while the controller is connected to such an instrument. Since the pull-down is passive, this behavior could happen even if the instrument is powered down when connecting USB. Honestly, this sounds like a serious design flaw to me. I have 5 GPIB instruments, and 3 of them cause this behavior. If 3 pieces of test equipment from 3 different manufacturers cause this behavior, it must be pretty common. Matt ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Prologix VRBOOT error
On Tue, Jun 3, 2008 at 5:31 PM, Prologix [EMAIL PROTECTED] wrote: Short version: Connect USB cable before connecting GPIB, and leave USB connected and powered. That isn't realistic for my setup. Long version: On startup, if one of the MCU I/O lines is pulled low, the controller will enter firmware update mode. As it happens, this I/O line is also one of the GPIB bus signals. Some instruments seem to have stronger pull-down on the bus lines than others. The controller may enter firmware update mode, if the USB cable is plugged in while the controller is connected to such an instrument. Since the pull-down is passive, this behavior could happen even if the instrument is powered down when connecting USB. Honestly, this sounds like a serious design flaw to me. I have 5 GPIB instruments, and 3 of them cause this behavior. If 3 pieces of test equipment from 3 different manufacturers cause this behavior, it must be pretty common. Matt ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Prologix VRBOOT error
Matt, We are testing a fix. I'll be in touch soon. Regards, Abdul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Ettus Sent: Wednesday, June 04, 2008 12:40 AM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] Prologix VRBOOT error On Tue, Jun 3, 2008 at 5:31 PM, Prologix [EMAIL PROTECTED] wrote: Short version: Connect USB cable before connecting GPIB, and leave USB connected and powered. That isn't realistic for my setup. Long version: On startup, if one of the MCU I/O lines is pulled low, the controller will enter firmware update mode. As it happens, this I/O line is also one of the GPIB bus signals. Some instruments seem to have stronger pull-down on the bus lines than others. The controller may enter firmware update mode, if the USB cable is plugged in while the controller is connected to such an instrument. Since the pull-down is passive, this behavior could happen even if the instrument is powered down when connecting USB. Honestly, this sounds like a serious design flaw to me. I have 5 GPIB instruments, and 3 of them cause this behavior. If 3 pieces of test equipment from 3 different manufacturers cause this behavior, it must be pretty common. Matt ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Prologix VRBOOT error
Hello Matt, It appears your Prologix GPIB-USB controller is in firmware update mode. Please follow these steps: 1. Disconnect USB cable and GPIB cable. If the controller is plugged onto an instrument, unplug it. 2. Connect USB cable. 3. Connect GPIB cable, or plug onto instrument. Let me know if you have more questions. Regards, Abdul Prologix, llc www.prologix.biz -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Ettus Sent: Tuesday, June 03, 2008 4:19 PM To: Discussion of precise time and frequency measurement Subject: [time-nuts] Prologix VRBOOT error I just received a Prologix GPIB interface today. At first it was working, but it only works some times when it is connected. The others it sends the following to minicom: ?VRBOOT??? It seems to get commands and try to respond, but it sends weird things. If I send a ++help it sends S and more question marks. Pressing enter causes it to send more question marks. Powering off and back on doesn't help. Anybody seen this behavior before? Matt ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Prologix VRBOOT error
On Tue, Jun 3, 2008 at 5:03 PM, Prologix [EMAIL PROTECTED] wrote: Hello Matt, It appears your Prologix GPIB-USB controller is in firmware update mode. Please follow these steps: 1. Disconnect USB cable and GPIB cable. If the controller is plugged onto an instrument, unplug it. 2. Connect USB cable. 3. Connect GPIB cable, or plug onto instrument. Let me know if you have more questions. That seems to fix things. Simply unplugging USB isn't enough -- I have to take it off the instruments as well. How do I keep from getting into that mode in the first place? I need this to work reliably without having to reconnect it several times a day. Matt ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Prologix VRBOOT error
Short version: Connect USB cable before connecting GPIB, and leave USB connected and powered. Long version: On startup, if one of the MCU I/O lines is pulled low, the controller will enter firmware update mode. As it happens, this I/O line is also one of the GPIB bus signals. Some instruments seem to have stronger pull-down on the bus lines than others. The controller may enter firmware update mode, if the USB cable is plugged in while the controller is connected to such an instrument. Since the pull-down is passive, this behavior could happen even if the instrument is powered down when connecting USB. Hope that helps. Regards, Abdul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Ettus Sent: Tuesday, June 03, 2008 5:12 PM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] Prologix VRBOOT error On Tue, Jun 3, 2008 at 5:03 PM, Prologix [EMAIL PROTECTED] wrote: Hello Matt, It appears your Prologix GPIB-USB controller is in firmware update mode. Please follow these steps: 1. Disconnect USB cable and GPIB cable. If the controller is plugged onto an instrument, unplug it. 2. Connect USB cable. 3. Connect GPIB cable, or plug onto instrument. Let me know if you have more questions. That seems to fix things. Simply unplugging USB isn't enough -- I have to take it off the instruments as well. How do I keep from getting into that mode in the first place? I need this to work reliably without having to reconnect it several times a day. Matt ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
