Hi. After having various issues keeping all my devices connected I followed the advice and got myself a powered USB hub.
I have a Sitecom CN-084 7x USB 3.0. It's fairly vompact and nice and thin. I sandwich it between the Powerbox and the Pi. Up until now it is working perfectly. I plug all my devices (HEQ5-Pro, EOS 6D, Pegasus Personal powerbox, QHY tracking camera, SensoSesto focusser) into the hub. I power the Pi and the Hub from the powerbox (using 2 BEC's to step down the voltage from 12V to 5V).
The Serial Assistant currently displays the 'serial' attribute (for serial devices with the same id).
Is there an easier way to add the serial attribute without going through the manual procedure of discovering the 'serial' attribute value and then writing a new rules file which I am sure is very daunting to users that do not know linux reasonably well.
I think by the time you have fairly complete setup you will have more than one serial device sharing the same id. I know you could you do hardware mapping but that is not an ideal solution as it is yet another thing that can go wrong when trying to get setup for the evening.
I now have the following connected and working well:
- HEQ 5 mount
- EOS 6D camera
- QHY guide camera
- SensoSesto focusser
- Pegasus powerbox
- 2 dew heaters (built into the Pegasus)
All attached to a powered USB hub. All powered from the powerbox so I only need one source of power (mains or battery).
Its not in the regular build yet but if you switch to the nightly build you can get it. The instructions for the nightly build can be found a couple of pages back in this thread.
I am using the Stellarmate which is Ubuntu on the Pi. Since I have started using a good powered USB hub it has been extremely stable. Using the built in USB ports from the Pi did not work well for me. I also use an separate WiFi access point which I place as close as possible to the Pi.
Great to hear it works. Should have some clear skys here tonight so hopefully I can give it a real test.
I don't know when it will be added to the stable build. Probably best to ask Jasem when that happens.
Changes have been approved so 1.4 will be in the next nightly build.
Let me know how it goes.
Took a little longer than I anticipated, those last few details cost me more time that I thought.
I will push my changes to the repository later today so version 1.4 should be available via the nightly build within a couple of days.
I considered putting the Calibration on its own settings page but since the focuser is a simple device I put the options on the Main page.
Once you start the Calibration process you need to finish it. I have not included an Abort option on purpose as it leaves the focuser in an undefined state.
I also only display the Move In/Move Out/Stop buttons when the Calibration process requires them. These are not required for normal operation and I think they are a little dangerous as they have to be able to go beyond the current Min/Max values.
Turns out I was barking up the wrong tree. No need for a sleep!
Hi. I have just done some modifications to the Sesto Senso focuser. After the calibration process I tell the focuser to save all settings. This command seems to take a while and if I send it another command when it is still saving i get fatal serial comms errors. Using the debugger I see that as long as I pause after sending the command to save the settings I can then read out the setting I need. When it runs at full speed that's when I get the Serial comms error.
Is it OK to sleep in the driver code (this part is only used for the control panel) ?