@Loukas
I can help if he is in the USA via chrome remote desktop.
@Johann
I would get the directions from the GD wiki.
You MUST do this in the exact order, or you will likely have problems.
Use the flip the dip switches on the Simucube method.
And I wouldn’t stay with MMOS. The Simucube software is a big upgrade over MMOS.
I am in South Africa I will look in the wiki. Where on the wiki can i have a look at this.
This is what I get…
There is a section on Simucube.
It goes thru all of the steps to build and operate a Simucube.
When I am home I will get you a link unless someone else does it first.
Ok thanks for the help
try this perhaps
Can you paste the debug event log from 0.11.2 after power-off and power-on?
SimuCUBE Boot : 0
SimuCUBE Boot : 11
SimuCUBE Boot : 2
Flash settings data loaded : 0
Initial config has not been performed. : 0
First-time drive initialization : 0
Error initializing SMBus baudrate : 0
State: Error uploading Drive firmware : 0
Command: Request profile number : 0
Command: Request profile name for profile : 0
Command: Request profile byte data for profile : 0
Command: Request hardware settings : 0
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 0
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 1
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 2
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 3
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 4
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 5
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 6
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 7
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 8
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 9
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 10
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 11
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 12
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 13
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 14
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 15
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 16
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 17
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 18
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 19
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 20
Command: Event log download request : 0
looks like the very first communications with the servo drive are failing already, that is, the Simucube processor is not able to directly communicate with the servo drive.
Is the board you have a Simucube 1r004?
Hi yes it is…
MMos is working fine with the board
yeah, MMOS is not communicating via the simplemotion bus, it uses PWM&DIR signals.
I’m thinking about this possibly being a hardware issue with your particular Simucube board.
Ok thanks for your help.
You are very welcome.
