TA.NexDome.Shutter.ino sketch to big

[gintasd]

Firmware/TA.NexDome.Shutter/TA.NexDome.Shutter.ino sketch shows to big.

[NameOfTheDragon]

You can't build this sketch in Arduino IDE. Please see the ReadMe file for information about the required build environment and a discussion of why it was done that way. Also, the code size IS a very tight fit and it might be sensitive to the version of the compiler that you have installed.

[gintasd]

Hello Tim, Thank you for answer. I am not a programmer and have very little experience with the VisualStudio. Probably I could learn it but it would take to long :). I will not bother you but just now I stuck with a "Processing -File C*: _Programos\Astronomija\Observatorija failed because the file does not have a .ps1 extension. Specify a valid PowerShell script file name, and then try again" and can not find where to set this. Basically I can upload the hex file from the github but I need to change the gear ratio to align the software to my own dome HW. Maybe I am doing something wrong but I can not upload the hex file using the "NexDomeControlSystem.3.0.1". I have the Arduino port selected but after "Update""button the Bootloader com port does not open despite the application reboots the Arduino. And nothing happens. I did upload successfully using avrdude. After upload the control basically works fine. My PC is Win7 64bit. Arduino IDE 1.8.5

Best Regards Gintautas

On Mon, Oct 7, 2019 at 10:54 PM Tim Long notifications@github.com wrote:

You can't build this sketch in Arduino IDE. Please see the ReadMe file for information about the required build environment and a discussion of why it was done that way. Also, the code size IS a very tight fit and it might be sensitive to the version of the compiler that you have installed.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nexdome/Firmware/issues/3?email_source=notifications&email_token=ANJOF3VDKBTXFNO64G5ZTSTQNOHXRA5CNFSM4I2DZTU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEARS7FI#issuecomment-539176853, or mute the thread https://github.com/notifications/unsubscribe-auth/ANJOF3THDLDMWEDJLGPAXMTQNOHXRANCNFSM4I2DZTUQ .

-- Pagarbiai, Gintautas Drazdauskas

[NameOfTheDragon]

You shouldn't need to recompile for that. The firmware doesn't have any concept of a gear ratio. It just knows the total number of whole steps per dome revolution. Can you not just change the number of steps per revolution using the @RWR ("range write") command? Once you've determined the correct number of steps you can save it to EEPROM using @ZWR.

[gintasd]

Aaa, it works this way. OK, clear. So should I use Full Steps on the motor driver as well if the range in the controller software is set by Full Steps? Or the Full Steps are recalculated in to the Microsteps (x8) what usually are used?

On Tue, Oct 8, 2019 at 11:44 PM Tim Long notifications@github.com wrote:

You shouldn't need to recompile for that. The firmware doesn't have any concept of a gear ratio. It just knows the total number of whole steps per dome revolution. Can you not just change the number of steps per revolution using the @RWR ("range write") command? Once you've determined the correct number of steps you can save it to EEPROM using @ZWR.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nexdome/Firmware/issues/3?email_source=notifications&email_token=ANJOF3TO7GQHHIZKPFOXP6TQNTWL5A5CNFSM4I2DZTU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAVR3LI#issuecomment-539696557, or mute the thread https://github.com/notifications/unsubscribe-auth/ANJOF3RWXTNBSYP6SMX7YOTQNTWL5ANCNFSM4I2DZTUQ .

-- Pagarbiai, Gintautas Drazdauskas

[NameOfTheDragon]

I'm not totally clear what you are asking here, but in general as an end user, you always talk to the firmware in whole steps. Microstepping is fixed internally at 8 microsteps per step but you never get to see that as the user. We decided to fix it at 8 uSteps/Step as we didn't want to deal with the support issues that variable microstepping would generate ;-) Sometimes more options just confuses the users.

[gintasd]

Hi Tim, That was what I was asking :). I have tested it already a few days ago. And I agree with you - more options = more problems :).Thanks a lot.

It is not the end of the world but still unable to upload the firmware using the "NexDomeControlSystem". I was wrong in my first email regarding the Arduino reboot after the "Update" button. Actually nothing happens after the "Update" is pushed. I can see in the window appears the printed string. But I see it tries to send the update using the same port ( the option -pcom) at what Arduino is connected. I mean it does not reboot the Arduino to open the bootloader port. It updates just fine using the command line.

Best Regards Gintautas Drazdauskas

On Mon, 14 Oct 2019, 06:22 Tim Long, notifications@github.com wrote:

I'm not totally clear what you are asking here, but in general as an end user, you always talk to the firmware in whole steps. Microstepping is fixed internally at 8 microsteps per step but you never get to see that as the user. We decided to fix it at 8 uSteps/Step as we didn't want to deal with the support issues that variable microstepping would generate ;-) Sometimes more options just confuses the users.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nexdome/Firmware/issues/3?email_source=notifications&email_token=ANJOF3WMWL6ZUZGJ4FNGLMDQOPQWXA5CNFSM4I2DZTU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBDIDTY#issuecomment-541491663, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANJOF3TWAZH5R3YHLMT7XMDQOPQWXANCNFSM4I2DZTUQ .

[NameOfTheDragon]

Closing issue as there's no action resulting from it.