Hi gents, After some delay, I'm trying to setup the probe I received. Unfortunately, it seems that something is not quite working. Once it's plugged in and powered, there is no activity. There is no DHCP request for the probe so I can't see anything on the network side. Could something be wrong with the usb key? Is there a way I could reflash the usb key with the OS files? Thanks Laurent Dumont -- Laurent Dumont coldnorthadmin.com
Hi Laurent, while I am not in charge of customer support .... I can tell you that the USB Flash only stores results, the OS is on the internal flash and that the most common problem is insufficient or unstable USB power to the unit. I hope this helps until the pros arrive at the office. Daniel On 23.06.15 0:37 , Laurent Dumont wrote:
Hi gents,
After some delay, I'm trying to setup the probe I received. Unfortunately, it seems that something is not quite working. Once it's plugged in and powered, there is no activity. There is no DHCP request for the probe so I can't see anything on the network side.
Could something be wrong with the usb key? Is there a way I could reflash the usb key with the OS files?
Thanks
Laurent Dumont
On 2015/06/23 8:38 , Daniel Karrenberg wrote:
I can tell you that the USB Flash only stores results, the OS is on the internal flash
and that the most common problem is insufficient or unstable USB power to the unit.
I hope this helps until the pros arrive at the office.
Hi, It is a bit more complex than that. The internal flash is not big enough to contain all programs needed by the probe. So what we did was to move the main Atlas code to the USB stick and put the code for booting (including the kernel) and flashing the USB stick on the internal flash. If the probe is running from internal flash than the LED next to the power LED is blinking. If the probe is running from the USB stick then LEDs 3 and 4 (counting the power LED as 1) are blinking or solid. Philip
Ah, nobody tells me anything anymore around here ;-). So does this mean you can no longer just change the USB stick anymore like you used to? Daniel On 23.06.15 12:24 , Philip Homburg wrote:
On 2015/06/23 8:38 , Daniel Karrenberg wrote:
I can tell you that the USB Flash only stores results, the OS is on the internal flash
and that the most common problem is insufficient or unstable USB power to the unit.
I hope this helps until the pros arrive at the office.
Hi,
It is a bit more complex than that. The internal flash is not big enough to contain all programs needed by the probe. So what we did was to move the main Atlas code to the USB stick and put the code for booting (including the kernel) and flashing the USB stick on the internal flash.
If the probe is running from internal flash than the LED next to the power LED is blinking. If the probe is running from the USB stick then LEDs 3 and 4 (counting the power LED as 1) are blinking or solid.
Philip
On 2015/06/23 14:06 , Daniel Karrenberg wrote:
Ah, nobody tells me anything anymore around here ;-). So does this mean you can no longer just change the USB stick anymore like you used to?
This behavior is unchanged since the v3 probes were first introduced. Assuming no static network configuration, you can just plug in an empty USB stick. The code on the internal flash will fetch a copy of the Atlas firmware from the controller, write it to the USB stick and reboot to start running from the USB stick. Philip
participants (3)
-
Daniel Karrenberg -
Laurent Dumont -
Philip Homburg