Forum Replies Created
Great! Thanks. Looking forward to test it
Thanks Max – I wasn’t aware of that I might give it a try. Though posts like this still makes me want the latest version as a DLL instead: http://www.monobrick.dk/forums/topic/error-when-building-with-xamarin/
Thanks. Yes, I have read that this is an alternative, but I do not know anything about github and how to compile it, and I have limited time to figure that out, and to be honest I am not that interested in it either. I just want the latest version and an update log so I know when I can continue with my little project 🙂
Thanks Max.I started to use MB a little while ago and ran into some issues with the motor controls and was told that there was a new version coming, but I haven’t seen any news about it on the forum, so I am still not quite sure if issues has been fixed or not.
I think I just found the answers to my previous question. I just found that the output of the display tricked me as the last two digits of the tacho count were clipped. So I think it’s safe to say that the tacho-count shows the number of steps which is the same as degrees.
About the Ultrasonic-output, I think the explanation is as simple as there is a comma missing. It should be 36,1 and 111,1 cm 🙂
One follow up question. I don’t think I understand the Steps-parameters in SpeedProfileStep and the Tacho count.
I just executed the following:
Bakmotor.ResetTacho (); Bakmotor.SpeedProfileStep (50, 100, 300, 100, true, true); LcdConsole.WriteLine("SpeedProfileStep (1), Taco: " + Bakmotor.GetTachoCount()); LcdConsole.WriteLine ("Ultrasonic: " + usSensor.ReadAsString ()); Bakmotor.SpeedProfileStep (-50, 10, 30, 10, true, true); LcdConsole.WriteLine("SpeedProfileStep (2), Taco: " + Bakmotor.GetTachoCount()); LcdConsole.WriteLine ("Ultrasonic: " + usSensor.ReadAsString ());
The output is something like:
peedProfileStep (1), Taco: 1
Ultrasonic: 361 cm
peedProfileStep (2), Taco: 4
Ultrasonic: 1111 cm
It seems both the GetTachoCount and the ultrasonic sensor reading are wrong. How can the tacho count be 1 after the first run and 4 after the second run backwards?
I think I need an explanation on what exactly the tach count is (is it degrees?) and what the Steps parameters are. Are they also degrees?
Also note that the output from the ultrasonic sensor seems to be different for every run.
Yes, that makes sense. I’ll check out the SpeedProfileStep function.
By the way – how are updates communicated? It seems the blog hasn’t been updated for a while.
Takk for hjelpen!
Hi Anders. I have just started to do some test-coding trying to learn both C# and Monobrick at the same time 🙂
Am I correct to understand that I should not use On() anymore, but use Move or MoveTo instead?
Actually it didn’t take that much longer time. I prefer working over fast 😉
Cool to have Monobrick running now. Looking forward to play with it!
Thanks Anders, but now I tried again by using
sudo dd if=imagefile_512MB.img of=/dev/disk1 bs=1m
sudo dd if= imagefile_512MB.img of=/dev/rdisk1 bs=1m
..and now it works 🙂 Not sure why, but I guess not using raw is more fail safe?
Hi. Thanks for the suggestion. Actually I tried that earlier today, but it did not work either. One difference is that the red light never turned off, but it didnt complete booting anyway 🙁